Add ability to build a "partial" prerelease package (for native code)

[bbowman]

For the NuGetizer project or similar VS build integration of package creation, it is necessary to allow the creation of a partial package. MsBuild by default operates on a specific build configuration that specifies the target platform and configuration for a build (Debug|x86 for example). Therefore it is most common that a developer building locally will only build for one "flavor" of a package that could be consumed across platforms, configurations, etc.

To make it easier to integrate with builds and easier to consume "just built" components, I propose the ability to create a partial package that would only contain the newly built bits for a given build configuration. Ideally this partial packaging step would only work when operating with prerelease packages as an official release would obviously need to be the full package. Using the prerelease string could also make it easier to produce well formed and easily identifiable partial packages based on what was built.

The current .nuspec schema seems insufficient with replacement tokens to have the duality of a partial package or full package be built. I'm not exactly sure how the schema could be expanded to express this and how it would integrate with VS / NuGetizer but this would be a valuable feature for rapid developement.

https://github.com/NuGet/Home/wiki/NuGetizer-Future-Features seems like it is starting to think about this however the sub-projects for each platform would be a little rough for normal VS development as it abuses the idea of a buildConfiguration and would slow down development by always building all configurations which may not be desirable.

Thoughts?

[yishaigalatzer]

@rohit21agrawal @kzu

[bbowman]

@rohit21agrawal I know there is some cross targeting work going on. Any thoughts here on how it could relate?

[jainaashish]

@rohit21agrawal Lets discuss plan for native projects pack.