Hi,

 could please send the repro steps so i can reproduce the issue and resolve it .

Thanks

Rudra roy

I ported the app in question from vs2003. The conversion process does not set up the vs2005 environment entirely. Additionally, conversion from my impression of the forums, has a habit of dropping modules and misconverting interfaces. In fact, I had to convert the project in question twice, because a module's interface was trashed. I am using the IIS for debugging, and the Response.Redirect will terminate a session, or start a second session, if there is disagreement with the IIS site name. I know that the session was terminated, in this instance.  I am not sufficiently knowledgeable to know how this might have happened, but it could be due to the vs2005 project setup.

I will attempt to build an app in vs2003 that will exhibit this behavior, and put it up.

HI,StanDav

It is due to browser security settings, if you add the web address in trusted sites list it works fine, and session doesn't expire. The alternate way is to add the following code in response header before redirecting the page:

     Response.AddHeader("P3P", "CP=\"CAO PSA OUR\"");
     Response.Redirect("mypage.aspx", false);

Hi Rex,

I have both vs2003 and vs2005 resident on the same machine (MS says its OK). The VS2003 version of the app works fine on the machine. Thus it cannot be the browser, unless vs2005 makes additional demands. I added the urls to the browser anyway, with no change.

In the vs2005 environment, I had to change the assembly name slightly, so that it would register(myapp.dll and myapp05.dll), since the projects in both environments have the same name(different locations and web site names).

I don't know if this is a factor in vs2005, but I am running w2000.

ATTN : LIN

Was that it?  Was that the extent of Community support? 

What was the recommendation?

 Was my problem insoluble?