This project is read-only.

NPanday Advantage over MSBuild

Apr 3, 2009 at 2:10 PM
Hi there,

I come from the java world and I have used maven extensively in my java projects.  Therefore, I'm looking at NPanday/NMaven at the beginning of switching to C# .net.  However, as I gain more knowledge in the C# related build tools, I don't quite understand the need to have a NPanday or NMaven for a project build with Visual Studio.  Although VS is far behind in term of productivity compared with Eclipse, I think from a dependency management point of view, dot Net has its advantage over Java.  A project maintains a versioned list of dll dependencies natively.  It also seems to handle transitive dependency.  As for CI, cruise control .net integrates with MSBuild.exe quite well.  Can someone please point out what NPanday or NMaven provides? 



Apr 3, 2009 at 2:14 PM
I should have read the post before I started this new one:

Q: Why use NPanday when you can build .Net Applications in VS?
A: NPanday aims for Continuous Integration and Artifact Management for your .Net Applications using Open Source Technology, by using NPanday you can take advantage of existing development infrastructure that is compatible with Maven.

As I said CI can be done with MSBuild.  Is Artifact Management the only advantuage NPanday/NMaven provides? 
Apr 3, 2009 at 2:37 PM
On Fri, Apr 3, 2009 at 6:15 AM, [email removed] wrote:

> As I said CI can be done with MSBuild.  Is Artifact Management the only
> advantuage NPanday/NMaven provides?

The shared artifact repository is huge advantage. Prior to adopting
NPanday, a team I work with was _emailing_ new dlls around to
developers. Reuse was difficult since there was nowhere you could go
to find out if what you wanted already existed within the

Maven and NPanday encourage following conventions, such as versioning
your artifacts, and following a release process to tag the repository
and build from a clean checkout. Before, no one was changing the
version number, they'd just build 1.0 over and over, and it was
difficult to find the exact code that was running in production.

Just as you can do everything with Ant that you can do with Maven, you
can do it with MSBuild, too, it just takes more discipline.