ASP.Net 1.0 in 3.5 container

[Grant Molloy]

Hi all..

So my boss came to me yesterday and asks me to look into and build a
prototype for an ASP.Net 3.5 web app which would need to act as a container
for an ancient ASP.Net 1.0 app..
1.0 app is well and truely past due for life cycling, but org doesn't want
to do big bang tech refresh, as have recently had fingers burnt on another!

The request...
"The prefered approach would be to come up with a solution that allows
existing functionality to remain 'as-is' and new functionality to be
developed in .Net 3.5.
Over time existing functionality can be upgraded (from 1.0 to 3.5) as the
need arises.

Can you look at building a simple prototype in 3.5 that acts as a container
to 'Project ABC' web presentation functionality? The focus would be to
identify possible options for integration between 3.5 and 1.0 at a
presentation level..  Some key challenges include
* how to host 1.0 components within a 3.5 container
* how to integrate navigation from UIP (3.5) to 1.0 model
* how to sync data between 3.5 and 1.0 (eg. Session state)
* how to best isolate 1.0 functionality to allow clean separation from a
maintenance perspective, as well as ease to be able to upgrade any piece of
1.0 functionality independently of other functionality. "

As I'm waiting for my environment to be commissioned, I've been fruitlessly
scouring the web. It seems like the web has cleansed itself of most. Net
1.0 info!!

Has anyone out there faced and defeated (or turned and run away screaming
for their mummy) this type of beast?

Can you use. Net 1.0 user controls in 3.5?

Grant

Re: ASP.Net 1.0 in 3.5 container

[Preet Sangha]

I've not done this, but I'm wondering if you can just use two virtual
directories each with a different WebApplication framework/type? And
Hyperlink between them? You can upgrade the old pages as time allows, and
 as time allows add new functionality the 3.5 application?

On 13 June 2012 17:04, Grant Molloy  wrote:

> Hi all..
>
> So my boss came to me yesterday and asks me to look into and build a
> prototype for an ASP.Net 3.5 web app which would need to act as a container
> for an ancient ASP.Net 1.0 app..
> 1.0 app is well and truely past due for life cycling, but org doesn't want
> to do big bang tech refresh, as have recently had fingers burnt on another!
>
> The request...
> "The prefered approach would be to come up with a solution that allows
> existing functionality to remain 'as-is' and new functionality to be
> developed in .Net 3.5.
> Over time existing functionality can be upgraded (from 1.0 to 3.5) as the
> need arises.
>
> Can you look at building a simple prototype in 3.5 that acts as a
> container to 'Project ABC' web presentation functionality? The focus would
> be to identify possible options for integration between 3.5 and 1.0 at a
> presentation level..  Some key challenges include
> * how to host 1.0 components within a 3.5 container
> * how to integrate navigation from UIP (3.5) to 1.0 model
> * how to sync data between 3.5 and 1.0 (eg. Session state)
> * how to best isolate 1.0 functionality to allow clean separation from a
> maintenance perspective, as well as ease to be able to upgrade any piece of
> 1.0 functionality independently of other functionality. "
>
> As I'm waiting for my environment to be commissioned, I've been
> fruitlessly scouring the web. It seems like the web has cleansed itself of
> most. Net 1.0 info!!
>
> Has anyone out there faced and defeated (or turned and run away screaming
> for their mummy) this type of beast?
>
> Can you use. Net 1.0 user controls in 3.5?
>
> Grant
>



-- 
regards,
Preet, Overlooking the Ocean, Auckland

Re: ASP.Net 1.0 in 3.5 container

[Michael Ridland]

With that you can also use a distributed session state.



On Wed, Jun 13, 2012 at 4:51 PM, Preet Sangha  wrote:

> I've not done this, but I'm wondering if you can just use two virtual
> directories each with a different WebApplication framework/type? And
> Hyperlink between them? You can upgrade the old pages as time allows, and
>  as time allows add new functionality the 3.5 application?
>
>
> On 13 June 2012 17:04, Grant Molloy  wrote:
>
>> Hi all..
>>
>> So my boss came to me yesterday and asks me to look into and build a
>> prototype for an ASP.Net 3.5 web app which would need to act as a container
>> for an ancient ASP.Net 1.0 app..
>> 1.0 app is well and truely past due for life cycling, but org doesn't
>> want to do big bang tech refresh, as have recently had fingers burnt on
>> another!
>>
>> The request...
>> "The prefered approach would be to come up with a solution that allows
>> existing functionality to remain 'as-is' and new functionality to be
>> developed in .Net 3.5.
>> Over time existing functionality can be upgraded (from 1.0 to 3.5) as the
>> need arises.
>>
>> Can you look at building a simple prototype in 3.5 that acts as a
>> container to 'Project ABC' web presentation functionality? The focus would
>> be to identify possible options for integration between 3.5 and 1.0 at a
>> presentation level..  Some key challenges include
>> * how to host 1.0 components within a 3.5 container
>> * how to integrate navigation from UIP (3.5) to 1.0 model
>> * how to sync data between 3.5 and 1.0 (eg. Session state)
>> * how to best isolate 1.0 functionality to allow clean separation from a
>> maintenance perspective, as well as ease to be able to upgrade any piece of
>> 1.0 functionality independently of other functionality. "
>>
>> As I'm waiting for my environment to be commissioned, I've been
>> fruitlessly scouring the web. It seems like the web has cleansed itself of
>> most. Net 1.0 info!!
>>
>> Has anyone out there faced and defeated (or turned and run away screaming
>> for their mummy) this type of beast?
>>
>> Can you use. Net 1.0 user controls in 3.5?
>>
>> Grant
>>
>
>
>
> --
> regards,
> Preet, Overlooking the Ocean, Auckland
>



-- 

*Michael Ridland | ThinkSmart Digital*
Managing Director
P. 0404 865 350
E. mich...@thinksmartdigital.com.au
W. www.thinksmartdigital.com.au
T. www.twitter.com/rid00z
L. au.linkedin.com/in/michaelridland


 

Re: ASP.Net 1.0 in 3.5 container

[Preet Sangha]

Sorry Michael I don't know - I've not touched ASP.NET (except for WCF) for
years.

On 13 June 2012 18:58, Michael Ridland  wrote:

>
> With that you can also use a distributed session state.
>
>
>
> On Wed, Jun 13, 2012 at 4:51 PM, Preet Sangha wrote:
>
>> I've not done this, but I'm wondering if you can just use two virtual
>> directories each with a different WebApplication framework/type? And
>> Hyperlink between them? You can upgrade the old pages as time allows, and
>>  as time allows add new functionality the 3.5 application?
>>
>>
>> On 13 June 2012 17:04, Grant Molloy  wrote:
>>
>>> Hi all..
>>>
>>> So my boss came to me yesterday and asks me to look into and build a
>>> prototype for an ASP.Net 3.5 web app which would need to act as a container
>>> for an ancient ASP.Net 1.0 app..
>>> 1.0 app is well and truely past due for life cycling, but org doesn't
>>> want to do big bang tech refresh, as have recently had fingers burnt on
>>> another!
>>>
>>> The request...
>>> "The prefered approach would be to come up with a solution that allows
>>> existing functionality to remain 'as-is' and new functionality to be
>>> developed in .Net 3.5.
>>> Over time existing functionality can be upgraded (from 1.0 to 3.5) as
>>> the need arises.
>>>
>>> Can you look at building a simple prototype in 3.5 that acts as a
>>> container to 'Project ABC' web presentation functionality? The focus would
>>> be to identify possible options for integration between 3.5 and 1.0 at a
>>> presentation level..  Some key challenges include
>>> * how to host 1.0 components within a 3.5 container
>>> * how to integrate navigation from UIP (3.5) to 1.0 model
>>> * how to sync data between 3.5 and 1.0 (eg. Session state)
>>> * how to best isolate 1.0 functionality to allow clean separation from a
>>> maintenance perspective, as well as ease to be able to upgrade any piece of
>>> 1.0 functionality independently of other functionality. "
>>>
>>> As I'm waiting for my environment to be commissioned, I've been
>>> fruitlessly scouring the web. It seems like the web has cleansed itself of
>>> most. Net 1.0 info!!
>>>
>>> Has anyone out there faced and defeated (or turned and run away
>>> screaming for their mummy) this type of beast?
>>>
>>> Can you use. Net 1.0 user controls in 3.5?
>>>
>>> Grant
>>>
>>
>>
>>
>> --
>> regards,
>> Preet, Overlooking the Ocean, Auckland
>>
>
>
>
> --
>
> *Michael Ridland | ThinkSmart Digital*
> Managing Director
> P. 0404 865 350
> E. mich...@thinksmartdigital.com.au
> W. www.thinksmartdigital.com.au
> T. www.twitter.com/rid00z
> L. au.linkedin.com/in/michaelridland
>
>
>  
>
>


-- 
regards,
Preet, Overlooking the Ocean, Auckland

Re: ASP.Net 1.0 in 3.5 container

[djones147]

Try converting it, there will be some problems. But as long as you stop the 
wizard from converting the web type you should be able to fix in a couple of 
weeks. It's the components that were used in the site that will cause you the 
most grief, but back in 1.0 days there wasn't the framework mania that exists 
today.  

Good luck

Davy
Hexed into a portable ouija board. 

-Original Message-
From: Preet Sangha 
Sender: ozdotnet-boun...@ozdotnet.com
Date: Wed, 13 Jun 2012 19:12:06 
To: ozDotNet
Reply-To: ozDotNet 
Subject: Re: ASP.Net 1.0 in 3.5 container

Sorry Michael I don't know - I've not touched ASP.NET (except for WCF) for
years.

On 13 June 2012 18:58, Michael Ridland  wrote:

>
> With that you can also use a distributed session state.
>
>
>
> On Wed, Jun 13, 2012 at 4:51 PM, Preet Sangha wrote:
>
>> I've not done this, but I'm wondering if you can just use two virtual
>> directories each with a different WebApplication framework/type? And
>> Hyperlink between them? You can upgrade the old pages as time allows, and
>>  as time allows add new functionality the 3.5 application?
>>
>>
>> On 13 June 2012 17:04, Grant Molloy  wrote:
>>
>>> Hi all..
>>>
>>> So my boss came to me yesterday and asks me to look into and build a
>>> prototype for an ASP.Net 3.5 web app which would need to act as a container
>>> for an ancient ASP.Net 1.0 app..
>>> 1.0 app is well and truely past due for life cycling, but org doesn't
>>> want to do big bang tech refresh, as have recently had fingers burnt on
>>> another!
>>>
>>> The request...
>>> "The prefered approach would be to come up with a solution that allows
>>> existing functionality to remain 'as-is' and new functionality to be
>>> developed in .Net 3.5.
>>> Over time existing functionality can be upgraded (from 1.0 to 3.5) as
>>> the need arises.
>>>
>>> Can you look at building a simple prototype in 3.5 that acts as a
>>> container to 'Project ABC' web presentation functionality? The focus would
>>> be to identify possible options for integration between 3.5 and 1.0 at a
>>> presentation level..  Some key challenges include
>>> * how to host 1.0 components within a 3.5 container
>>> * how to integrate navigation from UIP (3.5) to 1.0 model
>>> * how to sync data between 3.5 and 1.0 (eg. Session state)
>>> * how to best isolate 1.0 functionality to allow clean separation from a
>>> maintenance perspective, as well as ease to be able to upgrade any piece of
>>> 1.0 functionality independently of other functionality. "
>>>
>>> As I'm waiting for my environment to be commissioned, I've been
>>> fruitlessly scouring the web. It seems like the web has cleansed itself of
>>> most. Net 1.0 info!!
>>>
>>> Has anyone out there faced and defeated (or turned and run away
>>> screaming for their mummy) this type of beast?
>>>
>>> Can you use. Net 1.0 user controls in 3.5?
>>>
>>> Grant
>>>
>>
>>
>>
>> --
>> regards,
>> Preet, Overlooking the Ocean, Auckland
>>
>
>
>
> --
>
> *Michael Ridland | ThinkSmart Digital*
> Managing Director
> P. 0404 865 350
> E. mich...@thinksmartdigital.com.au
> W. www.thinksmartdigital.com.au
> T. www.twitter.com/rid00z
> L. au.linkedin.com/in/michaelridland
>
>
>  <http://au.linkedin.com/in/michaelridland>
>
>


-- 
regards,
Preet, Overlooking the Ocean, Auckland

Re: ASP.Net 1.0 in 3.5 container

[Jamie Surman]

I've worked at places that have done this. Use virtual directories for the 
separate dot net versions, and you will need each one to be running a separate 
application pool set to the appropriate version.
 
We actually had classic/1.1/2.0/3.5 all running on the same web site (note I 
wouldn't advise this setup personally).
 


 From: Preet Sangha 
To: ozDotNet  
Sent: Wednesday, 13 June 2012 6:51 PM
Subject: Re: ASP.Net 1.0 in 3.5 container
  

I've not done this, but I'm wondering if you can just use two virtual 
directories each with a different WebApplication framework/type? And Hyperlink 
between them? You can upgrade the old pages as time allows, and  as time allows 
add new functionality the 3.5 application?


On 13 June 2012 17:04, Grant Molloy  wrote:

Hi all.. 
>So my boss came to me yesterday and asks me to look into and build a prototype 
>for an ASP.Net 3.5 web app which would need to act as a container for an 
>ancient ASP.Net 1.0 app..
>1.0 app is well and truely past due for life cycling, but org doesn't want to 
>do big bang tech refresh, as have recently had fingers burnt on another!
> 
>The request...
>"The prefered approach would be to come up with a solution that allows 
>existing functionality to remain 'as-is' and new functionality to be developed 
>in .Net 3.5.
>Over time existing functionality can be upgraded (from 1.0 to 3.5) as the need 
>arises. 
>Can you look at building a simple prototype in 3.5 that acts as a container to 
>'Project ABC' web presentation functionality? The focus would be to identify 
>possible options for integration between 3.5 and 1.0 at a presentation 
>level..  Some key challenges include
>* how to host 1.0 components within a 3.5 container
>* how to integrate navigation from UIP (3.5) to 1.0 model
>* how to sync data between 3.5 and 1.0 (eg. Session state)
>* how to best isolate 1.0 functionality to allow clean separation from a 
>maintenance perspective, as well as ease to be able to upgrade any piece of 
>1.0 functionality independently of other functionality. " 
>As I'm waiting for my environment to be commissioned, I've been fruitlessly 
>scouring the web. It seems like the web has cleansed itself of most. Net 1.0 
>info!! 
>Has anyone out there faced and defeated (or turned and run away screaming for 
>their mummy) this type of beast? 
>Can you use. Net 1.0 user controls in 3.5?Grant
> 


-- 
regards,
Preet, Overlooking the Ocean, Auckland

Re: ASP.Net 1.0 in 3.5 container

[Grant Molloy]

Thanks all for your suggestions.
In relation to IIS,  my memory is telling me that .Net 1.0 with IIS 6.0 on
Win 2003 server needs to be run in IIS 5.0 isolation mode.  Correct?

I've not run .Net 3.5 apps with IIS 5.0 isolation mode on before. What
affect does this have?
 On 13/06/2012 7:41 PM, "Jamie Surman"  wrote:

> I've worked at places that have done this. Use virtual directories for the
> separate dot net versions, and you will need each one to be running a
> separate application pool set to the appropriate version.
>
> We actually had classic/1.1/2.0/3.5 all running on the same web site (note
> I wouldn't advise this setup personally).
>
>*From:* Preet Sangha 
> *To:* ozDotNet 
> *Sent:* Wednesday, 13 June 2012 6:51 PM
> *Subject:* Re: ASP.Net 1.0 in 3.5 container
>
> I've not done this, but I'm wondering if you can just use two virtual
> directories each with a different WebApplication framework/type? And
> Hyperlink between them? You can upgrade the old pages as time allows, and
>  as time allows add new functionality the 3.5 application?
>
> On 13 June 2012 17:04, Grant Molloy  wrote:
>
> Hi all..
> So my boss came to me yesterday and asks me to look into and build a
> prototype for an ASP.Net 3.5 web app which would need to act as a container
> for an ancient ASP.Net 1.0 app..
> 1.0 app is well and truely past due for life cycling, but org doesn't want
> to do big bang tech refresh, as have recently had fingers burnt on another!
> The request...
> "The prefered approach would be to come up with a solution that allows
> existing functionality to remain 'as-is' and new functionality to be
> developed in .Net 3.5.
> Over time existing functionality can be upgraded (from 1.0 to 3.5) as the
> need arises.
> Can you look at building a simple prototype in 3.5 that acts as a
> container to 'Project ABC' web presentation functionality? The focus would
> be to identify possible options for integration between 3.5 and 1.0 at a
> presentation level..  Some key challenges include
> * how to host 1.0 components within a 3.5 container
> * how to integrate navigation from UIP (3.5) to 1.0 model
> * how to sync data between 3.5 and 1.0 (eg. Session state)
> * how to best isolate 1.0 functionality to allow clean separation from a
> maintenance perspective, as well as ease to be able to upgrade any piece of
> 1.0 functionality independently of other functionality. "
> As I'm waiting for my environment to be commissioned, I've been
> fruitlessly scouring the web. It seems like the web has cleansed itself of
> most. Net 1.0 info!!
> Has anyone out there faced and defeated (or turned and run away screaming
> for their mummy) this type of beast?
> Can you use. Net 1.0 user controls in 3.5?
> Grant
>
>
>
>
> --
> regards,
> Preet, Overlooking the Ocean, Auckland
>
>
>