Publishing project with MSBUILD

I am running msbuild on our build server, the server has the .NET v2 beta 2 runtime and SDK installed, it does not have DEVENV installed on it.

When I try to publish the project with msbuild from the command line on my local PC that has DEVENV installed it all seems to work.

When I try running the some command on the build server I get:

“C:\WINNT\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets : warning MSB3482: SignTool reported an error 'SignTool.exe not found.'.”

The command line I am using is:
%windir%\Microsoft.NET\Framework\v2.0.50215\MSBuild.exe StudentAllocator.sln /p:Configuration=Release /property:ApplicationVersion=0.0.0.1} /t:SamClient:publish /t:AdministratorClient:publish'

Before hitting this problem I found that MSBUILD would not work without the SDK installed, that I found a bit odd, as MSBUILD is included in the runtime. What else do I need to install

Ian Ringrose
www.ringrose.name <- email on website

Answer this question

Publishing project with MSBUILD

Ashish Kumar
I have openned a bug, see FDBK33957
Mick McGrellis
Ian,
Would you mind opening a bug on this at http://lab.msdn.microsoft.com/productfeedback/ Please include all the repro steps and your configuration.

From a quick look at the current code, it seems like it should find the tool. Opening a bug will route your report to the right person in the VB team, who own the task that is calling signtool.exe.

I wish I had time to investigate this more myself right now but it would be better to open a bug.

Thanks
Dan
DerikMHinz
I have got the SDK installed. However MSBUILD can not find SignTool.exe
IanTP
I thought VS was needed for running unit and web tests during the build. Is that part of the SDK now
JasonRiccio
Ian,
I am also getting the same problem with msbuild.exe and I do not have VS 2005 installed on my machine. I have sm.exe in directory C:\Program Files\Microsoft SDKs\WinFX\bin but still I am getting the same warning during compile time. Can you provide more details on this.

Navneet Gupta
Ajit Porlekar
You should definitely not have to install Visual Studio on your build server. That was one of our original goals for MSBuild.

Not every tool used by the common targets ships in the .NET Framework redist, so some projects will need the .NET SDK installed as well. Examples include signtool.exe and lc.exe (license compiler). Note: resgen.exe is not shipped in the .NET redist, but we got around that by packaging our own replacement task called GenerateResource that does not need resgen but works the same.

Typical winforms projects and such should build fine without even the .NET SDK. The SDK may be needed to publish though, for things like signtool. I'll check exactly when signtool is used.

Dan
(msbuild@microsoft.com)
Eli Lopian
Thanks Ian.
lochew
Dan,

Please see the post marked as answer in this thread:

http://forums.microsoft.com/msdn/ShowPost.aspx PostID=17644

It states that VS needs to be installed on the build server, can you please verify

Thanks!
mGreenway

It seems that sm.exe is not included in the "standalone" sdk but is included in the sdk that is installed by msdev.

When I copied sm.exe into the sdk/bin directory on my build machine the build worked ok
brsrkr
You need to install Visual Studio on your build server as well. It is required in Beta 2 for some build tasks. I am not sure if it is going to be a requirement in the RTM version though.
AndySchumann
Note I believe we had a report of these problems in the past, and you should try with the RTM version of the framework. I'm 99% sure it works fine in RTM.

Neil
Publishing project with MSBUILD

Answer this question