Get builds from CI to Nuget/OpenWrap

[m3dwards]

@huboard:{"order":0.25}

[serialseb]

My take on this. OpenWrap is already in charge of building all projects.

To build the nuget package, we'd need a nuspec (ideally in sync with the descriptor, by reading assembly metadata should work just fine), and add a build: instruction in our descriptors that calls nuget.exe to generate the package.

I'd think that ci packages should go on a CI-specific feed (why not use symbolsource.org? They have openwrap and nuget support, and we only need to upload the pdb / source in the openwrap package for those to be picked up by the nuget package).

For non-CI specific code, I'm open to ideas on how the release process would work (tag on master, a r/ branch for releases, a manual build in TC?). Please express opinions on this.

[serialseb]

As an addition, the nuget packages for openrasta components ought to have something in /content to create ConfigurationSource, the asp.net and webforms components ought to have web.config transforms.

Note that I'd rather keep the openrasta-core package without any transforms as it's likely to be used without wanting the /content added. I'd suggest having an openrasta package that contains those and references openrasta-core.

Note that we use different conventions for package names than nuget does, but please keep those conventions as is. OpenWrap does predate nuget and the dot convention is not something i wish to promote.