Problems with nuget packages (framework version and localized assemblies)
Hello,
I just began to follow a new Pluralsight course about Humanizer nuget pckg.
I tried to install it in linqpad (instead of making a project in VS) as I usually do when wanting to test nuget packages.
I received a first error
I downloaded a local copy of the nuget package and opened it with Nuget Package Explorer
I supposed the problem could come from the multiple version under the lib folder so I renamed it to net45
I then tried to get my modified nuget package from a local source and it worked!
This workaround is a bit tricky and I hope a solution will come soon in Linqpad in order to be able to tackle this small problem.
Unfortunately, this nuget package comes with a lot of localization satellite assemblies and these are not taken into account by linqpad.
I Hope that this multiple localization sattelite assemblies will also be solved soon as LinqPad has really become my everyday swiss army knive.
Hoping this will help Linqpad to improve a little more
Frederic Hallot
I just began to follow a new Pluralsight course about Humanizer nuget pckg.
I tried to install it in linqpad (instead of making a project in VS) as I usually do when wanting to test nuget packages.
I received a first error
I downloaded a local copy of the nuget package and opened it with Nuget Package Explorer
I supposed the problem could come from the multiple version under the lib folder so I renamed it to net45
I then tried to get my modified nuget package from a local source and it worked!
This workaround is a bit tricky and I hope a solution will come soon in Linqpad in order to be able to tackle this small problem.
Unfortunately, this nuget package comes with a lot of localization satellite assemblies and these are not taken into account by linqpad.
I Hope that this multiple localization sattelite assemblies will also be solved soon as LinqPad has really become my everyday swiss army knive.
Hoping this will help Linqpad to improve a little more
Frederic Hallot
Comments
Thanks for the detailed repro. This has been fixed for the next beta.
Cheers
Joe
Let me know if it fixes the issue described.