.NET 3.What?
-
I just wanted to have a brief rant. ahem. I think naming the WinFX extensions ".NET 3.0" (that work on the 2.0 CLR) instead of .NET 2.5 was dumb, and then naming the next version .NET 3.5 instead of 3.0 and having it run on the 2.0 CLR instead of the 3.0 CLR wasn't quite dumb, just messy. End of rant. (For the explanation read Brad Adams' blog entry[^])
cheers, Chris Maunder
CodeProject.com : C++ MVP
Chris, Here's another confusing bit: WPF 1.0 was part of .NET 3, right? Ok, fine. .NET 3.5 comes out, and now it's called WPF 3.5! Ha! While I agree it's confusing that the CLR, .NET framework, the languages, and the various APIs like WPF all have their own versions that makes it confusing, I do remember devs were complaining that leaving it "WinFX" was confusing. I remember a Slashdot article where everyone was like, "WinFX? What ever happened to .NET? I guess that means .NET failed! Woo! Down with M$!" So I guess I'm not sure of a better way to do this. If the CLR, .NET framework, languages, and APIs all shared the same version number, one could not increment version number without all of them incrementing. Which would mean C# 3 would be the same as C# 2, which seems equally confusing.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Upon this disciple I'll build my new religion? The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
This will to some extent damper adoption. I cant imagine attempting to explain the deployment and technology to my clients. Ideally, I'd like to say we are using version X of product Y without having to worry about runtime and framework version requirements.
Although I've never done any .NET development, I think that WinFX was the original (pre-release) name for version 1 of the .NET framework. It's possible that they released a new product by the same name, but I've never heard of it.
-
This is easy to explain. Before Windows 2000, the business OS was just numbered NT {version number}, like NT 3.11, NT 3.5 and NT 4.0. Win 2000 is really NT 5.0. XP is really NT 5.1, and that's when the business OS and the consumer OS came together and the DOS based OS was finally gone. Well, if you can see the trend, Vista is really NT 6 and so the next version would be called 7 internally, later given some not-so-fancy name by marketing. It appears that the jump between major build numbers is hard for people to do. If you remember, back a few (8) years ago, the transition between NT4 to 2000 was pretty significant, just like the transition between XP and Vista is now. And people were slow to adopt Win2k as well. Maybe the difference is that people knew that Win2k was much better than NT4, but people today aren't sold on Vista being much, if any, better than XP. I am in the small minority of people that actually like Vista.
Success is the happy feeling you get between the time you do something and the time you tell a woman what you did. --Dibert My left name is Tremendous Savings, Ms. America – Señor Cardgage
Me too - the only problem I have with Vista is that my display driver gets a little glitched when I try to connect a projector to the video-out port on my laptop - sometimes I get no signal. For everything else, I love it.
-
That's a great petition and, had I known about it, I would've signed it! I'm beginning to think that petitions in general rarely work (can anyone point me to any significant ones that have?)
- S 50 cups of coffee and you know it's on!
I did get a reply[^] from Jason and some attention in the press[^], but you're right, in the end it didn't do much.
-
Me too - the only problem I have with Vista is that my display driver gets a little glitched when I try to connect a projector to the video-out port on my laptop - sometimes I get no signal. For everything else, I love it.
Mind you, nVidia did play a huge part in driving Vista's reputation into the ground with their absolutely horrible drivers. Oh, and the fact that people believe Windows hasn't made any technical advancements thanks yet again to the dumb decision to move WinFX to .NET. And yes I do mean a version number of 2010 or what not, not just a product name. .NET supports version number segments of up to 65535, so we might as well.
modified on Thursday, March 13, 2008 4:22 PM
-
Chris, Here's another confusing bit: WPF 1.0 was part of .NET 3, right? Ok, fine. .NET 3.5 comes out, and now it's called WPF 3.5! Ha! While I agree it's confusing that the CLR, .NET framework, the languages, and the various APIs like WPF all have their own versions that makes it confusing, I do remember devs were complaining that leaving it "WinFX" was confusing. I remember a Slashdot article where everyone was like, "WinFX? What ever happened to .NET? I guess that means .NET failed! Woo! Down with M$!" So I guess I'm not sure of a better way to do this. If the CLR, .NET framework, languages, and APIs all shared the same version number, one could not increment version number without all of them incrementing. Which would mean C# 3 would be the same as C# 2, which seems equally confusing.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Upon this disciple I'll build my new religion? The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
Ah, Slashdot. That bastion of intelligent, thoughtful discussions on Microsoft.
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
-
Chris Maunder wrote:
I've seen "8 years experience in C#".
It is possible. The first beta of .NET 1.0 was released in 2000.
-
Mind you, nVidia did play a huge part in driving Vista's reputation into the ground with their absolutely horrible drivers. Oh, and the fact that people believe Windows hasn't made any technical advancements thanks yet again to the dumb decision to move WinFX to .NET. And yes I do mean a version number of 2010 or what not, not just a product name. .NET supports version number segments of up to 65535, so we might as well.
modified on Thursday, March 13, 2008 4:22 PM
reinux wrote:
Mind you, nVidia did play a huge part in driving Vista's reputation into the ground with their absolutely horrible drivers.
Interesting - I never even mentioned that my laptop has a GeForce 8600 card and you're talking about nVidia anyway.
-
QmxvdyBtZSE= :)
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
haven't worked with that encoding since uni. Much preferred uuencode / uudecode :D
I have no blog...
-
Ah, Slashdot. That bastion of intelligent, thoughtful discussions on Microsoft.
cheers, Chris Maunder
CodeProject.com : C++ MVP
:laugh:
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Upon this disciple I'll build my new religion? The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
I disagree, if you want to work with something you must at least know a bit of what you are talking about, it doesn't matter if he is an expert in JAVA and knows nothing of C# if that is what he is going to work with. First, learn the language/tool, then you can go for it. This just proves he "lied" about his expertise and I think that is enough reason to not give him a job.
Now aggreed. After facing this issue.
-
Now aggreed. After facing this issue.
Wow, long time... So, you faced the issue couz it happened to you or someone you were hiring?
