Question

I have this nice little MSBuild-based daily build setup that I use on my personal projects. It checks out my code, builds it, then invokes devenv.exe on my project to build my VS setup project.

It has always worked swimmingly, until, well, yesterday. Now, whenever it tries to invoke devenv.exe, the VS 2008 installer comes up, and I have to physically click “Cancel” to make it go away, at which point, the build resumes and finishes without any problems.

The only difference between before, when it worked, and after, when it stopped working, is that I traveled to a different location and am using a different wireless network.

Here is part of my script:

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <Import Project="$(MSBuildExtensionsPath)\MSBuildCommunityTasks\MSBuild.Community.Tasks.Targets"/>

  <PropertyGroup>
    <VisualStudio9>"C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe"</VisualStudio9>
    <StagingPathBetaPro>BetaPro</StagingPathBetaPro>
    <CheckoutPathBetaPro>CheckoutTrunk</CheckoutPathBetaPro>
  </PropertyGroup>

  <Target Name="BetaPro">

    <!-- snip -->

    <Exec Command="$(VisualStudio9) $(StagingPathBetaPro)\$(CheckoutPathBetaPro)\MyProject.sln /Build Release-Beta-Pro /Project Setup-Beta-Pro"/>

    <!-- snip -->

  </Target>
</Project>

Has anyone seen anything like this?

Answer 1

What happens if you open that solution in Visual Studio? Does the installer popup?