Re: Opinions on .NET Framework?

Pete,

This is my last word on this (cause I'm growing old over here)....

See responses inline...

"Peter Duniho" <NpOeStPeAdM@xxxxxxxxxxxxxxxx> wrote in message
news:12jsmb74f6ldu10@xxxxxxxxxxxxxxxxxxxxx
"Scott M." <s-mar@xxxxxxxxxxxxx> wrote in message
news:eA0UMZ59GHA.4196@xxxxxxxxxxxxxxxxxxxxxxx
I don't know how to make it any clearer. Ok, let's try this...

Q: I'd like to do some Windows development. What development IDE's are
available from MS to accomplish this task?

Who asked that question? Why is an answer to that question relevant in
this thread?

I did. And, it's relevant because it explains my original reply in this
thread.


A: One of the VS .NET flavors.

Summary:

VS .NET is the only MS development environment at this time. So, I would
say that .NET (as a development platform and an API) will be with us for
a while.

As far as I know, there is no Visual Studio .NET anymore. I have both the
Express and retail version of Visual Studio, and both of them simply say
"2005". They don't appear to be labeled as ".NET" any longer.

True, but VS .NET 2002 and VS .NET 2003 are still supported products from MS
and VS 2005 (while not having the .NET brand name) still works with the .NET
Framework. The decision to drop .NET from the name is not related to the
adoption (or lack thereof) of the .NET technology by MS, it has to do with
the ubiquitous nature that .NET has become and marketing.

In any case, the continued production of some version of Visual Studio in
no way at all implies the continued support of any version of .NET. The
two are completely independent of each other. Microsoft could easily drop
support for the .NET Framework without affecting their Visual Studio
business. Currently, it would be harder for them to drop Visual Studio
without affecting the .NET Framework, since there are no third-party tools
for writing .NET code, but the fact remains that there is at least the
theoretical possibility of that.

Ok, but what does that have to do with the OP or anything that I have said.
I never once said .NET reigns supreme and will continue to do so ad
infinitem. Any implications that this is what I said, were made by you.

So, it seems to me that not only have you misinterpreted the original
question (it wasn't asking about development tools), your answer continues
to confuse the API and the development tools used to write software for
the API. At every step, you've tried to modify the original question to
better suit the answers you're giving, but in doing so the answers still
aren't correct.

No, not at all. You've just continuously been pounding your terminology
preferences over mine. My point is simple and clear (despite your attempts
to make it more compicated). Right now (and for the foreseeable future) MS
is providing a development environment that relies on the .NET Framework for
(all but native) code written with it. The .NET Framework is certainly not
a *small* part of the Visual Studio equation. And, this is the ONLY
development environment being supplied by MS at this time.

I brought the IDE into the conversation as a way to express the current
importance of the .NET Framework. Despite your feelings that talking about
the development environment is somehow not warrented in the replies to this
thread (the title of the post by the way was: "Opinions on the .NET
Framework" - - did you notice the Opinions part?), I felt it appropriate to
talk about the development environment that 99.999% of Windows developers
are currently using to develop .NET applications. I never said .NET
applications couldn't be built without it (as you have implied that I did
say). I said that it is the only "development platform" being provided by
MS for .NET development at this time. You take issue with my wording here
(development platform). Fine, how about "developmemt IDE" instead? This is
what I meant (and quite frankly, clearly understandable by most readers).

Don't get me wrong...I'm not trying to attack you or somehow undermine
your credibility. But I do think it's *very* important to understand the
difference between a given API (of which there are many for writing
Windows software) and a development tool (of which there are many for
writing Windows software). Inasmuch as your replies appear to confuse the
two, I see a need to at least attempt to correct that confusion.

Nor am I, but I think the simple point (which I won't repeat because I've
stated it simply several times by now) which I've been trying to make has
been obscured by hair splitting on terminology.


By the way, going back to the OP (which I haven't strayed from at all,
despite your statements to the contrary), let's add the fact that the 3.0
Framework will be coming out and that the most (if not all) of MS's
enterprise server line have (or will have) native CLR support add to my
orginal assertion that .NET will be here for a while.


Pete



.

Relevant Pages

  • Re: relation between .Net framework and .Net
    ... Also, for your information, sauj, Visual Studio 2005 will be the ... development environment for the new .NET Framework 2.0. ... will be known as Visual Studio 2005 and not Visual Studio .NET 2005. ...
    (microsoft.public.dotnet.framework)
  • .sdf on desktop again :-)
    ... With the new versions of SQL Server, Visual Studio and .NET Framework it ... should be possible to create SQL Server CE database files on a desktop PC ... Is it a functoinality of the development environment (i.e. ...
    (microsoft.public.sqlserver.ce)
  • Re: Common Library .NET and CF.NET
    ... Of course you have to limit your usage of the .NET Framework to the ... share among .NET and .NETCF. ... Visual Studio should define some platform symbol in all Smart ... Both builds can be made from the same source code though. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Opinions on .NET Framework?
    ... You wrote "VS .NET is the only MS development environment at this time". ... require the .NET Framework. ... acknowledged that the term I used "development platform" and the term you ... help compose the abbreviation IDE. ...
    (microsoft.public.dotnet.framework)
  • Re: Programming for Electronics Engineers
    ... >> gives you the full power of the .NET Framework. ... >Is that like a cut down version of Visual Studio? ... We're solving math problems, so ... would be learning Linux. ...
    (sci.electronics.design)
Loading