MSBuild command line execution of Visual Studio 2010 Solution fails referencing VS2010 SDK to build an extension?

Up vote 2 down vote favorite share g+ share fb share tw.

Scenario Solution that has a VS2010 extension in it (.NET 4 Class library, with a WPF UI) It builds fine inside visual studio On the same machine when I attempt to build it via command line (as part of a build script) Fails when using this command to attempt to build it: msbuild JsExt. Sln /t:Build /p:Configuration=Debug /p:OutDir=..\..\Binaries Update To MSBuild Adding /property:VsSDKInstall="C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\VSSDK" leads to this exception... Exception The "VSCTCompiler" task failed unexpectedly. C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\VSSDK\Microsoft.VsSDK.Common.

Targets(74,5): error MSB4018: System. ArgumentNullException: Value cannot be null. Extra info Visual Studio 2010 SDK SP1 is installed The path to and file Microsoft.VsSDK.Common.

Targets does exist. I'm running from an x86 console and PowerShell window and vcvarsall. Bat (x86) are loaded I'm not sure what the tmp_proj is about.

It's a WPF User Interface, is there something I'm missing to compile something with WPF/XAML via MSBuild? There is nothing pre/post build events of the CSProj file that is the extension. Build platform target is Any CPU I have other solutions/projects working well with the same MSBuild command.

Setting /v:diag doesn't offer much more information on the errors. Any ideas, what am I missing, what's next to debug? Wpf visual-studio-2010 .

Net-4.0 msbuild visual-studio-extensions link|improve this question edited Dec 21 '11 at 1:29 asked Dec 21 '11 at 0:02Nick Josevski8061920 71% accept rate.

Are you calling: '"C:\Program Files\Microsoft Visual Studio 10.0\VC\vcvarsall. Bat" x86' in your build script? – DaveShaw Dec 21 '11 at 0:12 @DaveShaw yes, they are loaded, confirmed by running it explicitly before executing the build command, still fails with same exceptions – Nick Josevski Dec 21 '11 at 0:19 Sorry then, that was my only idea – DaveShaw Dec 21 '11 at 0:41.

VSSDK100Install=C:\Program Files (x86)\Microsoft Visual Studio 2010 SDK SP1\ If so, then add "/v:diag" to your cmd line to see what that turns up. Take a look at the following blog post - step #3 sounds like your original issue, and step #4 explains the subsequent VSCTCompiler issue that you just encountered.

It wasn't but I supply it via the msbuild command variables, I'll update the question, as now there's another error showing up - The "VSCTCompiler" task failed unexpectedly. – Nick Josevski Dec 21 '11 at 1:20 Apparently some VSSDK tasks still require the VsSDKInstall path to be set as environment variable. – ArPharazon Dec 21 '11 at 2:24.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.