An unhandled exception of type 'System.StackOverflowException' occurred in mscorlib.dll" at application startup

One of our applications (which worked fine yesterday!!)  now generates the error "An unhandled exception of type 'System.StackOverflowException' occurred in mscorlib.dll" when run from the Visual Studio

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.StackOverflowException: Exception of type System.StackOverflowException was thrown.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Stack Trace:


[StackOverflowException: Exception of type System.StackOverflowException was thrown.]


[TargetInvocationException: Exception has been thrown by the target of an invocation.]
   System.RuntimeType.CreateInstanceImpl(Boolean publicOnly) +0
   System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
   System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +655
   System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +200
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance() +160
   System.Web.HttpApplicationFactory.FireApplicationOnStart(HttpContext context) +20
   System.Web.HttpApplicationFactory.Init(HttpContext context) +497
   System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +170
   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +414

 
Any ideas why?!  No code has been changed, and it happens if we port it to other servers  :-P

I would be happy to post code, but it seems to happen before even the debuggers can trap it (ie: even using F11 from VS doesn't identify a start line before the code crashes)Start Free Trial