Dave Burke : Freelance .NET Web Developer specializing in Online Communities

Interesting CSContext null error while debugging

Probably like most of you reading this post, I've got a love-hate thing going with VS2005.  It's been ticking me off a lot lately, hanging a lot, sucking in more and more memory the longer I have it open, and I'm seeing occasional SQL2005 connection timeouts when too many VS2005 resources are in use.  And this is VS2005 on a clean machine with VS2005 SP1.  So I don't know if this is something I did on a custom CS site, perhaps because a user previously used for testing might have been deleted, or is a pure VS2005 thing.  The problem was that I was trying to debug a CS2007 solution today and couldn't get past a Null Reference Exception on the CSContext.Current.User. 

 



Maybe someone can tell me what I did, but I found a quick work-around of changing the start action to "Wait for an external application request."  Firing up Firefox and loading the Visual Studio port-assigned localhost url (ex: http://localhost:5159) acknowledged the breaks I had set and allowed me to play through.


Comments (2) | Post RSS RSS comment feed

Posted on 6/12/2007 8:45:48 PM by Dave Burke
Categories: .NET | Community Server
Tags: no tags for this post

Related posts

Comments (2) -

6/13/2007 9:26:10 PM Permalink

Hey Dave, are you stopping the VSDS after builds?  You don't always need to do this, but it depends what you are working on and what crashes.  Just right click on the server icon in the server tray and select STOP, then restart the debugger.

Bill Bosacker |

6/13/2007 9:56:26 PM Permalink

Thanks Bill. Yes, I stop it whenever I see the icon in the tray, but thanks for the tip.  I appreciate it!

daveburke |


Powered by BlogEngine.NET 2.0.0.36
Theme by Dave Burke