It's not clear what you mean. In the context of C# and .NET, there's no
such thing. There is a NullReferenceException, which you can catch just
like any other exception. But because of garbage collection and the
inability to assign arbitrary values to reference variables in C# (at
least without "unsafe" code...maybe you can do it in "unsafe" code), you
wouldn't get other kinds of invalid references.
It's not clear what you mean. In the context of C# and .NET, there's no
such thing. There is a NullReferenceException, which you can catch just
like any other exception. But because of garbage collection and the
inability to assign arbitrary values to reference variables in C# (at
least without "unsafe" code...maybe you can do it in "unsafe" code), you
wouldn't get other kinds of invalid references.
Please have a look at this reference: http://support.microsoft.com/kb/305652
I want to protect against that happening or create a way out by means of a
catch and a message.
I still don't understand. That reference discusses a particular fault
that happens with a specific piece of software when a computer is
rebooted. It's not something that would be related to your C# code at all.
Are you getting this same fault from within your own C# program? If so,
how do you do that, given that the fault you're referring to appears to be
specific to boot time after installating a particular program.
If not, I think you need to be more specific about what scenario it is you
have and how you want to handle it.
Pete
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
