The shock of the week -- how could I be running the old version of the framework?

  • Thread starter Thread starter Mountain Bikn' Guy
  • Start date Start date
M

Mountain Bikn' Guy

I just called:
System.Environment.Version.ToString()
and
RuntimeEnvironment.GetSystemVersion()
as a little experiment.

Both report that I'm running 1.0.3705.288. However, my IDE is VS.NET 2003
and I never installed VS.NET 2002 on this machine. I don't recall if
something else has ever forced me to install framework 1.0 on this machine
(obviously, it's on here, but I just don't recall how it got here)... but
what is shocking is that version 1.0 is the default and that all the
projects I'm building are using 1.0. I didn't previously realize this.

How can I correct this? Is there a reason for it? Can anyone explain what I
overlooked?

Thanks.
Dave
 
I just did a test as well and got what I expected....1.0 on a 1.0 build, 1.1
on a 2003 build. The only thing I can think of that would cause this is the
fact that you can build 1.0 projects in 2003, but you usually have to set it
explicitly. Check the Assembly Properties and under Common Properties,
select Build. There's a seperator on the bottom of the form titled
Supported Runtimes. It says, "By Default, add.config supports running on
..NET Framework 1.1" however, there is a change button next to it. Verify
that you are getting this and try changing it to 1.1 if it's not set. I'm
guessing that something in app.config is set to 1.0 (weird things happen and
perhaps this got set somehow) or somehow the default was changed. When you
select the Change button, you'll see three option buttons indicating 1.1,
1.0 or both 1.0 and 1.1..

HTH,

Bill
 
BTW, in addition to Steve's comment, if you have all of the Windows updates
on your machine, you'll have both Frameworks installed.
 
Thanks Bill. This is the strangest thing I've seen in a while. BTW, I'm
running W2K. I installed VS.NET 2003 on a fresh OS install several months
ago. I've never changed the supported runtimes property, but I'll go take a
look at it. I appreciate your tips.
Dave
 
Sorry... it is.....Just worked an issue this week.. which reminded me
that it is already on the machine..... when you put the OS on it... So is
MDAC 2.7
 
Steve S said:
Sorry... it is.....Just worked an issue this week.. which reminded me
that it is already on the machine..... when you put the OS on it... So is
MDAC 2.7
Click to expand...

What release of Windows XP has the .NET Framework built in? I have a whole
lab full of Windows XP machines that definitely do not have it built in, and
neither did my laptop.
 
I'm working on the issues around a laptop..... Compaq.. with XP sp1 from
the factory...... already has framework loaded on it...... seems like it
doesn't want to talk to a 2000AS server..... but another desktop
machine... XP sp1 talks just fine...... Actually, this situation is
posted in several of the other NGs, on Wed of this week......

The machines are at work..... I will check the configurations tomorrow if
I think of it..... and post the findings....... I could be in error...
but pretty sure I saw both frameworks on the machine...... It was one of
the big 'pluses'... the runtime was already on the machines.....

As for 2003... how the framework is laced into the calling stacks is very
different..... it eliminates several layers of the calling stack to get to
the actual call..... Hence the claim... do more with less..... it is
supposed to run faster....

I can't say that I have seen that yet...... management won't give me a
2003 server :(
 
From a press release:
The key features in the new operating system image include the NET
Framework, several security updates and support for IPv6.

Also see:
http://www.microsoft.com/technet/tr...nol/winxppro/evaluate/xptechov.asp?frame=true

This section provides a conceptual overview of how Windows XP lays the
foundation for an important part in the future of computing: the Microsoft
..NET Platform, which aims to provide a new level of connectivity that lets
you get more out of networking and the Internet.

And...
http://www.microsoft.com/technet/tr...nol/winxppro/evaluate/xptechov.asp?frame=true

Of course, none of that guarantees what's actually on your machines...
 
The key might be the service pack that is installed.

What better way to ensure that all Windows machines get the framework then
to include it with future service packs.

I don't know if for certain, just a guess.
 
Not that I'm trying to piss anyone off....... but here are a few
quotes.... from the MS site.....

The Microsoft® .NET initiative aims to turn this around through a framework
built around XML-based Web services that interoperate via existing open
Internet protocols such as TCP/IP and HTTP. And at the heart of the .NET
vision for knowledge workers, business users, and consumers lies the new
client operating system, Windows XP.



The programmatic backbone of this emerging platform is called the .NET
Framework. It is the culmination of several years of research and
development aimed at simplifying the process of building, deploying, and
maintaining applications. Windows XP is an essential piece of the Windows
Server System and takes its place alongside other client devices as shown in
Figure 1 below.


Powerful client software such as the .NET Compact Framework, Windows CE, and
Windows XP enable a host of smart devices-PCs, laptops, workstations,
phones, handheld computers, Tablet PCs, game consoles, and other devices to
operate in the .NET universe. Through the use of this software, smart
devices harness the power of the Internet providing you with a compelling
and immersive experience while giving you more control over their
information.



If they DIDN'T make it part of the OS... they really missed their
boat...... and their vision.... while there are references all over the
place to the .NET services, components and capabilities..... being
embedded...... until you look at the Microsoft.net directory under the
WINNT directory....... and the assembly directory on a virgin XP
machine.... this will not be answered..... as those two locations are the
trademark directories of the framework.



The framework could still be embedded within the OS... and until you look
at things well below the covers...... we might never know.....
 
Sorry... it is.....Just worked an issue this week.. which reminded me
that it is already on the machine..... when you put the OS on it...
So is MDAC 2.7
Click to expand...

MDAC is something else. .NET isn't shipped with XP. It comes as a
separate download and is probably added to SP1 but vanilla XP doesn't have
..NET. Not very weird when you consider that .NET was shipped in feb 2002 and
XP a year earlier.

FB
 
The framework is not built into XP. It has, in many cases, been
slip-streamed into the OS images by the hardware manufacturers.

-Eric
 
It was included in one of the XP updates. So if your normal installation is
CD then update from internet, it might appear to be "included" in Windows
XP.

Colin
 
I% SAY :::
It was included in one of the XP updates. So if your normal installation is
CD then update from internet, it might appear to be "included" in
Click to expand...

even worse:

0. After installing an early 1.1, Windows Update would not automatically
update the 1.1 framework.

1. When I purchased my VS.NET upgrade, I had to manually uninstall the old
1.1 framework ( which took forever !!!) and then install the new 1.1
 
Frans said:
MDAC is something else. .NET isn't shipped with XP. It comes as
a separate download and is probably added to SP1 but vanilla XP
doesn't have .NET. Not very weird when you consider that .NET was
shipped in feb 2002 and XP a year earlier.

FB
Click to expand...

It's not in -any- version of XP by default. It's also not in SP1 or in
SP1a. It's a separate download on the windows update site. It has been
slipstreamed into many installs, as has been noted here already.

Just because it's installed on your computer and -you- didn't install
it, doesn't mean it's included with the OS. Did you think that Office
was included in the OS because it is preinstalled on your new computer?

Mark
 
It's not in the RTM version, but Microsoft periodically updates their OEM
versions as service packs and updates are released. This keeps an OEM from
having to "Windows Update" every PC they ship...

Jeff
 
Back
Top