1
Vote

Visual Studio 2013 broken?

description

Hi,

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.

Ciao!
Stefan

file attachments

comments

habakuk wrote Aug 19 at 1:03 PM

Here the build output without the nuget package generation.

deadlydog wrote Aug 19 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 at 9:46 AM

Hi, thanks for your answer!

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