Re:Building .NET projects is a world of pain and here's how ...
by JonoW on Friday April 11, 2014 @06:08AM
(#7572057)
I think they just need to separate out the tools from the libraries, within the SDKs, i.e. all libraries through NuGet, everything else can still be an Msi, as a dev will need things like emulators and VS tooling add-ins, but none of this is needed for build server just to build the project
Re:Building .NET projects is a world of pain and here's how ...
by chton on Friday April 11, 2014 @06:15AM
(#7572066)
I whole-heartedly agree. It does create some danger there of mismatching versions between the tooling and the nuget packages. What do we do if the user has upgraded to a newer version of the package, but hasn't updated his emulator yet? Vice versa is somewhat easier to enforce, but either way it will require careful checking and notifying of the devs.
Re:Building .NET projects is a world of pain and here's how ...
by mattmanser on Friday April 11, 2014 @09:02AM
(#7572582)
https://www.nuget.org/packages/AWSSDK/
https://www.nuget.org/packages/Box.V2/
https://www.nuget.org/packages/DeveloperForce.Common/
https://www.nuget.org/packages/Atlassian.SDK/3.0.0-beta1
Random enterprise names I picked out off the top of my head.
It's not just Microsoft though. Other vendors need to jump on the same bandwagon. Right now, almost nobody really does, definitely nobody who sells to the enterprise market.