Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start
Go Back  Xtreme Visual Basic Talk > > > Session is destroyed after calling Process.Start


Reply
 
Thread Tools Display Modes
  #1  
Old 06-20-2012, 06:44 AM
lamy's Avatar
lamy lamy is offline
Junior Contributor
 
Join Date: Jan 2003
Location: under your bed
Posts: 347
Default Session is destroyed after calling Process.Start


i have the following files:

- default.aspx (on load it sets the session variable)
- webservice.asmx (with session enabled, this calls an external cmd app using process.start)
- ajaxfilehandler.ashx (handles the upload)

the page uploads a file with jquery which is handled by the file handler (no problem with that), on the last process where i need to call a webservice which calls an external commandline application to process the uploaded file and do the needful the session is not retained

the result is it works on first run where the session is set on load, but after calling the webservice the session is destroyed, tried setting the value of the variable after calling process.start but still no session is retained

there is no problem if i remove the Process.Start, however that part is crucial to the entire operation, was thinking if there is another way to call an external executable but can't find anything

the only workaround i could think of is to create a winform app to execute that external app and have it communicate the results through database (which is really unnecessary if that alone will work)

any idea how to go about this?
__________________
slow down when you need to hurry, stop when you need to move on,
look back when you need to forget, or you might slip and leave sanity

Last edited by lamy; 06-20-2012 at 08:38 AM.
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Forum Jump

Advertisement:





Free Publications
The ASP.NET 2.0 Anthology
101 Essential Tips, Tricks & Hacks - Free 156 Page Preview. Learn the most practical features and best approaches for ASP.NET.
subscribe
Programmers Heaven C# School Book -Free 338 Page eBook
The Programmers Heaven C# School book covers the .NET framework and the C# language.
subscribe
Build Your Own ASP.NET 3.5 Web Site Using C# & VB, 3rd Edition - Free 219 Page Preview!
This comprehensive step-by-step guide will help get your database-driven ASP.NET web site up and running in no time..
subscribe
Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start
 
Session is destroyed after calling Process.Start
Session is destroyed after calling Process.Start
 
-->