undefined | Better HN

0 pointstieTYT12y ago0 comments

Yes but I thought everyone uses VS for .NET development? Am I wrong about that? If I'm right, your point is kind of moot.

0 comments

3 comments · 1 top-level

edwinnathaniel12y ago· 2 in thread

VS.NET comes in many editions with some limitations.

For example: VS.NET Express does not allow you to have any plugins (or used to, never checked anymore) which means you can't run your NUnit from there and expect code-coverage instantly show up once you ran them.

Their NuGet solution somehow seems limited compare to Maven eclipse plugin where it can download the JAR, JavaDoc, and Source if required whenever someone needs to navigate the source code of 3rd-party lib.

brimanning12y ago

You shouldn't be using the Express version for professional development anyway, you really need to use the paid version - that's a whole different Java vs .NET debate running into OS vs proprietary that will never end.

As for NuGet, as soon as you build, all code, docs, etc are right there and it's up to the creator of the library to have created the info. It manages versioning and updating for you as well.

edwinnathaniel12y ago

Excellent, I didn't know that (about NuGET), here's the link for those who are interested to know how to set it up:

http://blog.davidebbo.com/2011/04/easy-way-to-publish-nuget-...

Unfortunately the whole debate of OSS vs Proprietary does matter when it comes to "which tools is better". I know it'll never end but it affects the playing fields.

The fact that you can get up to speed very very quickly without spending money or talking to Finance, MS Sales/re-sellers using Eclipse+plugins and Java+OSS libraries/frameworks that were more mature is probably a significant point on this debate.

1 more reply

j / k navigate · click thread line to collapse