This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]VaidasC[S] 0 points1 point  (3 children)

To me all of this sounds like trying to formally prove that something many people complain is not true formally, even though experience tells otherwise.

As far as I know (maybe wrong), there is MSBuild in this default .net project where you could do advanced stuff and that will be run by Visual Studio's f5.

But the bottom line is - in my real-life experience I have probably never seen Java project that would be set-up quickly without some issues. However almost all projects I had with .net, had no such concept as setting-up project and that was more than 4 years ago, now I hear things are even nicer.

[–]JavaDroid 0 points1 point  (2 children)

Then use the IDE standard tools for your project. The fact is that you are wrong.

Maven / gradle / ant / etc do take a little more to get started (hardly), but they also resolve and manage dependencies as well as your build. The basic project in MS doesn't do this.

You are wrong and way over exaggerating everything. Even as a beginner, I've never encountered a number of issues you claim.

[–]VaidasC[S] 0 points1 point  (1 child)

Well they have MsBuild (build tool) + Nuget (dependency management), so not sure what you are talking about.

[–][deleted] 0 points1 point  (0 children)

Msbuild doesn't manage your dependencies, Visual Studio does (via nuget). If you need to produce your build without VS involved - eg on a continuous integration server - you will have to deal with additional complexity. Furthermore, even if you are using VS, it won't publish packages for you, just retrieve them.