I have just upgraded from VS.NET 2002/Framework 1.0 to
VS.NET 2003/Framework 1.1 and migrated my current web dev
project to VS.NET 2003/Framework 1.1 as well. On my
local machine, this all seems to have gone well.

However, after refreshing this same project on the ISP
server that hosts my "production" version of said
project, I am getting all sorts of bizarre errors.

I am assuming this may due to the fact that my ISP is
still running .NET Framework Version:1.0.3705.288 and my
local version is 1.1.

Anybody shed any light on this or point me to a place on
Microsoft that has specific articles that might help me
figure this out.

Thanks,
Tim Heffernan

Re: 1.1 Framework Upgrade Issues... by Cowboy

Cowboy
Wed Nov 19 09:01:42 CST 2003

This is very likely, esp. if you hit breaking changes. IF the ISP also works
with version 1.1, I would have them switch your virtual root to version 1.1,
to make everything work fine. You can add a target to the config file
(accepted Framework version(s)), but it does not work 100% with web apps.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

**********************************************************************
Think Outside the Box!
**********************************************************************
"Tim H" <timandsuzi36@hotmail.com> wrote in message
news:085701c3ae8d$00a28ae0$a301280a@phx.gbl...
> I have just upgraded from VS.NET 2002/Framework 1.0 to
> VS.NET 2003/Framework 1.1 and migrated my current web dev
> project to VS.NET 2003/Framework 1.1 as well. On my
> local machine, this all seems to have gone well.
>
> However, after refreshing this same project on the ISP
> server that hosts my "production" version of said
> project, I am getting all sorts of bizarre errors.
>
> I am assuming this may due to the fact that my ISP is
> still running .NET Framework Version:1.0.3705.288 and my
> local version is 1.1.
>
> Anybody shed any light on this or point me to a place on
> Microsoft that has specific articles that might help me
> figure this out.
>
> Thanks,
> Tim Heffernan