Changing Names .NET ______
-
For casual reading over the holidays I picked up a book on C# 8 and .Net Core 3. I skimmed much of it and between it and the turkey I had some great naps. I have been using .NET for years. I did not know until recently it was .NET Framework. The word “Framework” was probably buried in there somewhere, but I like most people largely ignored it. I mostly ignored .NET Core also. I figured it was just another reincarnation of Silverlight. Now that Core is going to replace Framework I figured I better learn something about Core. Guess what? No more Core. No more Framework. We are back to just .NET. I think the marking guys really had to work over time to come up with this idea (sarcasm intended). I know the book is already obsolete. It was just published a few month ago. I kind of feel sorry for the authors. Now they have to rewrite the book as “Pro C# 9 with .NET”
So many years of programming I have forgotten more languages than I know.
-
For casual reading over the holidays I picked up a book on C# 8 and .Net Core 3. I skimmed much of it and between it and the turkey I had some great naps. I have been using .NET for years. I did not know until recently it was .NET Framework. The word “Framework” was probably buried in there somewhere, but I like most people largely ignored it. I mostly ignored .NET Core also. I figured it was just another reincarnation of Silverlight. Now that Core is going to replace Framework I figured I better learn something about Core. Guess what? No more Core. No more Framework. We are back to just .NET. I think the marking guys really had to work over time to come up with this idea (sarcasm intended). I know the book is already obsolete. It was just published a few month ago. I kind of feel sorry for the authors. Now they have to rewrite the book as “Pro C# 9 with .NET”
So many years of programming I have forgotten more languages than I know.
The details are even worse. Basically Core was intended as a cross platform rendition of .NET which I think is silly because Mono can already run .NET Framework apps (so presumably, could other incarnations of the CLI). There's no code access security or windows specific things like Winforms but basically otherwise it's the same thing to the developer. The main difference from a usability standpoint AFAIAC is the the fact that you must instantiate .NET core apps using a sandbox app like:
dotnet myapp
instead of just
myapp
which frankly makes using it as a CLI a little annoying. Then there's .NET standard which is a standard subset that works with both of the above. It's more than a marketing problem. It was a tech problem. They forked .NET when they never should have. Arguably it was unavoidable because of some baggage in terms of how .NET Framework was designed in the first place but i don't know how much I agree with that, given Mono. Take all this with a grain of salt. This is just my take from using them + the snatches of info I've read online.
Real programmers use butterflies
-
For casual reading over the holidays I picked up a book on C# 8 and .Net Core 3. I skimmed much of it and between it and the turkey I had some great naps. I have been using .NET for years. I did not know until recently it was .NET Framework. The word “Framework” was probably buried in there somewhere, but I like most people largely ignored it. I mostly ignored .NET Core also. I figured it was just another reincarnation of Silverlight. Now that Core is going to replace Framework I figured I better learn something about Core. Guess what? No more Core. No more Framework. We are back to just .NET. I think the marking guys really had to work over time to come up with this idea (sarcasm intended). I know the book is already obsolete. It was just published a few month ago. I kind of feel sorry for the authors. Now they have to rewrite the book as “Pro C# 9 with .NET”
So many years of programming I have forgotten more languages than I know.
It's always been the .net framework and it will continue to be the .net framework. I do hope they come up with a good replacement for it soon.
-
The details are even worse. Basically Core was intended as a cross platform rendition of .NET which I think is silly because Mono can already run .NET Framework apps (so presumably, could other incarnations of the CLI). There's no code access security or windows specific things like Winforms but basically otherwise it's the same thing to the developer. The main difference from a usability standpoint AFAIAC is the the fact that you must instantiate .NET core apps using a sandbox app like:
dotnet myapp
instead of just
myapp
which frankly makes using it as a CLI a little annoying. Then there's .NET standard which is a standard subset that works with both of the above. It's more than a marketing problem. It was a tech problem. They forked .NET when they never should have. Arguably it was unavoidable because of some baggage in terms of how .NET Framework was designed in the first place but i don't know how much I agree with that, given Mono. Take all this with a grain of salt. This is just my take from using them + the snatches of info I've read online.
Real programmers use butterflies
Do not be so serious about it. In some ways you sound like Microsoft marketing. They have pushed the speech many times in many places. Mine was a rant on how it impressed me (and affected the books authors). It was an attempt at being humors. Well, as humors as a programmer can be.
So many years of programming I have forgotten more languages than I know.
-
For casual reading over the holidays I picked up a book on C# 8 and .Net Core 3. I skimmed much of it and between it and the turkey I had some great naps. I have been using .NET for years. I did not know until recently it was .NET Framework. The word “Framework” was probably buried in there somewhere, but I like most people largely ignored it. I mostly ignored .NET Core also. I figured it was just another reincarnation of Silverlight. Now that Core is going to replace Framework I figured I better learn something about Core. Guess what? No more Core. No more Framework. We are back to just .NET. I think the marking guys really had to work over time to come up with this idea (sarcasm intended). I know the book is already obsolete. It was just published a few month ago. I kind of feel sorry for the authors. Now they have to rewrite the book as “Pro C# 9 with .NET”
So many years of programming I have forgotten more languages than I know.
I forgot to mention I only paid $7 for the book. It was on some kind of holiday sales deal.
So many years of programming I have forgotten more languages than I know.
-
I forgot to mention I only paid $7 for the book. It was on some kind of holiday sales deal.
So many years of programming I have forgotten more languages than I know.
So, we're all programmers here. Do you mean
michaelbarb wrote:
...It was on some kind of (holiday sales deal).
or
michaelbarb wrote:
...It was on (some kind of holiday) sales deal.
Sorry, getting annoyed with people that can't use the word "Christmas".
I'm retired. There's a nap for that... - Harvey
-
So, we're all programmers here. Do you mean
michaelbarb wrote:
...It was on some kind of (holiday sales deal).
or
michaelbarb wrote:
...It was on (some kind of holiday) sales deal.
Sorry, getting annoyed with people that can't use the word "Christmas".
I'm retired. There's a nap for that... - Harvey
So we're all programmers here. Therefore, in the absence of parantheses, we parse from left to right. :)
Wrong is evil and must be defeated. - Jeff Ello Never stop dreaming - Freddie Kruger
-
For casual reading over the holidays I picked up a book on C# 8 and .Net Core 3. I skimmed much of it and between it and the turkey I had some great naps. I have been using .NET for years. I did not know until recently it was .NET Framework. The word “Framework” was probably buried in there somewhere, but I like most people largely ignored it. I mostly ignored .NET Core also. I figured it was just another reincarnation of Silverlight. Now that Core is going to replace Framework I figured I better learn something about Core. Guess what? No more Core. No more Framework. We are back to just .NET. I think the marking guys really had to work over time to come up with this idea (sarcasm intended). I know the book is already obsolete. It was just published a few month ago. I kind of feel sorry for the authors. Now they have to rewrite the book as “Pro C# 9 with .NET”
So many years of programming I have forgotten more languages than I know.
To change names in .NET use the ctrl + r, ctrl + r shortcut in Visual Studio :D
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
So, we're all programmers here. Do you mean
michaelbarb wrote:
...It was on some kind of (holiday sales deal).
or
michaelbarb wrote:
...It was on (some kind of holiday) sales deal.
Sorry, getting annoyed with people that can't use the word "Christmas".
I'm retired. There's a nap for that... - Harvey
I do not know about that, but none of the sales in the last mont were labeled 'Christmas sale', so we left with 'some kind of holiday'... :-)
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
