Spiritual programming?

31 May 2006 5:25 PM

CR

I just received the error message "An exception has been thrown by the
target of an invocation." So, I did as any good Christian would do, I closed
Visual Studio 2005 Standard, said a little prayer, reopened Visual Studio,
and the error was gone! Invocation = Prayer, so the target of a prayer
threw an exception in my application!
Honestly, what does that error message mean? It showed up when switching
from viewing code to viewing the designer on a user control. There was no
location listed for the error, it was the only error, and evidentially,
there was nothing wrong with my code, because it works fine again.

31 May 2006 5:55 PM

Chris

CR wrote:

> I just received the error message "An exception has been thrown by the
> target of an invocation." So, I did as any good Christian would do, I closed
> Visual Studio 2005 Standard, said a little prayer, reopened Visual Studio,
> and the error was gone! Invocation = Prayer, so the target of a prayer
> threw an exception in my application!
> Honestly, what does that error message mean? It showed up when switching
> from viewing code to viewing the designer on a user control. There was no
> location listed for the error, it was the only error, and evidentially,
> there was nothing wrong with my code, because it works fine again.
>
>

Are you using any com objects in your program?

Chris

31 May 2006 6:52 PM

CR

No, everything is .NET.

Show quoteHide quote

"Chris" <no@spam.com> wrote in message
news:OS1EetNhGHA.4284@TK2MSFTNGP05.phx.gbl...
> CR wrote:
>> I just received the error message "An exception has been thrown by the
>> target of an invocation." So, I did as any good Christian would do, I
>> closed Visual Studio 2005 Standard, said a little prayer, reopened Visual
>> Studio, and the error was gone! Invocation = Prayer, so the target of a
>> prayer threw an exception in my application!
>> Honestly, what does that error message mean? It showed up when switching
>> from viewing code to viewing the designer on a user control. There was no
>> location listed for the error, it was the only error, and evidentially,
>> there was nothing wrong with my code, because it works fine again.
>
> Are you using any com objects in your program?
>
> Chris

1 Jun 2006 2:24 AM

ewok66

We have that happen a lot: a lot of funny errors that make no sense that are
easily cleared by closing VS and reopening.

A lot of times, the errors are due to controls we purchased.

--
--ewok
MCSA+M,MCSE, MCSD, MCDBA,MCITP

Show quoteHide quote

"CR" wrote:

> No, everything is .NET.
>
> "Chris" <no@spam.com> wrote in message
> news:OS1EetNhGHA.4284@TK2MSFTNGP05.phx.gbl...
> > CR wrote:
> >> I just received the error message "An exception has been thrown by the
> >> target of an invocation." So, I did as any good Christian would do, I
> >> closed Visual Studio 2005 Standard, said a little prayer, reopened Visual
> >> Studio, and the error was gone! Invocation = Prayer, so the target of a
> >> prayer threw an exception in my application!
> >> Honestly, what does that error message mean? It showed up when switching
> >> from viewing code to viewing the designer on a user control. There was no
> >> location listed for the error, it was the only error, and evidentially,
> >> there was nothing wrong with my code, because it works fine again.
> >
> > Are you using any com objects in your program?
> >
> > Chris
>
>
>

2 Jun 2006 3:54 AM

Ray Cassick (Home)

I have received errors like that while doing some remoting stuff that had
security issues. Think you could also get it for other reasons but that was
mine.

Show quoteHide quote

"CR" <c@home.com> wrote in message
news:e1z4ucNhGHA.1204@TK2MSFTNGP02.phx.gbl...
>I just received the error message "An exception has been thrown by the
>target of an invocation." So, I did as any good Christian would do, I
>closed Visual Studio 2005 Standard, said a little prayer, reopened Visual
>Studio, and the error was gone! Invocation = Prayer, so the target of a
>prayer threw an exception in my application!
> Honestly, what does that error message mean? It showed up when switching
> from viewing code to viewing the designer on a user control. There was no
> location listed for the error, it was the only error, and evidentially,
> there was nothing wrong with my code, because it works fine again.
>