VS 2010 SP1 changes PackageCode in .vdproj on each build, but fails as source controlled - by AdamRobertson

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 650587 Comments
Status Closed Workarounds
Type Bug Repros 91
Opened 3/10/2011 3:50:23 AM
Access Restriction Public


I have just upgraded from VS 2010 to VS 2010 SP1 and I now run into an "infinite loop" of dialog boxes when building a setup (.vdproj) project that is under source control.  If the .vdproj is not checked out and I build up the project I get a message when it starts building the setup project saying "The command you are attempting cannot be completed because the file 'XXX.vdproj' is under source control and is not checked out."  There are ok and help buttons on the dialog, but if I press the ok button the dialog just closes and reappears.  I have to then use task manager to kill devenv.exe.

If I check out the .vdproj before doing the build I can see that the file is changed.  It will always change the PackageCode property of the installer, but will sometime also reorder various parts of the file.

My problem is that in all previous versions of VS, simply building up the installer didn't make a change to the file and I don't want to have to have my setup projects checked out all the time to be able to build them up.  I also have a scripted build that runs devenv and this fails for the same reason as above.
Sign in to post a comment.
Posted by msbyuva on 8/30/2012 at 8:14 AM
Sorry, I found the Hotfix.. was looking in to wrong link.... Thanks.. its fixed now I don't see dialog boxes when I build Solutions...
Posted by msbyuva on 8/30/2012 at 7:29 AM
I could not find the hotfix, it says page not found.. Please give me a link from where I can download the required hotfix.
Posted by pravek on 8/15/2012 at 9:59 AM
I installed the hotfix and resolved the problem. Thanks alot.
Posted by Arthg on 5/18/2011 at 11:20 AM
I got lucky. Today I experienced the issue of "infinite dialogs", and indeed the hotfix solved the issue. Thanks to all the teams that had to suffer through without a hotfix.
Posted by Microsoft on 5/9/2011 at 11:39 AM
Thank you for the confirmation. We'll go ahead and close this issue.
Posted by alaa9jo on 5/4/2011 at 10:10 PM
It seems this hotfix fixed the issue,it's working now!
Posted by Rahul Techie on 5/3/2011 at 4:06 AM
Thanks, this Hot fix really solves my issue.
Posted by AdamRobertson on 5/3/2011 at 4:00 AM
That's great Microsoft, things are now working for me. Thanks for the fix.
Posted by Ilpo Juvander on 5/2/2011 at 5:24 AM
Yes, working
Posted by Max Oleznyuk on 5/2/2011 at 12:59 AM
I've hust tested it. The bug is fixed. Thanks!
Posted by Maximilian Haru Raditya on 5/1/2011 at 9:10 AM
I just tested it and it seems this has been fixed.

Posted by Microsoft on 4/29/2011 at 4:51 PM
The hotfix is now published to public channel on Connect and CodeGallery. Below are the links:

MSConnect: http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=35848
Code Gallery: http://archive.msdn.microsoft.com/KB2529927

Please let us know if you have any questions or further issues. Thank you for your support.
Posted by Bob Riddle on 4/29/2011 at 7:37 AM
We just made the mistake of installing the service pack. Now all of our builds fail exactly as described. We also need a fix, and relatively quickly to avoid impacting deliveries.
Posted by mamikel on 4/27/2011 at 10:40 PM
Oh you lucky person who only has to click 15 times, I have to click 230+ times.
Posted by AdamRobertson on 4/18/2011 at 8:14 AM
Thanks Microsoft, this is finally good progress. I look forward to the end of the month.
Posted by Microsoft on 4/15/2011 at 5:08 PM
A quick update on our investigation. We have identified the root cause of the issue and confirmed that this is a regression in VS2010 SP1. The temporary workaround for this issue is to manually check out the setup project file (.vdproj) prior to building and revert back after the build is completed. This problem also impacts people who are using VS2010 (without SP1) and have installed the hotfix KB2418919. We are diligently working on producing a hotfix for this issue for VS2010 SP1 and expect to have it released to the public by the end of this month. We are also expecting to release a separate hotfix for people who are using VS2010 with KB2418919 installed by the end of May.

We will send out a link to the hotfix when it becomes avaliable. Thanks again for your patience.
Posted by Microsoft on 4/13/2011 at 5:55 PM
Hi all,

We apologize for the delayed response on this issue. We are able to reproduce this and are investigating on the problem. Please expect an update from us before the end of this week.

Thank you for your patience.
Posted by Gary Fletcher on 4/12/2011 at 8:06 AM
This bug report is a month old and in that time we have seen no movement on this issue. You promised a follow up on 3/17 and we've received nothing. Come on Microsoft - would it kill you to give us a status report? If I ignored my customer's support requests for a month I wouldn't have any customers....
Posted by AdamRobertson on 4/12/2011 at 4:23 AM
This item is now the 8th most voted active bug on the MS Connect site. It was raised over a month ago and MS last commented nearly 4 weeks ago when a smaple project and clear steps to repeat were posted. 60 users report that they can reproduce the problem, probably meaning that at a minimum 60 projects are suffering because of this bug.

What is it going to take to get any further engagement from Microsoft on this issue?
Posted by tonbr on 4/8/2011 at 1:49 AM
Encountered the same problem. I wasn't paying attention to the error since I expected that a build wouldn't want to change any files. Indeed the resulting MSI does not contain all the files. My users reported back receiving the following error:

"The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2709."

Checking out the vdproj file prior to build solves the problem, but is annoying.
Posted by herlihyboy on 4/7/2011 at 12:36 PM
"the optimum workaround is to uninstall SP1 and everything is back to normal."

And yet, when you begin to uninstall SP1, you are highly warned that this may cause serious issues. Which is the greater evil?
Posted by FabioBo on 4/4/2011 at 4:20 AM
I also have same issue, i was running 2010 without SP1
Posted by learnerplates on 4/1/2011 at 9:02 AM
me too me too please. clicking 15 dialogs makes my day.
Posted by AdamRobertson on 4/1/2011 at 7:40 AM
This is now the 14th most voted bug - 57 people have said they think this is worth looking at, and 41 user have reproduced the problem. Please could we have a status update at the least.
Posted by dennisgorelik on 3/31/2011 at 12:48 PM
Setup Project was always shaky, but with Visual Studio 2010 SP1 it got even worse.
Compilation should not change source code.
This is very serious bug from MS.
Posted by AdamRobertson on 3/31/2011 at 2:23 AM
Any news on this Microsoft?

I've just checked and as of 9:20 GMT today this issue is the 17th most voted bug out of 254. At the very least can you provide a status update. Have you been able to reproduce this now? Do you think you will be able to fix this and issue a hotfix? If so how long will this take?
Posted by Davd A on 3/30/2011 at 4:02 AM
I cannot explain in words how annoying this new behaviour is and how much time we wasted on it today. (I know that does not help get the problem resolved but one little software engineer is feels a little better.)
Posted by Brian Bagley on 3/29/2011 at 6:54 AM
Hello MS, it has been more than 10 days and no response. This is preventing us from rolling out SP1 to our users and our build servers. Please provide an update on the status of this issue. Just information would be appreciated at this point in time.
Posted by Maximilian Haru Raditya on 3/28/2011 at 11:56 PM
I think the main point of the issue here is that VS2010SP1 DOES CHANGE a setup configuration project (.vdproj) every time it's being built, when it SHOULDN'T do that. This change in behavior is certainly a breaking change from VS2010 (and all previous VS versions) due the fact that VS doesn't change a setup project when it's being built.
Further, changing the setup configuration project causing it to be checked out from a source control (if it's a source-controlled setup project) either one using TFS, SVN, or others.

The most unbelievable thing here is that MS can't repro this change behavior, and they remain silent until now... >:(
Posted by ppfeifer on 3/28/2011 at 2:09 PM
We're having the same problem. Our workaround is to go into explorer and make the setup project file readable. This is not a good long term solution, though.
Posted by Ilpo Juvander on 3/28/2011 at 1:55 AM
Thanks AdamRobertson for the note on the scripted build.

Now all our Release builds are built with cmd file like this:

"C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.com" "Solution.sln" /Rebuild "Release|Mixed Platforms"

No prompting, everything as it was before!
Posted by AdamRobertson on 3/25/2011 at 2:50 AM
Come on MSFT - You've had my steps to repeat for a week now (and even these were blindingly obvious and could have been deduced from the initial description of the problem) and at least 22 other users can also repeat the problem. Can you provide some feedback as to whether you've been able to repeat the problem, whether you'll be able to fix the problem and if so what sort of timescale for the fix should we expect.
Posted by Ken Layton on 3/23/2011 at 10:00 AM
This issue is especially annoying when your setup project references multiple merge module projects. Please fix this ASAP.
Posted by Max Oleznyuk on 3/23/2011 at 1:14 AM
We have the same problem.
Posted by Daniel Schmitz on 3/23/2011 at 12:36 AM
Same issue here!
Posted by Vladimir Stepa on 3/22/2011 at 12:57 AM
We have to break our build processes after update on VS2010 SP1. We trifle a lot of man power away.
Please fix the bug.
Posted by Browserboy on 3/21/2011 at 12:34 PM
We are having the same issue. It's killing us. Please keep us posted on a possbile work around or fix.
Posted by Microsoft on 3/17/2011 at 10:11 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by AdamRobertson on 3/17/2011 at 4:58 AM
Oh, and I created this with VS 2010 SP1:

Microsoft Visual Studio 2010
Version 10.0.40219.1 SP1Rel
Microsoft .NET Framework
Version 4.0.30319 SP1Rel

If you need more details of the other information from Visual Studio's Help -> About, let me know.
Posted by AdamRobertson on 3/17/2011 at 4:56 AM
I have attached (twice actually - I think I was impatient with the upload, whoops) a very simple sample project that demonstrates the problem. I created it in the following way:

1) Created a new WPF Application project into a new solution and marked it to be source controlled
2) Added a Setup Project to the solution
3) Edited the Release build configuration to build up the Setup Project
4) Added the Primary Output of the WPF Application project to the Setup Project
5) Checked in the entire solution
6) Tried to build the solution in the Release configuration. Got the same errors as before.

Just to stress, there isn't a problem when the solution isn't source controlled or the Setup Project is checked out. But if it is checked in you get the problem.
Posted by Microsoft on 3/17/2011 at 12:42 AM
Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team

Posted by Maximilian Haru Raditya on 3/16/2011 at 6:09 PM
This is certainly broken, and needs to be fixed ASAP.

But MS has not confirmed this yet. So, what do you think, MS?
Posted by Ken Layton on 3/16/2011 at 4:54 PM
I can't understand how this is not urgent. If broken product is not urgent what is?
Posted by JonathanPugh on 3/16/2011 at 4:13 PM
I also am getting this exact same error right after upgrading VS2010 to the final release of SP1. I have a lot of setup projects in my solution so this is quite annoying. Need fix ASAP?
Posted by Ilpo Juvander on 3/16/2011 at 7:11 AM
Very annoying feature, no issues with SP1 beta, this came with release version of SP1
Posted by BenoitA on 3/15/2011 at 4:54 AM
Same issue here. Will be really annoying.
Posted by Microsoft on 3/10/2011 at 9:19 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Brian Bagley on 3/10/2011 at 6:45 AM
One more thing, when the .msi is built it is not including all of the files that are normally packaged as part of the process.
Posted by Brian Bagley on 3/10/2011 at 6:43 AM
I also have this same issue, I was running SP1 beta with no issues prior to installing the release version of SP1.
Posted by AdamRobertson on 3/10/2011 at 4:16 AM
As an update to this, I have been able to reproduce the issue with mulitple solutions. However, it turns out that the number of dialogs that pop up saying the comand can't be completed because the file is under source control isn't "infinite", its just very big - possibly even the number of items in the setup project including detected dependencies. I patiently pressed the ok button for some time and eventually the build went through and succeeded.

I have also found the the scripted build doesn't error due to this problem. Perhaps all the dialogs are suppressed (as I run the build from a CruiseControl.Net service and so devenv is headless) and so VS carries on regardless.

Either way, it is still bloomin' annoying to have to repeatedly click ok for a few minutes on every release build.
Posted by Microsoft on 3/10/2011 at 4:13 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)