Re:Building .NET projects is a world of pain and here's how ...
by maartenba on Friday April 11, 2014 @05:07AM
(#7571896)
Added a P.S. to the post to reflect this: P.S.: A lot of the new packages like ASP.NET MVC and WebApi, the OData packages and such are being shipped as NuGet packages which is awesome. The ones that I am missing are those that require additional build targets that are typically shiipped in SDK's. Examples are the Windows Azure SDK, database tools and targets, ... I would like those to come aboard the NuGet train!
[ Parent
| on HN ]
Re:Building .NET projects is a world of pain and here's how ...
by ygra on Friday April 11, 2014 @05:31AM
(#7571965)
There's nothing technical that would prevent nuget from including MSBuild targets that are then picked up after installing the package, right? (Worst case would be that you'd have to use a wrapper project which gets the dependencies and then builds the actual project, in case project includes are handled before the nuget target.)
Re:Building .NET projects is a world of pain and here's how ...
by maartenba on Friday April 11, 2014 @05:36AM
(#7571976)
True that! And I hope more SDK's are shipped in NuGet packages so we can define explicit dependencies instead of implicit ones.
Re:Building .NET projects is a world of pain and here's how ...
by profquail on Friday April 11, 2014 @08:19AM
(#7572421)
It doesn't seem to have been widely publicized, but as of NuGet 2.5 it's been possible to include custom .targets files in NuGet packages which are automatically pulled into a project when the package is referenced: http://docs.nuget.org/docs/reference/support-for-native-proj...