Opinions on .NET Framework?

[Jon Skeet [C# MVP]]

Because, as you agree, there is a relationship between the IDE and the
Framework.

But by not stating that you were talking about VS.NET, you caused
confusion. I didn't just ask why you replied with a statement about
VS.NET - I asked why you replied with one which implied you were
talking about .NET.

And I've agreed (literally 7 posts ago).

Where, exactly? It's hard to know exactly what you mean by "7 posts
ago". I can see you claiming that your point was clear as recently as
2:10 today (UTC).

No, I can't, but the OP didn't know that, thus his post.

So why did you write:

<quote>
The OP asked for opinions, and that is mine. I find it easy and clear
to see why using the IDE as an example of why the .Framework is on
solid ground a simple conceptual leap to make, you don't - - your
problem, not mine.
</quote>

Why did you claim I don't find your example a simple conceptual leap? I
do - once you've actually stated it that way, rather than misleadingly
referring to VS.NET as "it" when replying to a post which didn't
mention IDEs at all. You recently conceded that you should have written
"development environment", but that still doesn't address the fact that
with that change your post would have referred to the .NET framework as
if it were an IDE.

No, I'm berating people for not letting go of it and continuing to pounce on
it after I corrected my terminology 7 posts ago!

The way you corrected it still seemed to imply that it was everyone
else who was deliberately misinterpreting your first post rather than
it being a basically misleading post.

 

[Kevin Spencer]

The only relationship between Visual Studio and the .Net Framework is that
Visual Studio requires the .Net Framework. The .Net Framework does *not*
require Visual Studio. Visual Studio also requires a number of COM DLLs to
be installed. It is a one-way "relationship."

This is the same relationship that *every* piece of software has with the
DLLs that it uses to function. C++ MFC applications require MFC and/or COM
DLLs to work. C applications almost always require (at least) stdio.dll to
work. VB applications require one or another of the VB DLLs and (usually)
some COM DLLs to work.

--
HTH,

Kevin Spencer
Microsoft MVP
Short Order Coder
http://unclechutney.blogspot.com

The devil is in the yada yada yada

 

[Jon Skeet [C# MVP]]

The only relationship between Visual Studio and the .Net Framework is that
Visual Studio requires the .Net Framework. The .Net Framework does *not*
require Visual Studio. Visual Studio also requires a number of COM DLLs to
be installed. It is a one-way "relationship."

That's true - but it's that way that I believe Scott was relying on.
Microsoft wouldn't use .NET in Visual Studio if either they were
planning on getting rid of it or if they thought it was rubbish.

That's an entirely fair point to make and one I support, even if I
disagree with the way Scott made it

 

[Peter Duniho]

The first step (out of the 3 step installation) is the installation of the
.NET Framework. It is part of the VS .NET installation, not a pre-install
requirement.

So, in other words, Visual Studio "requires" the .NET Framework in the same
way that it requires every other component installed with VS, such as the
IDE executable itself, all the supporting DLLs, the compiler, linker, etc.
That is, you don't so much have to *have* the .NET Framework as you have to
allow Visual Studio to install it for you.

Which means that Microsoft *could* pull support for the .NET Framework at
any time, and that would not interfere one bit with the ability to install
Visual Studio, or to use it to write Windows software (managed or
otherwise).

So the dependency of Visual Studio on the .NET Framework turns out to not be
related to Microsoft's future plans for the .NET Framework at all.

Pete

 

[Kevin Spencer]

I agree, it's a fair point. In fact, Microsoft is investing quite heavily in
the .Net Framework, and writing new software with it all the time (not *all*
of their new software, but quite a lot of it).

--

Kevin Spencer
Microsoft MVP
Short Order Coder
http://unclechutney.blogspot.com

The devil is in the yada yada yada

 

[Bob Lehmann]

Man, you guys must have a lot of free time on your hands, or else your
extemely bored.

Bob Lehmann

I agree, it's a fair point. In fact, Microsoft is investing quite heavily in
the .Net Framework, and writing new software with it all the time (not *all*
of their new software, but quite a lot of it).

--

Kevin Spencer
Microsoft MVP
Short Order Coder
http://unclechutney.blogspot.com

The devil is in the yada yada yada

 

[Kevin Spencer]

If I had a lot of free time on my hands, I *would* be extremely bored!

However, I don't, and I'm not.

--
;-),

Kevin Spencer
Microsoft MVP
Short Order Coder
http://unclechutney.blogspot.com

The devil is in the yada yada yada

Man, you guys must have a lot of free time on your hands, or else your
extemely bored.

Bob Lehmann