Installing i18n packge via Nuget breaks application

[menaheme]

having problems, just setting things up.

1. i installed the nuget i18n 1.0.8 to an existing MVC4 app , added the entries to the web config and i get the YSOD saying "could not load type 'i18n.LocalizingModule' from assembly i18n". , i looked inside the i18n assembly and indeed the module isn't there.

also ,
2. the post build action was not registered by the Nuget,
3. plus, the post build assembly is built for x86 instead of 'Any', VS warns me about this,(my dev station is x64, and all my projects are 'Any'.)

[turquoiseowl]

v1 on master branch is end of life. Refer to v2 branch for current version. Thanks.

[menaheme]

Using the nuget package from visual studio's package manager. is it
possible to update the package?
On 12 Dec 2013 19:32, "Martin Connell" notifications@github.com wrote:

v1 on master branch is end of life. Refer to v2 branch for current
version. Thanks.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/117#issuecomment-30443503
.

[turquoiseowl]

Not at the moment. To try v2 you need to clone the github project to your local drive and build it. Then reference the i18n.dll produced. We are working on getting v2 onto Nuget.

[krisztianb]

I created a nuget package using the pack-nuget.bat that comes with the module. You can then set up a local nuget source in Visual Studio and install the package this way. I hope this help.

[krisztianb]

And don't forget to manually copy PostBuild.exe into the bin folder of i18n before creating the nuget package. Otherwise you will have to use the path of your i18n folder in the PostBuild action, when specifying the post build event that creates the message files.

[christian-lang-2012]

I have a question actually. My team and I are running Visual Studio 2013 and when we clone the repo and go to build, we get a compatibility error with the POTGenerator even though it is targeting the 4.5 framework and we have a higher Visual Studio version than the one required.
This ONLY happens with the POTGenerator. The rest build just fine.
Can I have an explanation on why this might be?

[turquoiseowl]

Off the top of my head, could it be because the POTGenerator project includes a Visual Studio extension and so is dependent on the version of the VS extension libs? It was originally developed for VS2012. Perhaps you've already thought of that.

Sent from my ZX Spectrum

From: Christian Lang [mailto:notifications@github.com]
Sent: 03 October 2014 21:47
To: turquoiseowl/i18n
Cc: Martin Connell
Subject: Re: [i18n] Installing i18n packge via Nuget breaks application (#117)

I have a question actually. My team and I are running Visual Studio 2013 and when we clone the repo and go to build, we get a compatibility error with the POTGenerator even though it is targeting the 4.5 framework and have a higher Visual Studio version.
This ONLY happens with the POTGenerator. The rest build just fine.
Can I have an explanation on why this might be?

—
Reply to this email directly or view it on GitHub #117 (comment) . https://github.com/notifications/beacon/3240189__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcyNzk4ODM5MCwiZGF0YSI6eyJpZCI6MjE5NTE1MzR9fQ==--bd76e8e2e6f789d3713e171aa4b6d21dbd32870a.gif

[christian-lang-2012]

Do you happen to know what extension it is?
We had actually not thought of that. We went rummaging around the .csproj file a lot to see if that was the main cause of the problem.

[christian-lang-2012]

I just solved the issue actually. Thank you for mention the extensions! I didn't know there was a separate Visual Studio 2013 SDK you had to download and install.
I figured it would've come with it already!

[turquoiseowl]

So I should perhaps add a note regarding this to the README.

Just to confirm, to build i18n in VS2013, one needs the VS 2013 SDK installed. With that, does it build okay?

[christian-lang-2012]

Yeah, you have to do an upgrade to the project, get rid of the reference for Microsoft.VisualStudio.Shell.11 and replace it with Microsoft.VisualStudio.Shell.12. It built just fine after that.

[turquoiseowl]

Great, I've updated the readme accordingly.

[StanleyGoldman]

nuget is still showing 1.0.8...
Did you ever complete the update to the nuget package?

[turquoiseowl]

Sorry, no.