Warnings during building of NuGet packages

[GoogleCodeExporter]

What steps will reproduce the problem?

1. hg clone http://code.google.com/p/elmah.pkg/
2. Run pack.cmd in the root of the working directory.

What is the expected output? What do you see instead?

Expect packaging to take place without errors and warnings. Instead several 
warnings are issues:

WARNING: 1 issue(s) found with package 'elmah.corelibrary'.
WARNING: 2 issue(s) found with package 'elmah.postgresql'.
WARNING: 3 issue(s) found with package 'elmah.sqlite'.

See attached log for full details.

P.S. The packages do install fine.

Original issue reported on code.google.com by azizatif on 18 Jan 2012 at 6:58

Attachments:

• log.txt

[GoogleCodeExporter]

All warnings are correct in terms of how NuGet works (and in the vast majority 
of cases, they are probably valid). However, I don't believe that they are 
applicable to ELMAH.

1) WARNING: 1 issue(s) found with package 'elmah.corelibrary'.

Issue: Assembly not inside a framework folder.
Description: The assembly 'lib\Elmah.dll' is placed directly under 'lib' 
folder. It is recommended that assemblies be placed inside a framework-specific 
folder.
Solution: Move it into a framework-specific folder. If this assembly is 
targeted for multiple frameworks, ignore this warning.

> ELMAH *IS* targeted for multiple frameworks!

2) WARNING: 2 issue(s) found with package 'elmah.postgresql'.

Issue: Assembly not inside a framework folder.
Description: The assembly 'lib\Mono.Security.dll' is placed directly under 
'lib' folder. It is recommended that assemblies be placed inside a 
framework-specific folder.
Solution: Move it into a framework-specific folder. If this assembly is 
targeted for multiple frameworks, ignore this warning.

Issue: Assembly not inside a framework folder.
Description: The assembly 'lib\Npgsql.dll' is placed directly under 'lib' 
folder. It is recommended that assemblies be placed inside a framework-specific 
folder.
Solution: Move it into a framework-specific folder. If this assembly is 
targeted for multiple frameworks, ignore this warning.

> Again, as per 1) I believe that these assemblies target multiple frameworks

3) WARNING: 3 issue(s) found with package 'elmah.sqlite'.

Issue: Assembly outside lib folder.
Description: The assembly 'NativeBinaries\x64\System.Data.SQLite.DLL' is not 
inside the 'lib' folder and hence it won't be added as reference when the 
package is installed into a project.
Solution: Move it into the 'lib' folder if it should be referenced.

Issue: Assembly outside lib folder.
Description: The assembly 'NativeBinaries\x86\System.Data.SQLite.DLL' is not 
inside the 'lib' folder and hence it won't be added as reference when the 
package is installed into a project.
Solution: Move it into the 'lib' folder if it should be referenced.

Issue: Unrecognized PowerScript file.
Description: The script file 'Tools\GetPostBuild32v64BitCmd.ps1' is not 
recognized by NuGet and hence will not be executed during installation of this 
package.
Solution: Rename it to install.ps1, uninstall.ps1 or init.ps1 and place it 
directly under 'tools'.

> This is our current workaround to get 32/64 bit deployments of SQLite

Original comment by jamesdriscoll71 on 18 Jan 2012 at 8:30

• Changed state: WontFix