Hi SevDer,
From your description, you're encountering some problem on ASP.NET
application's sessionstate data, you found the session state in your
ASP.NET 2.0 web application (in product environment) will get lost
unexpectedly, correct?
According to your description, your application is mainly divided into two
parts:
** the main framework application, deployed in the top virtual directory
** some module components that is deployed in a sub directory and could be
updated when there is new module added or old module remoted
As for the following things you mentioned:
=========
1. When I build a referenced library project, it adds a new web.config
under
my app which is not required at all and I don't know why this started.
2. When I build myapp it also adds this web.config (I just have to delete
it
each time as it does not fit my scenario and throws exceptions when exists)
===========
do you mean it will add a new web.config file under the application's sub
directory or means the new web.config file will override the original root
web .config file? For "reference library project", is it a normal class
library project? If so, I think it should only contains a App.config file
and will output an assembly(dll) file rather than web.config file. If the
reference library is abit particular, would you provide some further
description on it?
So far, based on my experience, for session state lossing, if you're using
inproc session, it is probably caused by the ASP.NET web applicaiton
restart(or the worker process recycle). There are many causes could make
asp.net application restart:
** process recycle
** many aspx page get recompiled dynamically
** web.config file has been modified
** bin dir has been modified
** some antivirus software that modify application files
....
For your scenario, if your module components will be updated during
application running and modify some of the above things, it cause the
appliation to restart. You can also put some trace statement in the
Application_Start global event to see whether you can capture such
application start behavior.
here are some other web articles that mentioned some of these behaviors:
http://www.kbalertz.com/871042/application.aspx http://support.microsoft.com/kb/316148 http://www.eggheadcafe.com/articles/20021016.asp
BTW, for such problem, if it is specific to a certain machine or
environment, is could be caused by some particular things that may be hard
to troubleshoot through newsgroup support. Anyway, we'll try to help you
track down and isolate this issue.
If you have any other finding or any questions on this, please feel free to
post here.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
