.NET Framework Initialization Error - Trap

  • Thread starter Thread starter Fox/Net West
  • Start date Start date
F

Fox/Net West

Currently using .NET v1.1.4322 and v1.0.3705.

Starting a C# console application for the office - I wanted to <gracefully>
via structured error handling trap the condition where the .NET framework
(neither of the above) is not installed on the server/workstation - instead
of the default messagebox with the ok button that shows up - is there a way
for me to provide better messaging to the operator/user?

Tia,

John C. Gunvaldson
San Diego, CA
 
You're in a catch-22 situation. In order for any of your C# code to be
executed (including any structured error handling code), the framework
must be loaded, but if the framework is not present, your structured
error handling code will not even run!!

I'm not sure what you can do. You might try creating an application
launcher using C++ or VB6 and have that check for the framework and if
not present, put up a graceful error message. And if it is, start the
..net app.
 
You're in a catch-22 situation. In order for any of your C# code to be
executed (including any structured error handling code), the framework
must be loaded, but if the framework is not present, your structured
error handling code will not even run!!
Click to expand...

Pretty much what I have seen googling the world. One would have thought that
there would be some Windows OS call that that provided the basis for the
default MessageBox that is displayed, that would have an interface that
could be extended (for a more client specific basis) - but I have not ran
across it yet, if available?

Thanks Chris,

John C. Gunvaldson
San Diego, CA
 
Back
Top