index > ClickOnce and Setup & Deployment Projects > Bug in "Detected Dependancies" does not update when you switch solution configurations

Bug in "Detected Dependancies" does not update when you switch solution configurations

If you have VS open and your solution in Debug mode, the "Detected Dependancies" point to the Debug directories. If you switch the project to Release, the Detected Dependancies don't change to point to the Release directories even if you "Refresh Dependancies"

bpeikes Thursday, July 09, 2009 1:46 PM

Hi,

Based on my understanding, you have a solution with two projects. One project is a Winform application project and the other is a Setup project. You add the primary output from the Winform application project to the Setup project. When you change the solution configuration to Release, the items under the Detected Dependencies within the Setup project still point to the files under the Debug directory. If I'm off base, please feel free to let me know.

I performed a test on this issue and did reproduce the problem on my side. When we add a primary output from a project and set the Configuration to Release, the configuration only applies to the primary output of that project. This won't affect the dependencies. Any way, the dependencies under the Debug and Release folder are the same.

Sincerely,
Linda Liu

Please remember to mark the replies as answers if they help and unmark them if they provide no help. end us any feedback you have about the help from MSFT at fbmsdn@microsoft.com.

Marked As Answer byLinda LiuMSFT, ModeratorMonday, July 13, 2009 2:43 AM
Unmarked As Answer bybpeikes Monday, July 13, 2009 1:11 PM

Linda Liu Friday, July 10, 2009 10:50 AM

Yes. That is the problem. Is there a hot fix? It's really a pain to have to exit Visual Studio each time we prepare to make a release. In order to create a setup using Release libraries, we have to switch the project to Release mode, exit Visual Studio, open Visual Studio with the solution already in Release mode, then Rebuild all.

bpeikes Monday, July 13, 2009 1:10 PM

Hi Bpeikes,

In my previous test, what I changedwas the "Configuration" in the Add Project Output Group dialog when adding a project output into the Setup project. I perform another test and in this test I change the active solution configuration in the Configuration Manager dialog. This time, I don't reproduce the problem you describe on my side.

Please have a try rebuilding the Winform application project after changing to Release in the Configuration Manager and then refreshing the detected dependencies in the Setup project.

Please remember to mark the replies as answers if they help and unmark them if they provide no help. end us any feedback you have about the help from MSFT at fbmsdn@microsoft.com.

Linda Liu Thursday, July 16, 2009 3:12 AM

Here are the steps to create the situation that sometimes causes the bug that I am seeing.

Create a solution called TestSetupProjectApp
Add a WinForms project called TestSetupProjectBugApp
Add a Class Library project called TestSetupProjectBugLib
Add code to the Program.cs in TestSetupProjectBugApp to call the constructor of Class1 in TestSetupProjectBugLib
Reference TestSetupProjectBugLib from TestSetupProjectBugApp
Add a new Setup Project to the TestSetupProjectBugApp solution called TestSetupProjectBugSetup
Add Project Output using the Primary output of TestSetupProjectBugApp
Build in Debug mode.
Refresh the "Detected dependancies" of TestSetupProjectBugSetup.
There should now be an entry for TestSetupProjectBugLib.dll. View the properties for that "Detected dependancy" and you should see the Source Path attribute as something like "U:\My Documents\Visual Studio 2008\Projects\TestSetupProjectBugApp\TestSetupProjectBugLib\bin\Debug\TestSetupProjectBugLib.dll"
Switch project to Release mode.
Rebuild solution.
Now look at the "Source Path" attribute for the TestSetupProjectBugLib.dll under "Detected dependancy". This will be "U:\My Documents\Visual Studio 2008\Projects\TestSetupProjectBugApp\TestSetupProjectBugLib\bin\Release\TestSetupProjectBugLib.dll"
Now switch to Debug mode.
Rebuild solution.
Now look at the "Source Path" attribute for the TestSetupProjectBugLib.dll under "Detected dependancy". This will be "U:\My Documents\Visual Studio 2008\Projects\TestSetupProjectBugApp\TestSetupProjectBugLib\bin\Debug\TestSetupProjectBugLib.dll"
So far everything is working how it should.

The problem is that in some of my solutuions, you switch from Debug to Release mode, the "Source Path" for libraries under "Detected dependancy" don't change. I can send you an example of a solution in which has the bug if you give me an email address.

bpeikes Thursday, July 16, 2009 2:02 PM

Hi Bpeikes,

Please send your solution to my email box v-lliu@microsoft.com.

Thanks,
Linda Liu

Please remember to mark the replies as answers if they help and unmark them if they provide no help. end us any feedback you have about the help from MSFT at fbmsdn@microsoft.com.

Linda Liu Friday, July 17, 2009 3:02 AM

Tried to send to your email address twice. Once to v-lliu@microsoft.com which got rejected:

v-lliu@microsoft.com on 7/17/2009 9:27 AM

The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.

< mail118-tx2-R.bigfish.com #5.0.0 X-Postfix; message size 13215367 exceeds size limit 10485760 of server winse-6216-mail2.customer.frontbridge.com[205.248.106.30]>

And lliu@microsoft.comm which got rejected with this message:

Your message did not reach some or all of the intended recipients.

Subject: Bug in "Detected Dependancies" does not update when you switch solution configurations

The following recipient(s) cannot be reached:

lliu@microsoft.com on 7/17/2009 9:31 AM

There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.

<exfront03-pdx.smarsh.com #5.5.0 smtp;554 <lliu@microsoft.com>: Recipient address rejected: Access denied>

bpeikes Friday, July 17, 2009 1:54 PM