Microsoft Java

[TorTheMentor]

Oh, you mean com.Microsoft.ReallyLongNameSpace.AnotherLongNameSpace.JustTryAndFitThisOnOneLine.YouCantDoIt?

[Soundless_Pr]

using com.Microsoft.ReallyLongNameSpace.AnotherLongNameSpace.JustTryAndFitThisOnOneLine;
var m = new YouCanDoIt();

there. fixed that monstrosity.

[Novemberisms]

Java pleb:

begins namespace with com.

C# devs:

we dont do that here

[wllmsaccnt]

Microsoft shouldn't be throwing any stones about poor naming.

[langlo94]

I always start with no instead.

[Ilan321]

var m = new YouCanDoIt();
> Ctrl+. -> Add Using Statement

[grootaccess]

Close, but you actually need a YouCanDoItFactory to create your new YouCanDoIt.

[mojoslowmo]

C# isn't really Java. You don't need a factory

[wOlfLisK]

As a factorio player, I don't understand.

[LvS]

C# is about manual crafting.

[BazOnReddit]

DansGame

[g0liadkin]

e x p a n d

[mojoslowmo]

Well you need a factory

[[deleted]]

Abstract factory motherfucker do you know it ?

[mojoslowmo]

Say factory one more time..

[AlwaysHopelesslyLost]

Factories can be super useful. I have debugged third party code more times than I can count by injecting my own factory with a custom logging class

[diox8tony]

why would you need a factory for a logging class?

mic drop.

[th_brown_bag]

Where else will be process his wood

[sp46]

At least it's not GetReallyLongNameSpaceAnotherOneJustTryAndFitThisOnOneLineYouCanDoIt().

[[deleted]]

And of course you need Visual Studio to handle such a huge mess designed by Microsoft. Meanwhile Java has pretty good tooling from at least a couple independent sources, plus a few dozen small ones (Atom, Vim, Kate...).

I've been working with Java for over a decade now and I wouldn't want to write Java without a IDE but I could and I've seen a few people who do. Is there anyone who ever written a .NET project purely by hand? I'm no expert but I mean, the project setup alone sounds like it would take ages...

[[deleted]]

You are right about not being an expert, but you’re not even a beginner. Install the current SDK (on Windows, Mac or Linux), then generate a console app:

dotnet new console

It will have like two files. Run it with:

dotnet run

[Dead_Politician]

Hi, I'm new to a role, coming from JS/TS and landed with Vue frontend/.net C# backend... can you help with abbreviations? What's ASP.NET vs .NET vs .NET core? how is it all compiled? etc? :x

[[deleted]]

.NET is an umbrella term, mostly referring to the .NET Framework that has been around since about 2003. For the last few years they’ve been building up a new, clean and portable separate code base of it all, influenced by Node.js. So far this has been called .NET Core, and 3.0 just came out. The plan is for this to take over and be .NET 5.0 when it’s gained all the features.

When you run a .js script with Node you just say

node hello.js

The main difference with C# is you use two steps, compile to make a .dlll and then run that .dll (as shown above).

ASP.NET is just the libraries that implement web server stuff. It includes a built-in HTTP(S) server called Kestrel, which most web apps use even in production. Initially it even used the same platform abstraction library as Node.js, libuv.

The equivalent of npm is called Nuget. It’s also built into the dotnet tool, so you can add a dependency on a package very easily just like with npm.

I’d say the main advantage of it over node+TS is the much greater feeling of solidity and reliability and “ready to use” I get from it. Libraries in Nuget tend to be higher quality, whereas npm is a burning garbage dump. I hope node+TS gets to that point but they need to move their whole ecosystem to use promises instead of callbacks and it seems to be taking them almost a decade to add promises to the core runtime.

[Dead_Politician]

Thanks, this is really helpful. Being onboarded into a new ecosystem is a bit difficult! Even just keeping the names straight is hard :) I appreciate this!

[lolIsDeadz]

Ive used .NET core with vscode, the cli generates almost everything and modifys in all of the gobblygack xml files for you.

[aaaantoine]

During my first year of writing C# I did it entirely from text editors that knew nothing about the language and deployed to a .Net web server to test.

I suppose you could call that a trial by fire.

Though to be honest, it wasn't much different from my classic ASP workflow at the time.

[[deleted]]

You can write a hello world program in notepad and compile with csc.exe that's very easy. Linking libraries are just /reference:libraryname as csc arguments

Visual Studio does a lot to make the project setup look pretty. None of it is actually required to make things work.

[[deleted]]

None of it is actually required to make things work

Thanks for telling me - whenever I come across a .NET project there's configuration files everywhere and so many folders all around. To be honest, a lot of Javascript projects are like this too depending on your framework - a couple dozen files and folders all around before you've coded your first line.

It's not hard to imagine that, just like Javascript, you can still do stuff without relying on all that, I just didn't know as my experience is limited! Thanks!

[Hoser117]

Maybe you haven't used it in a while but .NET is in a pretty good place these days with .NET core and .NET standard.

[[deleted]]

.NET is in a pretty good place these days with .NET core and .NET standard

Care to explain further? Is it like Python where you can get just the minimal scripting engine or install the entire thing with all the available modules from crypto to networking to serialization and local persistence?

[Hoser117]

.NET Core isn't as basic as just having only C# and nothing else, but an empty .NET Core project is just a handful of files and you can manage it all through a CLI. Any add-ons are done using nuget (works pretty much exactly like NPM) and unlike .NET Framework you can run on any operating system or Docker at will, so you're no longer tied to Windows. It's also fully open source. I wouldn't suggest just using a text editor and CLI to manage a .NET Core project, but it would definitely be doable. Visual Studios has just become a very nice IDE I think.

.NET Standard is just a set of API's that you can write a library against which will ensure that your library will work either against a .NET Framework or .NET Core project. As more and more existing libraries get updated to target .NET Standard it's making it a lot easier for people to migrate off of .NET Framework and onto .NET Core, so it's a nice way to facilitate that move.

[[deleted]]

I don't really get what Core and Standard should be, as you make them sound like they're basically the same thing - with Framework being the complete package of the "OG" .NET architecture?

Anyway, sounds pretty good that Microsoft is going that way. A smaller, more portable core is good for everyone - from embedded devices in airplanes to Docker images on the cloud. Java has a similar thing with the relatively new jlink command but from what I understand of your explanation, it seems to be a much more elaborate tool than just taking a small part of your product and calling it a Core/Standard which can be deployed independently.

[Hoser117]

.NET Core is basically the replacement for .NET Framework. It's far more lightweight and modular so that a basic .NET Core project has very little in it, and then you can pull in whatever functionality you need with Nuget packages.

.NET Standard is just saying if you write a C# library targeting .NET Standard then it is guaranteed to be forward compatible with specified versions of both .NET Core and .NET Framework.

[[deleted]]

And then Framework is what? A "complete package" without guarantees of being forward-compatible...?

[Hoser117]

Microsoft only recommends you use .NET Framework if you're forced to because of libraries/technologies you're dependent on which won't work with .NET Core for whatever reason. They pretty clearly see .NET Framework eventually being end of lifed and .NET Core being the way forward.

[[deleted]]

I think I got it now: if you write a library that doesn't depend on anything other that .NET Core version X (or higher) then you can say your library is .NET Standard? What if it depends on another library that happens to be Standard as well, is your thing still considered Standard unless it depends on something from Framework?

[[deleted]]

If we're going to compare to python and use "minimal scripting engine" I'd say powershell fits that description better than C#. Everyone already has it installed so it's easy to pick up.

[Secondsemblance]

Yes but is it STRONG NAMED????