News for hackers. Stuff that matters.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by tiffanyh on Tuesday March 21, 2023 @05:48PM (#35253056)
It’s a tired thing to say, but the “.NET” naming is so confusing on what’s what.

Which is sad because there’s so much to like about .NET

Re:Understanding the .NET ecosystem: The evolution of .NET i... by pyjarrett on Tuesday March 21, 2023 @06:13PM (#35253389)
1. .NET "Core" ... I tell myself "C is for Cross platform." This is usually what people seem like they mean now when they talk about ".NET".

2. .NET "Framework" ... I tell myself "F is for Former." This is the older, Windows specific version.

3. .NET "Standard" ... I tell myself "S is for Specification." This is just the spec which defines what Core and Framework must implement.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by starik36 on Tuesday March 21, 2023 @06:40PM (#35253728)
I think .NET "Standard" is deprecated. Per this article. https://devblogs.microsoft.com/dotnet/the-future-of-net-stan...

Though reading through it, I am still confused.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by Jochim on Tuesday March 21, 2023 @08:00PM (#35254630)
.NET Standard specified a common API that was implemented by the .NET Core and .NET Framework runtimes, allowing library authors to easily target both platforms.

.NET Standard solved a problem at the time but as elucidated in the article, it turned out not to be the right solution in the long term. .NET Framework is essentially in maintenance mode and won't be receiving new language features, so new .NET Standard versions don't make much sense given the overhead they introduce. Newer versions of .NET will still be able to build and run libraries targeting .NET Standard but no new .NET Standard versions will be released.

Greenfield projects now typically target what was previously called .NET Core. With the removal of .NET Standard, .NET Core was renamed to .NET to reflect the fact that it's the whole ecosystem as far as any future development is concerned.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by starik36 on Tuesday March 21, 2023 @08:20PM (#35254856)
So the bottom line is that .NET Core can't call a .NET Framework library. It must be converted to .NET Standard first. And despite deprecation (let's call it that), .NET 5, 6, 7, 8 will continue to support calling into .NET Standard libraries.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by matthewrobertso on Tuesday March 21, 2023 @08:29PM (#35254957)
I am not sure this is (still) correct - I am able to call into a .NET framework 4.8 library from .NET 7.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by int_19h on Tuesday March 21, 2023 @09:41PM (#35255601)
If it's built against .NET 4.8 but only uses the API surface subset that corresponds to .NET Standard, that works - but then it's effectively a .NET Standard library with metadata not properly reflecting that.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by WorldMaker on Wednesday March 22, 2023 @03:41PM (#35266136)
Since .NET Fx 4.7 or 4.8 libraries consumed via NuGet are "assumed" .NET Standard 2.0 unless proven otherwise for maximal compatibility with old code.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by tiffanyh on Tuesday March 21, 2023 @06:15PM (#35253416)
That’s super helpful, thank you.

Where it still gets a bit murky is:

> “ .NET has many different implementations, including the .NET Framework, Mono, and Unity. Each of these is a separate platform with separate Base Class Libraries (BCLs) and app models. .NET Core is another separate platform.”

Re:Understanding the .NET ecosystem: The evolution of .NET i... by simooooo on Tuesday March 21, 2023 @07:16PM (#35254163)
You don’t really interact with or care about mono as A normal c# dev
Re:Understanding the .NET ecosystem: The evolution of .NET i... by WorldMaker on Wednesday March 22, 2023 @03:42PM (#35266150)
Mono is almost entirely merged in .NET 8. Very few parts of "mono" exist now as a separate runtime.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by doodlesdev on Tuesday March 21, 2023 @06:22PM (#35253509)
What about Mono and Unity?
Re:Understanding the .NET ecosystem: The evolution of .NET i... by pyjarrett on Tuesday March 21, 2023 @06:36PM (#35253676)
"Mono is an open source implementation of Microsoft's .NET Framework." [1]

Unity looks like it uses its own fork of Mono, or IL2CPP, which is a fancy thing that converts the intermediate language produced by C# into C++ code, which it compiles. [2][3][4]

[1]: https://www.mono-project.com

[2]: https://docs.unity3d.com/2023.2/Documentation/Manual/overvie...

[3]: https://docs.unity3d.com/Manual/IL2CPP.html

[4]: https://docs.unity3d.com/Manual/Mono.html

Re:Understanding the .NET ecosystem: The evolution of .NET i... by DoctorOW on Tuesday March 21, 2023 @08:33PM (#35254990)
Unity was Mono, and still is in some places. Now, it's moving to the cross platform .Net runtime.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by WorldMaker on Wednesday March 22, 2023 @03:44PM (#35266177)
As of .NET 8 most of what "mono" was has merged directly into one cross-platform .NET runtime. There's very little "mono" left, and most of it is on the path to disappearing/further merging, including the parts of mono that Unity uses.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by kgwxd on Tuesday March 21, 2023 @06:57PM (#35253923)
It's just .NET going forward (for now) if you don't need to worry about any old stuff.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by Kwpolska on Tuesday March 21, 2023 @07:25PM (#35254253)
The issue is with Googling (or Binging if you’re so inclined). If you google ".NET foobar", you might get answers for .NET Core, but you might also get old answers for the .NET Framework, written at a time when there was just one .NET, or when .NET Core was not as relevant and not the “real” .NET. Of course, it’s not super important if “foobar” is something simple and generic, like “.NET split string”, but when you get into the murky and obscure stuff, it might be hard to figure out if you’re reading an article about .NET Framework or .NET the-artist-formerly-known-as-Core.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by osigurdson on Tuesday March 21, 2023 @08:36PM (#35255014)
Suggest using ChatGPT instead of google.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by Kwpolska on Wednesday March 22, 2023 @07:33AM (#35259501)
Then go ahead and ask it, and tell us the results. A good query would be “How are assemblies loaded in .NET?”, and if the response talks about the Global Assembly Cache (GAC), app.config, or assembly redirections, it’s not applicable to the modern .NET.

I’m skeptical, ChatGPT is not magic, and it was trained on ~15 years’ worth of “there is only one .NET Framework, so we might as well call it .NET” content, ~5 years of “.NET Framework is for serious business, and there’s the cross-platform (mostly-)web .NET Core” content, and 1 year of “.NET 5 is the future of .NET”.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by osigurdson on Tuesday March 21, 2023 @08:33PM (#35254986)
Except .NET Core doesn’t exist anymore - it is just .NET.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by foobarbaz33 on Tuesday March 21, 2023 @09:36PM (#35255561)
It might be more accurate to say the label "Core" is no longer used by Microsoft branding department. The thing the label refers to still exists. And the label is still useful to differentiate from the old .NET.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by pyjarrett on Wednesday March 22, 2023 @12:14AM (#35256764)
True, but I only recently started learning .NET and I had to come up with a mnemonic to help filter out and through older docs and resources. It gave enough clarity to gain traction.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by SketchySeaBeast on Tuesday March 21, 2023 @05:59PM (#35253195)
Assuming you're not looking at legacy and are on .NET 5.0+ it's not confusing, it's just the one ecosystem, no core or framework stuff, just .Net.

If you're before that, well, good luck.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by Anon4Now on Tuesday March 21, 2023 @06:10PM (#35253342)
> no core

Except the docs, which still say core all over the place, including the url's. ;-)

Re:Understanding the .NET ecosystem: The evolution of .NET i... by yread on Tuesday March 21, 2023 @06:13PM (#35253388)
Isn't Java world a lot more confusing? You have Java language, Java compiler, Java class library, Java Virtual Machine, Java bytecode, Java runtime environment, Java development kit (OpenJDK - is it open? how many forks are there?), Java SE, ME, EE, JavaBeans. What can you use where, what is the license, who made what, what role does Oracle play? So many questions in a universe where google doesn't exist to clear up confusion, no?
Re:Understanding the .NET ecosystem: The evolution of .NET i... by javamanfossils on Tuesday March 21, 2023 @07:26PM (#35254273)
These are different things: JDK already includes an implementation of API, compiler, and runtime. OpenJDK has many builds, not forks. Java EE is now known as Jakarta, and "Enterprise JavaBeans" were replaced by Spring. Clarifying just in case; otherwise I agree that the ecosystem might be confusing, especially if you consider the historical development and legacy code.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by Kwpolska on Tuesday March 21, 2023 @07:35PM (#35254390)
I Googled “.NET assembly loading”. The second hit is “Understanding How Assemblies Load in C# .NET”, [0], from July 2020, 4 months before the RTM release of the unified .NET 5. While this post mentions .NET Core by name once, this post is completely irrelevant to .NET Core/5+ (which threw out the Global Assembly Cache, assembly redirections, and generally simplified everything). How do you find articles that are actually relevant to the modern .NET and not the Framework?

The Java stuff is easy. From the perspective of a Java developer, most of the things you listed (except for ME, EE and JavaBeans) are just “Java”. And they always have been.

[0] https://michaelscodingspot.com/assemblies-load-in-dotnet/

Re:Understanding the .NET ecosystem: The evolution of .NET i... by T-zex on Tuesday March 21, 2023 @05:58PM (#35253193)
Isn't it with .Net 7 it becomes simply .Net and confusion with Framework, Standard, Core is now gone?
Re:Understanding the .NET ecosystem: The evolution of .NET i... by SketchySeaBeast on Tuesday March 21, 2023 @05:59PM (#35253204)
Yes. Has been that way since 5.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by kgwxd on Tuesday March 21, 2023 @07:03PM (#35253999)
Which specifically wasn't named .NET 4 because that would be confused with .NET Framework 4.x :) Which I'm currently stuck on for work :(
Re:Understanding the .NET ecosystem: The evolution of .NET i... by justeleblanc on Tuesday March 21, 2023 @05:57PM (#35253171)
> It’s a tired thing to say,

And yet, here you are, right on the dot. First comment on any .NET thread.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by Nuzzerino on Tuesday March 21, 2023 @06:01PM (#35253228)
And in a thread about an article that explains the very thing commenter is "confused about"
Re:Understanding the .NET ecosystem: The evolution of .NET i... by thenerdhead on Tuesday March 21, 2023 @06:15PM (#35253427)
If you could rename it, what would it be and why?
Re:Understanding the .NET ecosystem: The evolution of .NET i... by smcl on Tuesday March 21, 2023 @06:28PM (#35253581)
Another good question would be - if you were Microsoft and wanted to plan a roadmap to take the .NET ecosystem forward from a couple of separate implementations (Windows-only .NET Framework, Cross-platform Xamarin) how would you go about this in a way that doesn't cause a big furore like Python 2->3 did?

Because I imagine you end up with what MS did - define a standard that can be used for building common code between new/old, continue support for both, quickly iterate the new while it's still new, be very open about support timelines and document everything pretty thoroughly. You'd just end up with a different set of names for that standard (.NET Standard), and new implementation (.NET Core) that make sense to you, but probably still confuse some people.

I don't think it's perfect, but .NET developers will (or should) all grasp the relationship between .NET Standard/Core/Framework (and now plain ".NET") pretty easily.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by Jochim on Tuesday March 21, 2023 @08:09PM (#35254731)
The only frustration I've experienced in actually working with it is that it leads to polluted search results.

Trying to find solutions to ASP.NET Framework problems usually requires discarding a whole bunch of irrelevant ASP.NET Core/.NET ones.

It's the same with Visual Studio/Visual Studio Code.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by thenerdhead on Tuesday March 21, 2023 @08:23PM (#35254878)
This is a similar problem with ChatGPT and AI in general. While some things may not change much, you can't generally say "how do I x in .NET" without the chance of getting a really old answer.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by Jochim on Thursday March 23, 2023 @07:41AM (#35273180)
Being more specific is definitely helpful. I've found that ChatGPT is less frustrating than DDG/Google, probably just due to the conversational nature. You can ask ChatGPT to correct itself if it doesn't give the answer you want. e.g. "Could you write that using .NET 7" or "Use <.net7 language feature> to solve the problem".

Whether it spits out the correct answer is still up to chance but the narrowing does seem to work quite well.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by smcl on Wednesday March 22, 2023 @10:52AM (#35261961)
It sounds like the issue you have is introducing breaking or backwards incompatible changes at all while retaining the a similar name. Which is a fair point.

I’m not sure what would help in that case other than using something else than “.NET” to identify it.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by Jochim on Thursday March 23, 2023 @07:36AM (#35273136)
Precisely. It's certainly not an issue exclusive to the .NET ecosystem but it is a minor annoyance in my day to day life. On the plus side it only affects work on legacy projects that haven't been migrated yet. One day will be the last day that someone needs to add "-Core", "-Code", "-.NET5", "+Framework" etc. to their search queries and that will be a happy day!

Griping about a minor inconvenience isn't to say that I don't think it was the correct decision. The new .NET is already far better than Framework, in how the platform is progressing and the development experience.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by WorldMaker on Wednesday March 22, 2023 @03:49PM (#35266242)
> Trying to find solutions to ASP.NET Framework problems usually requires discarding a whole bunch of irrelevant ASP.NET Core/.NET ones.

My experience was this was always a problem even before later versions of ASP.NET. There was so much backwards incompatible changes between ASP.NET 3/4/5 and ASP.NET MVC 3/4/5 and even things that searching for ASP.NET MVC 3/4/5/6 would disagree with ASP.NET 3/4/5 non-MVC recommendations.

If there was a point where googling ASP.NET problems was clean and unpolluted it probably only existed briefly in 1.0.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by Jochim on Thursday March 23, 2023 @07:46AM (#35273229)
That's both reassuring and a bit depressing :P

I'm young enough to have only caught the tail end of Framework in my professional career but I do recall a lot of Razor Pages content showing up when looking for tutorials on MVC.

It's certainly not unique to .NET. Being stuck on an old version of Elasticsearch can turn into a nightmare when trying to find a quick a solution to a query problem.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by andix on Tuesday March 21, 2023 @08:07PM (#35254703)
If you start now, you can ignore everything before .NET 5. And then there is no confusion left. Just don’t read any tutorials/documentation that were written for an older .NET version.