Build Issue in Visual Studio 2010

Question

I cannot build my solution in Visual Studio 2010 without checking out my setup project. Is there something that I can do to rectify this?

Here's the error message:

The command you are attempting cannot be completed because the file 'FooSetup.vdproj' is under source control and is not checked out.

Can you unload the setup-project? – KyorCode Aug 16 '12 at 12:07 — KyorCode, Aug 16 '12 at 12:07

score 2 · Answer 1 · edited Jun 01 '17 at 14:29

2

The issue is because, the file 'FooSetup.vdproj' is not checked out. This means its a Read-Only file.

If you don't want to checkout the file, work offline (without the project being connected to source control)

Its an issue with VS2010 SP1. You can check for any of the workaround mentioned in the Microsoft Connect.

edited Jun 01 '17 at 14:29

Hakan Fıstık

16,800
14
110
131

answered Aug 16 '12 at 12:10

Mohan Kumar

6,008
6
28
36

I have never had to work offline in any other Visual Studio environment (only 2010). I'm not modifying a file, so it shouldn't need to be checked out in order to build. I'm wondering if I have a file checked into the setup that shouldn't be in source control. – jmac Aug 16 '12 at 12:23
@jmac - Can you try it? My guess your trying to compile it. When **this happens vdproj is modified.** either don't build the setup file or remove it. They removed that feature from Visual Studio 2012 for a reason. – Security Hound Aug 16 '12 at 13:42

Hakan Fıstık · Answer 2 · 2018-03-08T19:42:10.420

2

Right click on the Setup Project in the Solution Explorer.
Select Check out for Edit... from the context menu.
Press Check Out button in the window which appeared.

The problem should be solved.

edited Mar 08 '18 at 19:42

answered Jun 01 '17 at 14:32

Hakan Fıstık

16,800
14
110
131

score 0 · Answer 3 · answered Aug 16 '12 at 12:11

0

Setup projects are notorious in being not compatible with source control. If anything in the FooSetup.vdproj needs to/is changed during the build, it will fail with that message.

After each check-in, I always check-out the Setup project immediately. AFAIK it is a PITA.

answered Aug 16 '12 at 12:11

Rudi

3,124
26
35

(See comment above). I'm not modifying the setup, so I don't see why it needs to be checked out. – jmac Aug 16 '12 at 12:23
@jmac - it modifies itself. We are telling YOU THE REASON. – Security Hound Aug 16 '12 at 13:42

score 0 · Answer 4 · answered Aug 16 '12 at 13:04

While doing further research, I found an article explaining that upgrading to SP1 caused this issue and there is a hotfix available. My colleague isn't getting the problem and didn't upgrade to VS2010 SP1.

Here's the excerpt that describes my problem and what is occurring in the setup project:

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.

http://connect.microsoft.com/VisualStudio/feedback/details/650587/vs-2010-sp1-changes-packagecode-in-vdproj-on-each-build-but-fails-as-source-controlled

I am posting an answer to my question in case anyone else is dealing with this issue. — jmac, Aug 16 '12 at 13:06
Microsoft isn't going to fix this problem. They have pretty much stop supporting this feature, in every single version since 2005 had bugs, LOTS of bugs. Setup for this type of project was removed in VS2012 I suggest you find a replacement. — Security Hound, Aug 16 '12 at 13:45

score 0 · Answer 5 · answered Mar 11 '13 at 10:34

0

Microsoft has fixed this issue, the hotfix is available here

MS Connect : http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=35848

Code Gallery: http://archive.msdn.microsoft.com/KB2529927

answered Mar 11 '13 at 10:34

wizzardz

5,664
5
44
66

Build Issue in Visual Studio 2010

5 Answers5