NuGet uninstaller package and dependencies everywhere

Why is Maven not necessary in .NET?

I agree with many of the answers here. .NET doesn't have a large number of independent IDEs, Visual Studio to write your code, manage dependencies etc. The solution in VS is good enough for MSBuild, so that's what you get from the build server.

Java on the other hand developed lots of Java IDEs and went a stretch of projects with external ones from the IDE. Liberate the developer to your IDE of choice. I've recently started cross training from C # into Java and I can tell you the maven build concept is completely alien, but then after a while, I love it, and more importantly, I see what the repo- Concept offers me.

Well, how the VS manages dependencies requires adding either a project reference or a reference to a DLL. Adding the DLL reference is incorrect. How do you manage to change versions, how do you structure 3rd party dlls form from external and internal sources as well as the dlls you want to include from your own team, but not as a project reference. I did a lot of tricks based on file-based directory structure in general, but none of them elegant or great when the versions changes. Also makes branching difficult because that becomes a consideration of how you structure the directories.

Now I work with Java and public mavan repos, super cool. I've been using python and pip to install effectively pulling back in and out of public repos. Finally I did some stuff in C # again with VS 2015 and integration with Nuget is exactly what was missing.

Now, in the corporate environment, public repos aren't always directly accessible, so you'll need the corporate repos. Again, Microsoft ecosystems are not ahead of this.

Basically in summary Java arose out of a more open source environment where the IDE project didn't use the maintenance, whereas .NET developed by Visual Studio managed the project, and these different ways meant the repo's later in Visual Studio.

Finally - and this is my observation - the Java community tends to give other people the frameworks more, as the Java base libraries offers less. Whereas .NET people write a lot more of their own code. The java community has a larger ecosystem of patterns and practices, whereas .NET again wrote its own code or waited for Microsoft. That changes but again shows why .NETTO is behind Java in the requirement for the repos.

Shareimprove this answer by Mark Channing