Compiling .dll's into a stand-alone .exe

[freeman.matt]

So I have this application which uses the MSComm control to interface
with a GPS receiver. I've developed it (using Vis Studio .NET 2003) to
the point where I'm mostly happy with it and I want to transfer it to
my laptop to do some real world trials.

When I transfer the \bin (containing GPS.exe, GPS.pdb, and
Interop.MSCommLib.dll) to my lapotp and run the .exe, the program
crashes, returning the message that there is an unhandled error in the
code. I believe that it has something to do with the MSComm, since the
..exe works fine on any comuputer with Vis Studio, but returns a similar
error on all machines lacking the software.

Is there something that I need to do to direct the computer to the
..dll, or better yet, include everything in a single .exe?

Thanks in advance.

-Matt

[freeman.matt]

If it helps, the specific error is as follows:
__________________________________________________ ______
|
x |
| Application has generated an exception that could not be handled.
|
|
|
| Process id=0xe64 (3684), Thread id=0xb30 (2864).
|
|
|
| Click OK to terminate the application.
|
| Click CANCEL to debug the application.
|
|_________________________________________________ _______|

[GhostInAK]

Hello fr**********@gmail.com,

The best solution would be to upgrade your dev environment to 2005 (Express
version is free) and use the 2.0 framework's SerialPort class.

-Boo

So I have this application which uses the MSComm control to interface
with a GPS receiver. I've developed it (using Vis Studio .NET 2003)
to the point where I'm mostly happy with it and I want to transfer it
to my laptop to do some real world trials.

When I transfer the \bin (containing GPS.exe, GPS.pdb, and
Interop.MSCommLib.dll) to my lapotp and run the .exe, the program
crashes, returning the message that there is an unhandled error in the
code. I believe that it has something to do with the MSComm, since
the .exe works fine on any comuputer with Vis Studio, but returns a
similar error on all machines lacking the software.

Is there something that I need to do to direct the computer to the
.dll, or better yet, include everything in a single .exe?

Thanks in advance.

-Matt

[Chris Dunaway]

fr**********@gmail.com wrote:

code. I believe that it has something to do with the MSComm, since the
.exe works fine on any comuputer with Vis Studio, but returns a similar
error on all machines lacking the software.

Have you installed the .Net framework on the target machine? Is the
MSComm control on the target machine and registered properly?

Try adding an application exception handler so you can catch the exact
exception that is occurring.

[freeman.matt]

Ghost: Thats good to know, my new copy of 2005 should arrive today and
if that fixes everything then so much the better.

Chris: I have not installed the framework yet, but I'll do that later
today and see what happens.

Thanks for the advice.

-matt