Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
My boss keeps asking me “which version of .NET are we upgrading to”, to which I answer “3.5, the latest one”.
But then he sees things about how .NET 3.5 is just a set of libraries on top of .NET 2.0 and I find myself having to explain it to him.
And of course the version of C# that ships with .NET 3.5 is actually C# 3.0.
What’s a good way to explain the different versions of .NET to a non-techie type in a way that doesn’t confuse them or freak them out?
You should decompose .NET as a package of three different things:
This way, it’ll be pretty easier to explain.
For instance, in .NET 3.5 we have: