All of a sudden: Programm cannot be launched via F5

[Helmut Giese]

Hello out there,
all of a sudden I get an error message when trying to debug (F5) a
program:
Error while trying to run project: Unable to start program <path>
Das aufgerufene Objekt wurde von den Clients getrennt.
(The called object was separated from the clients.)

If I change to the debug directory I can start the program manually
and it runs - as it does as well when I start it from within VS via
'Ctrl F5' (run without debugging) - but right now I _need_ debugging.

In case it matters: The program relies on a DLL which I build in
another project and then copy into this app's directory. This has
worked for weeks, but today I changed the DLL as well as this program.
The DLL itself works - I have a separate C++ console mode driver
program for doing basic tests before I integrate it into my GUI.

This threatens to become a bad show stopper.
Any idea or tip will be greatly appreciated.
Best regards
Helmut Giese

 

[Gregory A. Beamer]

In case it matters: The program relies on a DLL which I build in
another project and then copy into this app's directory.

Break the reference for the DLL in question and reset it. That should get
rid of hte gremlins, or at least does in a great number of cases.

Peace and Grace,

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************

 

[Helmut Giese]

Break the reference for the DLL in question and reset it. That should get
rid of hte gremlins, or at least does in a great number of cases.

Hi Gregory,
so the gremlins were the cause?
What I did was to add the DLL's lib file to the project (previously it
had been working without) and now it works again.

Seeing that once it worked w/o the lib file and once it was needed
leads to the more general question: What is the proper C# way to add a
DLL created in a different project? Oh, and the DLL is built with VC++
in case it matters.

Any info or link will be greatly appreciated.
Best regards
Helmut Giese

 

[Gregory A. Beamer]

Seeing that once it worked w/o the lib file and once it was needed
leads to the more general question: What is the proper C# way to add a
DLL created in a different project? Oh, and the DLL is built with VC++
in case it matters.

In theory, if all are .NET, you should be able to put all projects in the
same solution. This is fine up until you have a release, of course.

Once you have a release, you really need version control. You then
explicitly set to a particular version of the library for a release. If you
desire, you can create lib folders with different release versions. Once
you have a release on an assembly, reset the project to the new lib folder
and recompile.

For some, there is a preference to branch the entire code base at this
time, rather than simply branch the referenced assembly. I am not as fond
of this if there is not actually a release as you can end up with way too
many branches this way and end up with a maintenance nightmare for the
developers.

you can keep up without version control if you have the libs folder with
different versions of asemblies in different directories and repoint, but
you will eventually make a mistake this way.

If the C++ component is COM, you have more issues to deal with, but from
yoiur answer, I don't think COM is an issue.

Hope this makes sense.

peace and grace,



--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************