This project has moved and is read-only. For the latest updates, please go here.


Visual Studio 2013 broken?



I tried to include your script in a Visual Studio 2013 project, but always get the error that the output path cannot be determined.

See attached build output.


file attachments

Closed Apr 13 at 7:10 AM by deadlydog
The new New-NuGetPackage.ps1 v1.5.8 (and CreateNewNuGetPackageFromProjectAfterEachBuild NuGet package v1.8.10) now includes the required -ForceEnglishOutput parameter to NuGet.exe, so this problem should be resolved. NOTE: The -ForceEnglishOutput parameter is only supported by NuGet.exe v3.5.0+, so be sure you are using at least that version of the NuGet.exe.


habakuk wrote Aug 19, 2014 at 1:03 PM

Here the build output without the nuget package generation.

deadlydog wrote Aug 19, 2014 at 6:43 PM

It looks like the problem is that I don't support your language yet :P The script relies on some strings that are returned from the NuGet.exe, and these strings change depending on your operating system's language. Because I have to match some strings, such as the one that tells me where NuGet.exe output the .nupkg file to, when it can't match the string because the language is unexpected, the script spits out an error.

I had made changes to the script to make localization easier, but it's still a manual process of having to add in every language that I want to support, which involves changing the OS version, and executing all of the relevant NuGet.exe commands and recording the output it spits out. So it's not just a quick and easy process.

Which language are you using?

habakuk wrote Aug 21, 2014 at 9:46 AM

Hi, thanks for your answer!

My system language is German and I use a English Visual Studio.

deadlydog wrote Jan 23 at 3:10 AM

I believe this problem should now be solved using the CreateNewNuGetPackageFromProjectAfterEachBuild NuGet package v1.8.10 or greater. Can you please give it a try and let me know if it now works as expected. Thanks.