Wrox Home  
Search P2P Archive for: Go

  Return to Index  

aspx thread: Asp and ASP+ Interoperability


Message #1 by "Robert Horn" <robert@j...> on Sat, 25 May 2002 23:50:55 +1000
This is a multi-part message in MIME format.

------=_NextPart_000_007A_01C20447.02E052C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have a site that I need to start moving over to .NET. There are 
certain pages that I need to start migrating, but the whole site is 
using Session objects for the User Logon and the data connection. In the 
Microsoft documentation on the subject it says the following:

Another important thing to consider is that although your application 
can contain both ASP and ASP .NET pages, you cannot share state 
variables stored in the intrinsic Session or Application objects. You 
either need to duplicate this information in both systems or come up 
with a custom solution until your application is fully migrated. The 
bottom line is that if you have made little use of the Session and 
Application objects, you should be in good shape. If, on the other hand, 
you use these objects extensively, you will need to proceed with caution 
and perhaps come up with a custom short-term solution to sharing your 
state.

Does anyone know how to get variables across between ASP and ASP.NET 
without using cookies and the QueryString (UserID and ConnectionString 
are not something I want to be seen by the user)?

Thanks
Robert


Message #2 by "Albert Davis" <albertdavis@h...> on Sat, 25 May 2002 11:57:02 -0400
Is your connection string the same across the entire application? (No matter 
what page the user is on...)


>From: "Robert Horn" <robert@j...>
>Reply-To: "ASP+" <aspx@p...>
>To: "ASP+" <aspx@p...>
>Subject: [aspx] Asp and ASP+ Interoperability
>Date: Sat, 25 May 2002 23:50:55 +1000
>
>I have a site that I need to start moving over to .NET. There are certain 
>pages that I need to start migrating, but the whole site is using Session 
>objects for the User Logon and the data connection. In the Microsoft 
>documentation on the subject it says the following:
>
>Another important thing to consider is that although your application can 
>contain both ASP and ASP .NET pages, you cannot share state variables 
>stored in the intrinsic Session or Application objects. You either need to 
>duplicate this information in both systems or come up with a custom 
>solution until your application is fully migrated. The bottom line is that 
>if you have made little use of the Session and Application objects, you 
>should be in good shape. If, on the other hand, you use these objects 
>extensively, you will need to proceed with caution and perhaps come up with 
>a custom short-term solution to sharing your state.
>
>Does anyone know how to get variables across between ASP and ASP.NET 
>without using cookies and the QueryString (UserID and ConnectionString are 
>not something I want to be seen by the user)?
>
>Thanks
>Robert
>
>




_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

Message #3 by "Robert Horn" <robertho@m...> on Sun, 26 May 2002 08:41:45 +1000
Yes, except the connection string has the Username and Password for that
specific user. I could have handled it if the Username and Password were the
same throughout, but the site relies heavily on the Users and Roles built
into SQL.
----- Original Message -----
From: "Albert Davis" <albertdavis@h...>
To: "ASP+" <aspx@p...>
Sent: Sunday, May 26, 2002 1:57 AM
Subject: [aspx] Re: Asp and ASP+ Interoperability


> Is your connection string the same across the entire application? (No
matter
> what page the user is on...)
>
>
> >From: "Robert Horn" <robert@j...>
> >Reply-To: "ASP+" <aspx@p...>
> >To: "ASP+" <aspx@p...>
> >Subject: [aspx] Asp and ASP+ Interoperability
> >Date: Sat, 25 May 2002 23:50:55 +1000
> >
> >I have a site that I need to start moving over to .NET. There are certain
> >pages that I need to start migrating, but the whole site is using Session
> >objects for the User Logon and the data connection. In the Microsoft
> >documentation on the subject it says the following:
> >
> >Another important thing to consider is that although your application can
> >contain both ASP and ASP .NET pages, you cannot share state variables
> >stored in the intrinsic Session or Application objects. You either need
to
> >duplicate this information in both systems or come up with a custom
> >solution until your application is fully migrated. The bottom line is
that
> >if you have made little use of the Session and Application objects, you
> >should be in good shape. If, on the other hand, you use these objects
> >extensively, you will need to proceed with caution and perhaps come up
with
> >a custom short-term solution to sharing your state.
> >
> >Does anyone know how to get variables across between ASP and ASP.NET
> >without using cookies and the QueryString (UserID and ConnectionString
are
> >not something I want to be seen by the user)?
> >
> >Thanks
> >Robert
> >
> >
>
>
>
>
> _________________________________________________________________
> Chat with friends online, try MSN Messenger: http://messenger.msn.com
>
>

Message #4 by "Albert Davis" <albertdavis@h...> on Sat, 25 May 2002 19:15:14 -0400
Well your in a tough position while upgrading...  My suggestion is to either 
build your own temporary state management object that sits on the back-end 
of your web server like a .NET Remoting component that you can communicate 
to from ASP (with an RCW) and ASPX, that stores the userid and connection 
string which has a unique sessionid (that more than likely you are going to 
have to generate [a hash code could work]) and then pass that sessionid 
between your ASP and ASPX pages so they can then query the Remoting object 
for the userid and connection string information when needed.  There are 
many more ways other than remoting as well, for simplicity you could when 
gaining the credentials of your user serialize that user object to file disk 
(you would need to generate a unique name for the file) and then pass the 
file name to the ASPX page which would then deserialize the user object and 
contain the necessary information it needed & vice versa.

hth,
Al

>From: "Robert Horn" <robertho@m...>
>Reply-To: "ASP+" <aspx@p...>
>To: "ASP+" <aspx@p...>
>Subject: [aspx] Re: Asp and ASP+ Interoperability
>Date: Sun, 26 May 2002 08:41:45 +1000
>
>Yes, except the connection string has the Username and Password for that
>specific user. I could have handled it if the Username and Password were 
>the
>same throughout, but the site relies heavily on the Users and Roles built
>into SQL.
>----- Original Message -----
>From: "Albert Davis" <albertdavis@h...>
>To: "ASP+" <aspx@p...>
>Sent: Sunday, May 26, 2002 1:57 AM
>Subject: [aspx] Re: Asp and ASP+ Interoperability
>
>
> > Is your connection string the same across the entire application? (No
>matter
> > what page the user is on...)
> >
> >
> > >From: "Robert Horn" <robert@j...>
> > >Reply-To: "ASP+" <aspx@p...>
> > >To: "ASP+" <aspx@p...>
> > >Subject: [aspx] Asp and ASP+ Interoperability
> > >Date: Sat, 25 May 2002 23:50:55 +1000
> > >
> > >I have a site that I need to start moving over to .NET. There are 
>certain
> > >pages that I need to start migrating, but the whole site is using 
>Session
> > >objects for the User Logon and the data connection. In the Microsoft
> > >documentation on the subject it says the following:
> > >
> > >Another important thing to consider is that although your application 
>can
> > >contain both ASP and ASP .NET pages, you cannot share state variables
> > >stored in the intrinsic Session or Application objects. You either need
>to
> > >duplicate this information in both systems or come up with a custom
> > >solution until your application is fully migrated. The bottom line is
>that
> > >if you have made little use of the Session and Application objects, you
> > >should be in good shape. If, on the other hand, you use these objects
> > >extensively, you will need to proceed with caution and perhaps come up
>with
> > >a custom short-term solution to sharing your state.
> > >
> > >Does anyone know how to get variables across between ASP and ASP.NET
> > >without using cookies and the QueryString (UserID and ConnectionString
>are
> > >not something I want to be seen by the user)?
> > >
> > >Thanks
> > >Robert
> > >
> > >
> >
> >
> >
> >
> > _________________________________________________________________
> > Chat with friends online, try MSN Messenger: http://messenger.msn.com
> >
> >
>
>




_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

Message #5 by "Robert Horn" <robertho@m...> on Sun, 26 May 2002 10:37:03 +1000
Thanks for the help Al, this gives me two directions. I will most likely use
the last solution, as that is quite easy to implement.
----- Original Message -----
From: "Albert Davis" <albertdavis@h...>
To: "ASP+" <aspx@p...>
Sent: Sunday, May 26, 2002 9:15 AM
Subject: [aspx] Re: Asp and ASP+ Interoperability


> Well your in a tough position while upgrading...  My suggestion is to
either
> build your own temporary state management object that sits on the back-end
> of your web server like a .NET Remoting component that you can communicate
> to from ASP (with an RCW) and ASPX, that stores the userid and connection
> string which has a unique sessionid (that more than likely you are going
to
> have to generate [a hash code could work]) and then pass that sessionid
> between your ASP and ASPX pages so they can then query the Remoting object
> for the userid and connection string information when needed.  There are
> many more ways other than remoting as well, for simplicity you could when
> gaining the credentials of your user serialize that user object to file
disk
> (you would need to generate a unique name for the file) and then pass the
> file name to the ASPX page which would then deserialize the user object
and
> contain the necessary information it needed & vice versa.
>
> hth,
> Al
>
> >From: "Robert Horn" <robertho@m...>
> >Reply-To: "ASP+" <aspx@p...>
> >To: "ASP+" <aspx@p...>
> >Subject: [aspx] Re: Asp and ASP+ Interoperability
> >Date: Sun, 26 May 2002 08:41:45 +1000
> >
> >Yes, except the connection string has the Username and Password for that
> >specific user. I could have handled it if the Username and Password were
> >the
> >same throughout, but the site relies heavily on the Users and Roles built
> >into SQL.
> >----- Original Message -----
> >From: "Albert Davis" <albertdavis@h...>
> >To: "ASP+" <aspx@p...>
> >Sent: Sunday, May 26, 2002 1:57 AM
> >Subject: [aspx] Re: Asp and ASP+ Interoperability
> >
> >
> > > Is your connection string the same across the entire application? (No
> >matter
> > > what page the user is on...)
> > >
> > >
> > > >From: "Robert Horn" <robert@j...>
> > > >Reply-To: "ASP+" <aspx@p...>
> > > >To: "ASP+" <aspx@p...>
> > > >Subject: [aspx] Asp and ASP+ Interoperability
> > > >Date: Sat, 25 May 2002 23:50:55 +1000
> > > >
> > > >I have a site that I need to start moving over to .NET. There are
> >certain
> > > >pages that I need to start migrating, but the whole site is using
> >Session
> > > >objects for the User Logon and the data connection. In the Microsoft
> > > >documentation on the subject it says the following:
> > > >
> > > >Another important thing to consider is that although your application
> >can
> > > >contain both ASP and ASP .NET pages, you cannot share state variables
> > > >stored in the intrinsic Session or Application objects. You either
need
> >to
> > > >duplicate this information in both systems or come up with a custom
> > > >solution until your application is fully migrated. The bottom line is
> >that
> > > >if you have made little use of the Session and Application objects,
you
> > > >should be in good shape. If, on the other hand, you use these objects
> > > >extensively, you will need to proceed with caution and perhaps come
up
> >with
> > > >a custom short-term solution to sharing your state.
> > > >
> > > >Does anyone know how to get variables across between ASP and ASP.NET
> > > >without using cookies and the QueryString (UserID and
ConnectionString
> >are
> > > >not something I want to be seen by the user)?
> > > >
> > > >Thanks
> > > >Robert
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > _________________________________________________________________
> > > Chat with friends online, try MSN Messenger: http://messenger.msn.com
> > >
> > >
> >
> >
>
>
>
>
> _________________________________________________________________
> MSN Photos is the easiest way to share and print your photos:
> http://photos.msn.com/support/worldwide.aspx
>
>

Message #6 by Feduke Cntr Charles R <FedukeCR@m...> on Tue, 28 May 2002 08:55:36 -0400
	Okay, I know there's alot of people out there currently upgrading
their ASP to ASP.NET so *someone* has had to have done this the correct way
already (a ISAPI library that communicates b/w IIS's ASP and aspnet_wp).  I
know this is a little bit harder to do if you consider that someone can put
something like a "Scripting.FileSystemObject" in thier ASP Session
collection, but if you have done something that handles primitives (and
maybe ADODB stuff) please post the source code somewhere and notify the list
of it.

	I find it troublesome that MS didn't include something like this
with .NET.

- Chuck

-----Original Message-----
From: Robert Horn [mailto:robertho@m...]
Sent: Saturday, May 25, 2002 8:37 PM
To: ASP+
Subject: [aspx] Re: Asp and ASP+ Interoperability


Thanks for the help Al, this gives me two directions. I will most likely use
the last solution, as that is quite easy to implement.
----- Original Message -----
From: "Albert Davis" <albertdavis@h...>
To: "ASP+" <aspx@p...>
Sent: Sunday, May 26, 2002 9:15 AM
Subject: [aspx] Re: Asp and ASP+ Interoperability


> Well your in a tough position while upgrading...  My suggestion is to
either
> build your own temporary state management object that sits on the back-end
> of your web server like a .NET Remoting component that you can communicate
> to from ASP (with an RCW) and ASPX, that stores the userid and connection
> string which has a unique sessionid (that more than likely you are going
to
> have to generate [a hash code could work]) and then pass that sessionid
> between your ASP and ASPX pages so they can then query the Remoting object
> for the userid and connection string information when needed.  There are
> many more ways other than remoting as well, for simplicity you could when
> gaining the credentials of your user serialize that user object to file
disk
> (you would need to generate a unique name for the file) and then pass the
> file name to the ASPX page which would then deserialize the user object
and
> contain the necessary information it needed & vice versa.
>
> hth,
> Al
>
> >From: "Robert Horn" <robertho@m...>
> >Reply-To: "ASP+" <aspx@p...>
> >To: "ASP+" <aspx@p...>
> >Subject: [aspx] Re: Asp and ASP+ Interoperability
> >Date: Sun, 26 May 2002 08:41:45 +1000
> >
> >Yes, except the connection string has the Username and Password for that
> >specific user. I could have handled it if the Username and Password were
> >the
> >same throughout, but the site relies heavily on the Users and Roles built
> >into SQL.
> >----- Original Message -----
> >From: "Albert Davis" <albertdavis@h...>
> >To: "ASP+" <aspx@p...>
> >Sent: Sunday, May 26, 2002 1:57 AM
> >Subject: [aspx] Re: Asp and ASP+ Interoperability
> >
> >
> > > Is your connection string the same across the entire application? (No
> >matter
> > > what page the user is on...)
> > >
> > >
> > > >From: "Robert Horn" <robert@j...>
> > > >Reply-To: "ASP+" <aspx@p...>
> > > >To: "ASP+" <aspx@p...>
> > > >Subject: [aspx] Asp and ASP+ Interoperability
> > > >Date: Sat, 25 May 2002 23:50:55 +1000
> > > >
> > > >I have a site that I need to start moving over to .NET. There are
> >certain
> > > >pages that I need to start migrating, but the whole site is using
> >Session
> > > >objects for the User Logon and the data connection. In the Microsoft
> > > >documentation on the subject it says the following:
> > > >
> > > >Another important thing to consider is that although your application
> >can
> > > >contain both ASP and ASP .NET pages, you cannot share state variables
> > > >stored in the intrinsic Session or Application objects. You either
need
> >to
> > > >duplicate this information in both systems or come up with a custom
> > > >solution until your application is fully migrated. The bottom line is
> >that
> > > >if you have made little use of the Session and Application objects,
you
> > > >should be in good shape. If, on the other hand, you use these objects
> > > >extensively, you will need to proceed with caution and perhaps come
up
> >with
> > > >a custom short-term solution to sharing your state.
> > > >
> > > >Does anyone know how to get variables across between ASP and ASP.NET
> > > >without using cookies and the QueryString (UserID and
ConnectionString
> >are
> > > >not something I want to be seen by the user)?
> > > >
> > > >Thanks
> > > >Robert
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > _________________________________________________________________
> > > Chat with friends online, try MSN Messenger: http://messenger.msn.com
> > >
> > >
> >
> >
>
>
>
>
> _________________________________________________________________
> MSN Photos is the easiest way to share and print your photos:
> http://photos.msn.com/support/worldwide.aspx
>
>



  Return to Index