Solved

vsi The property ‘SourceFile’ of file ‘xxxx.dll’ is invalid.

Posted on 2002-07-18
6
463 Views
Last Modified: 2012-06-27
I’m trying to build a merge module with visual studio installer, the project contains several dlls that I have created and I am getting this warning for only one of them.

If I double-click the file name in the dependencies list I get the message ‘The file that this item references cannot be found.’.

The file exists, is registered and is listed in the dep file for the second dll.

Why should this sourcefile be invalid?
0
Comment
  • 4
  • 2
6 Comments
 
LVL 20

Accepted Solution

by:
hes earned 100 total points
ID: 7162500
Try deleting the file from the installer project and then add it again, using the full path to the dll
0
 
LVL 17
ID: 7162578
Thanks hes

I have tried that, I can't delete the file itself as it is only in there because it is listed as a dependency of an included file.
I can delete the dependency reference and add the file but it then appears directly under Files. If I then restore the reference it still comes up with the warning.

I have to confess almost total ignorance of vsi, I'm new to it and the documentation seems mostly aimed at telling me how good it is, but very little in the way of how I should be using it. I haven't found very much at all on creating and using merge modules, although what I have read seems to be telling me that I should be using them.
0
 
LVL 17
ID: 7162689
I've been prodding around and I don't know whether this will help you to help me.

If I right-click on the dependancy of one of my files that doesn't show an error it shows the full path - well with some dots and backslashes, but if I view the same information on the offending file then SourceFile is just shown as the filename, no path. At least the error message is beginning to make some sense now.

Can you suggest anything I can do to encourage the SourceFile property to display the path?

I have the code that created the offending file (VB), could it be something I set when I compiled it or built the dep file?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 17
ID: 7164345
I've fixed it/got around it.
Not sure if it's a valid way but it's got rid of the warning.
I opened the dep file (of the project that references the missing file)and added the full dll path in there.
Rebuilt the merge project and the warning has gone.
(Almost what you suggested hes)

I've actually got another problem now, it say's I can't include a dialog in the module - this didn't show up before and looks somewhat like a good place to stop.

Can you suggest a reference or a good book that would explain merge modules or the proper use of vsi?
0
 
LVL 20

Expert Comment

by:hes
ID: 7164987
0
 
LVL 17
ID: 7165024
Thanks for your time hes,

I've actually visited all those references or found them in msdn :(

Never mind though, your first comment put me on the right track, there seems to be a lot more to this subject than the available documentation would have me believe.
0

Featured Post

Free Tool: Postgres Monitoring System

A PHP and Perl based system to collect and display usage statistics from PostgreSQL databases.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction I needed to skip over some file processing within a For...Next loop in some old production code and wished that VB (classic) had a statement that would drop down to the end of the current iteration, bypassing the statements that were c…
Background What I'm presenting in this article is the result of 2 conditions in my work area: We have a SQL Server production environment but no development or test environment; andWe have an MS Access front end using tables in SQL Server but we a…
Get people started with the process of using Access VBA to control Outlook using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Microsoft Outlook. Using automation, an Access applic…
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question