Dirk,
 
There are a couple of options you could take.
 
1.  If the logic within the aspx page is not too lengthy, I would just consume the cf webservice from asp 3.0 and skip the aspx page altogether.   
 
2.  If you have too much invested in the aspx page or this is not an option, you could use cookies or request variables to send data back and forth between asp pages (class and .net).  When there are small amounts of data I usually use pseudo encryped url variables (if the data is not sensitive) to communicate between aspx and asp pages.
 
If you need any help, please feel free to contact me offline
 
thanks,
Lyndon Hughey

 
On 6/16/05, Dirk Meilinger <[EMAIL PROTECTED]> wrote:
Hey,
 
I'm sorry for the "off topic" post but I know there are a lot of smart people on this list that skills other than CF.
 
I am working on a legacy ASP application that has to call a Coldfusion Webservice that I have written. (There..I included CF in my thread so please don't boot me Matt ) 
 
I am trying to figure out the best way to invoke the CF webservice in the ASP application and parse the results.  I have little or no ASP and .NET experience.  A little investigation into .net indicated to me that it natively hides all the fun little SOAP details and provides an easy interface to webservices.  In fact, with no .net knowledge I was able to have a working prototype up and running in an hour that invokes my web service and returns my results.  Now, the only thing I am trying to figure out is how to get this data to the ASP app. 
 
Is there a .netter out there who can tell me the best approach ? I need to be able to call .aspx  inside of an ASP app and pass data back and forth.  Is that possible?  One thought I have is creating a .net .dll and invoking it in ASP, does this seem like a logical approach?
 
I recognize that I could call the WS directly from ASP but all the examples I have found are hideously involved, if you have an easier way I would sure appreciate hearing about it.
 
Any advice would be greatly appreciated.
 
Thanks,
 
Dirk

Reply via email to