The former employee implemented his own VB.Net context class, which inherits DictionaryBase and implements ILogicalThreadAffinitive. The class object supports values such as user ID, language, location, etc. Throughout a user session in an ASP.NET web application with the .NET 4 platform.
<Serializable()> _ Public NotInheritable Class Context Inherits DictionaryBase Implements ILogicalThreadAffinative ... Class Methods ... End Class
The object class works fine, storing values as expected when navigating from page to page, even when loading a pop-up page. My problem occurs anytime when I have a PostBack action. When this happens, the object becomes null and causes null reference errors.
The strange part is that it works for everyone but me. It is installed in our client system, works in our test environment and works for another developer in the project, but something prevents it from working in my development environment, where the application with the local IIS 7.0 web server is hosted. Another developer, and I cross-checked all the local IIS settings, VS2010 settings and the Internet settings that we would change, but everything seems identical between the two machines (both Win7 x64 and creating the application in x86 mode). Needless to say, this problem has become very erratic for development and troubleshooting.
Are there any suggestions as to what else can be verified that could lead to this behavior?
EDIT : After some more advanced digging, PostBack appears, causing a request for a second thread. This second thread, despite what the documentation apparently says, does not transfer the values to the CallContext. In the work environment of my colleague, this request is processed in the same topic. This is apparently the main symptom of the problem, but we still cannot determine the source. Also, please note: my machine has an SSD, but another developer does not. I do not know if this affects the threads, but I do not think that this will lead to these results.