how big is your site? If time isn't a factor convert the entire site to 2.0.
Why have 1 page in 2.0 and the other pages running .NET 1.1
what I have done in this scenario was run the old site under .NET 1.1, and I
created a new site under 2.0 and we would slowly migrate the site to 2.0 so
half of the site would run under 1.1 and the other half under 2.0 while the
migration was happening.
> We have one web application created in VS 2003 / Framework 1.1.
>
[quoted text clipped - 3 lines]
>
> Regards /Snedker
And, that is the only way you can truly do it.
Most 1.1 sites will succesfully convert to 2.0 without any problem, however,
so why go through the circus hoops when it is not needed.

Signature
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
Co-author: Microsoft Expression Web Bible (upcoming)
************************************************
Think outside the box!
************************************************
> how big is your site? If time isn't a factor convert the entire site to
> 2.0. Why have 1 page in 2.0 and the other pages running .NET 1.1
[quoted text clipped - 11 lines]
>>
>> Regards /Snedker
Mike - 13 Jun 2007 14:04 GMT
Most 1.1 sites will succesfully convert to 2.0 without any problem, however,
so why go through the circus hoops when it is not needed. -
this is true but I've taken on projects where the .NET 1.1 web apps were
still written like ASP but with an aspx extension so I had to a true
re-write of the application.
No kidding, I started one project to do some .NET 1.1 to 2.0 migration and
the entire 1.1 app was written in ASP. All the developer did was a copy and
paiste from him asp web site into a .NET project and gave the pages an aspx
extension. There was no code behind, the code had nothing to do with .NET at
all. So when I took it over I was pretty much starting from scratch. I've
seen many a projects like that. It seems like some developers aren't taken
the time to learn .NET, and they just want to create something in the .NET
IDE. Why create an ASP app in the .NET IDE or even use the .NET resources to
run the app? Makes no sense to me.
> And, that is the only way you can truly do it.
>
[quoted text clipped - 16 lines]
>>>
>>> Regards /Snedker
Mark Rae - 13 Jun 2007 14:51 GMT
> Most 1.1 sites will succesfully convert to 2.0 without any problem,
> however,
[quoted text clipped - 12 lines]
> create something in the .NET IDE. Why create an ASP app in the .NET IDE or
> even use the .NET resources to run the app? Makes no sense to me.
I've been tasked with similar upgrades - all that it means in the long run
is that price goes up... :-)

Signature
http://www.markrae.net
Mike - 13 Jun 2007 16:20 GMT
I've been tasked with similar upgrades - all that it means in the long run
> is that price goes up... :-)
yes it does. WAY UP! :)
>> Most 1.1 sites will succesfully convert to 2.0 without any problem,
>> however,
[quoted text clipped - 15 lines]
> I've been tasked with similar upgrades - all that it means in the long run
> is that price goes up... :-)
Mark Rae - 13 Jun 2007 16:25 GMT
> I've been tasked with similar upgrades - all that it means in the long run
>> is that price goes up... :-)
> yes it does. WAY UP! :)
You know the mantra:
"Wheresoever shall two or more contractors be gathered together in one
place, yea verily shall they smile sweetly and raise the invoice..."
Here endeth the lesson.
Amen.

Signature
http://www.markrae.net
Mike - 13 Jun 2007 17:06 GMT
LMAO!
>> I've been tasked with similar upgrades - all that it means in the long
>> run
[quoted text clipped - 9 lines]
>
> Amen.