Sometime back now I posted an article on building .NET and dependency management.
I have come to learn that there are several ways. Here are my favorites.
- Build your own maven plugin to build .NET projects. Package 3rd party products as zips and put them in maven. Write a plugin that reads solution and project files and calls MSBuild with the appropriate flags. Advantage, maximum flexibility. Disadvantage, lots of effort.
- Use the existing maven-dotnet-plugin. Advantage, does a lot for you including various types of test and coverage systems, plus it can run sonar. Disadvantage, Hard to get it to work on complex silverlight projects. In fact hard full stop. The docs are not great.
- Use NuGet. Advantages, it has .NET pedigree and Microsoft Backing. Adoption amongst .net developers is probably an easier sell than a java utility. Disadvantages, Very early days for the project, as yet unproven.
- Finally npanday. Advantages, nice integration with Visual Studio. Disadvantages, very hard to get it to work with silverlight. Impossible in fact as MS have kindly removed the command line baml compile utility.
So in summary. There are ways to do this now. There is hope for .NET dependency management!