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
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)
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
