This project has moved. For the latest updates, please go here.

NuGet Package - Assembly not inside a framework folder

Jan 31, 2012 at 9:01 AM

Hi,

the NuGet Package Explorer analysis finds 1 issue: "Assembly not inside a framework folder".

The assembly is placed directly under the 'lib' folder. It is recommended that assemblies be place inside a framework-specific folder.

 

That would also allow to include the 3.5 version within the NuGet package. As an example please have a look at the log4net Nuget package.

Thx,

Peter

Coordinator
Feb 1, 2012 at 4:52 AM

Would you be willing to prepare a package that I can use?

I feel like I'd just create another mess there.

Feb 2, 2012 at 8:47 AM

I will create an issue to upload the package. Only the *-client folders are necessary. Nuget will take the assemblies from the client folder if there is no separate folder also for Full Profile projects.

The easiest way to update the package would be by the NuGet Package Explorer.

 

Feb 5, 2012 at 11:43 AM

Hi,

because of the Name change of the Nuget package (ClosedXML for .NET4 to ClosedXML) you need to uninstall the old Nuget Package and install the new one.

Nuget does not recognise that there is an updated Package.

Thx, Peter