I use NuGet internally as a repository of frequent used modules. These modules often have dependencies to other modules. Every module might have a collection of aspx/ascx. Then I use the option provided by nuget.exe to pack a project as a nuget package.
'nuget.exe pack' takes the packages.config, project.nuspec and project.csproj in consideration when creating the package. Now Im facing a problem with having the same 'content' in multiple packages - this might be a problem when upgrading at a later stage.
Create a Project-A.csproj with a page: pageA.aspx
Now; create Project-B.csproj with a page; pageB.aspx, and add package Project-A.nupkg
This might lead to a problem when updating at a later stage, but if adding a package added content with BuildAction=None pageA.aspx would not become a part of Project-B.nupkg and problem is solved.
There might be problems related to adding content with BuildAction=None, but I would guess that if there are content from a package that required compilation that the content is already compiled into the assembly.
Is this an issue anyone else are experiencing or am I the only one using NuGet like this?