G Guest Dec 30, 2005 #21 No problem As Jim pointed out already, the blogs are really worth a look!! Thanks Jim!!!!
J Jim Cheshire Dec 30, 2005 #22 Rahul said: No problem As Jim pointed out already, the blogs are really worth a look!! Thanks Jim!!!! Click to expand... Sure. -- Jim Cheshire ================================ Blog: http://blogs.msdn.com/jamesche Latest entry: Digging into Objects Describes the details of digging into memory usage with the debugger.
Rahul said: No problem As Jim pointed out already, the blogs are really worth a look!! Thanks Jim!!!! Click to expand... Sure. -- Jim Cheshire ================================ Blog: http://blogs.msdn.com/jamesche Latest entry: Digging into Objects Describes the details of digging into memory usage with the debugger.
S SharpSmith Jan 1, 2006 #23 Well, that was the issue indeed. After removing the bulk of code which was problematic the application ceased to crash and went on the stable side. I cant thank you guys enough for the help! BTW Jim, great blog
Well, that was the issue indeed. After removing the bulk of code which was problematic the application ceased to crash and went on the stable side. I cant thank you guys enough for the help! BTW Jim, great blog
J Jim Cheshire Jan 1, 2006 #24 SharpSmith said: Well, that was the issue indeed. After removing the bulk of code which was problematic the application ceased to crash and went on the stable side. I cant thank you guys enough for the help! BTW Jim, great blog Click to expand... Thanks for the update. Glad to hear it, and thanks for the blog comment. -- Jim Cheshire ================================ Blog: http://blogs.msdn.com/jamesche Latest entry: Getting the PID and TID of a COM Call Describes how to get the PID of the dllhost process a COM call is executing in and how to locate the thread as well.
SharpSmith said: Well, that was the issue indeed. After removing the bulk of code which was problematic the application ceased to crash and went on the stable side. I cant thank you guys enough for the help! BTW Jim, great blog Click to expand... Thanks for the update. Glad to hear it, and thanks for the blog comment. -- Jim Cheshire ================================ Blog: http://blogs.msdn.com/jamesche Latest entry: Getting the PID and TID of a COM Call Describes how to get the PID of the dllhost process a COM call is executing in and how to locate the thread as well.
P Peter Gnorre Oct 10, 2006 #25 Hi, I know I'm a bit late, but I had the same problem. The solution for me was quite simle: First stop IIS. Next delete all your temporary ASP.NET files in C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files Now restart IIS again. For me, the problem was fixed. Best Regards, Gnorre
Hi, I know I'm a bit late, but I had the same problem. The solution for me was quite simle: First stop IIS. Next delete all your temporary ASP.NET files in C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files Now restart IIS again. For me, the problem was fixed. Best Regards, Gnorre