Framework installation

I'm not sure if this should go in FAQs or general.

I have a home network with a primary domain controller running Windows
2000 Server. It has .NET framework v 1.1 on it, and IIS 5 (probably
5.0).

I also have a workstation running XP Pro, Visual Studio 2005 with .NET
framework 2.0, and IIS 5.1 I have a web application I've developed
there, and I'm trying to install it on the server.

When I try to run it on server, it immediately throws an exception
trying to read the web.config file, saying it doesn't recognize the
<connectionstring> element. So I figure, Okay, it's running framework
v1.1, that's probably a v2.0 thing.

So I download the Framework 2.0 Redistributable from the Microsoft
website, and install it on the server, including running the SP1
update.

But it doesn't seem to be installed. There's now a v2_0 folder in the
\Winnt\Microsoft.Net\Framework directory tree, but IIS is still runing
v1.1 (as evidenced by the Version information when it throws the
exception). Also, when I run administrative tools on the workstation,
there's a "Microsoft .NET Framework 2.0 configuration" MSC, as well as
one for v1.1 and v1.0. Running administrative tools on the server
still only has the v1.1 configuration tool, and a search of the whole
disk for .MSC files does not turn up a 2.0 configuration MSC.

So what do I need to do to make sure 2.0 is properly installed, and
specifically, to get IIS to use it?

Thanks for any help.

daveh551
Fri Mar 07 14:21:20 CST 2008

On Mar 7, 11:59 am, gee...@gmail.com wrote:
> I'm not sure if this should go in FAQs or general.
>
> I have a home network with a primary domain controller running Windows
> 2000 Server. It has .NET framework v 1.1 on it, and IIS 5 (probably
> 5.0).
>
> I also have a workstation running XP Pro, Visual Studio 2005 with .NET
> framework 2.0, and IIS 5.1 I have a web application I've developed
> there, and I'm trying to install it on the server.
>
> When I try to run it on server, it immediately throws an exception
> trying to read the web.config file, saying it doesn't recognize the
> <connectionstring> element. So I figure, Okay, it's running framework
> v1.1, that's probably a v2.0 thing.
>
> So I download the Framework 2.0 Redistributable from the Microsoft
> website, and install it on the server, including running the SP1
> update.
>
> But it doesn't seem to be installed. There's now a v2_0 folder in the
> \Winnt\Microsoft.Net\Framework directory tree, but IIS is still runing
> v1.1 (as evidenced by the Version information when it throws the
> exception). Also, when I run administrative tools on the workstation,
> there's a "Microsoft .NET Framework 2.0 configuration" MSC, as well as
> one for v1.1 and v1.0. Running administrative tools on the server
> still only has the v1.1 configuration tool, and a search of the whole
> disk for .MSC files does not turn up a 2.0 configuration MSC.
>
> So what do I need to do to make sure 2.0 is properly installed, and
> specifically, to get IIS to use it?
>
> Thanks for any help.

Never mind, I answered my own question.

(Answer, if interested: In IIS Administration, each website has a
properties screen, with a ASP.NET tab that, among other things, has a
drop down list of .NET version to run for that web site. I changed it
there, and it worked.)