The object is currently in use elsewhere

[KevinBradly]

Building and running a VB or C# graphics application within VisStudio is fine.
Running the .exe outside VisStudio on the same machine is fine.
But trying to run the .exe on another machine produces this error.

Anyone have any clues?

[Nick Malik [Microsoft]]

any idea what object it is talking about? Do you have try-catch blocks that
identify the location in the code, or which log themselves, so that you can
figure out where the error is occuring?

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"KevinBradly" <Ke*********@discussions.microsoft.com> wrote in message
news:9A**********************************@microsof t.com...

Building and running a VB or C# graphics application within VisStudio is
fine.
Running the .exe outside VisStudio on the same machine is fine.
But trying to run the .exe on another machine produces this error.

Anyone have any clues?

[KevinBradly]

Not really and I don't have any try-catch blocks.
I have since discovered the following though:

When we install our software on a development machine, we add some DLL's
into the GAC. If I add the same DLL's into the GAC on the machine I am
trying to run the app. on (it happens to be running XP-Pro and has .NET
installed), all is now OK.
So, what do I do on machines that don't have .NET or the FrameworkSDK
installed?

Kevin

"Nick Malik [Microsoft]" wrote:

any idea what object it is talking about? Do you have try-catch blocks that
identify the location in the code, or which log themselves, so that you can
figure out where the error is occuring?

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"KevinBradly" <Ke*********@discussions.microsoft.com> wrote in message
news:9A**********************************@microsof t.com...

Building and running a VB or C# graphics application within VisStudio is
fine.
Running the .exe outside VisStudio on the same machine is fine.
But trying to run the .exe on another machine produces this error.

Anyone have any clues?

[Nick Malik [Microsoft]]

If your app requires a dll, it has to be on the target machine. You can
make a setup kit for your app that will install the dll for you. It often
doesn't need to be in the GAC. (depends on the app... most apps don't need
the dlls to be in the GAC).

You will ALWAYS require the .Net framework. You shouldn't need the SDK.

Oh, and use try - catch blocks.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"KevinBradly" <Ke*********@discussions.microsoft.com> wrote in message
news:CE**********************************@microsof t.com...

Not really and I don't have any try-catch blocks.
I have since discovered the following though:

When we install our software on a development machine, we add some DLL's
into the GAC. If I add the same DLL's into the GAC on the machine I am
trying to run the app. on (it happens to be running XP-Pro and has .NET
installed), all is now OK.
So, what do I do on machines that don't have .NET or the FrameworkSDK
installed?

Kevin

"Nick Malik [Microsoft]" wrote:

any idea what object it is talking about? Do you have try-catch blocks
that
identify the location in the code, or which log themselves, so that you
can
figure out where the error is occuring?

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"KevinBradly" <Ke*********@discussions.microsoft.com> wrote in message
news:9A**********************************@microsof t.com...

> Building and running a VB or C# graphics application within VisStudio
> is
> fine.
> Running the .exe outside VisStudio on the same machine is fine.
> But trying to run the .exe on another machine produces this error.
>
> Anyone have any clues?

[KevinBradly]

Thanks for your help Nick.
I'll look into making a setup kit that can install the DLL's, or
alternatively look into changing our app so that the DLL's don't have to be
GAC'ed. Any hints or links to reading material on that?

Kevin

"Nick Malik [Microsoft]" wrote:

If your app requires a dll, it has to be on the target machine. You can
make a setup kit for your app that will install the dll for you. It often
doesn't need to be in the GAC. (depends on the app... most apps don't need
the dlls to be in the GAC).

You will ALWAYS require the .Net framework. You shouldn't need the SDK.

Oh, and use try - catch blocks.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"KevinBradly" <Ke*********@discussions.microsoft.com> wrote in message
news:CE**********************************@microsof t.com...

Not really and I don't have any try-catch blocks.
I have since discovered the following though:

When we install our software on a development machine, we add some DLL's
into the GAC. If I add the same DLL's into the GAC on the machine I am
trying to run the app. on (it happens to be running XP-Pro and has .NET
installed), all is now OK.
So, what do I do on machines that don't have .NET or the FrameworkSDK
installed?

Kevin

"Nick Malik [Microsoft]" wrote:

any idea what object it is talking about? Do you have try-catch blocks
that
identify the location in the code, or which log themselves, so that you
can
figure out where the error is occuring?

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"KevinBradly" <Ke*********@discussions.microsoft.com> wrote in message
news:9A**********************************@microsof t.com...
> Building and running a VB or C# graphics application within VisStudio
> is
> fine.
> Running the .exe outside VisStudio on the same machine is fine.
> But trying to run the .exe on another machine produces this error.
>
> Anyone have any clues?