Real Newbie Question

  • Thread starter Thread starter Dave
  • Start date Start date
D

Dave

I created a C# Windows Application in VS 2003.

I test it with F5 and it runs fine.

When I look in the VS projects folder, I see a .exe file with my project
name.

Now what do I need to do in order to move this exe to another workstation
and have it execute there? (This other workstation has the NET Framework
installed in it).

Thanks
Dave
 
Dave,

Unless you have added 3rd party components you can just move the exe since
the .Net Framework already exists on the other workstation. Make sure to
compile your project to "Release" before moving.

HTH,

Matt
 
If you're application doesn't use anything like crystal that needs to be
installed on the client machine you can technically copy everything from
either the Debug folder or Release folder to a folder on the other machine.
However, MS emphasizes using the package and deployment to create a setup
project. If this is just for testing then build it in release mode and copy
everything from that folder. If it is just for testing it doesn't matter
which you use.
 
That didn't make sense what I said at the end....lol. Anyway, if it is just
for testing you can use the debug folder files, else I would use the release
folder files.

HTH

--
Lateralus [MCAD]


Lateralus said:
If you're application doesn't use anything like crystal that needs to be
installed on the client machine you can technically copy everything from
either the Debug folder or Release folder to a folder on the other
machine. However, MS emphasizes using the package and deployment to create
a setup project. If this is just for testing then build it in release mode
and copy everything from that folder. If it is just for testing it doesn't
matter which you use.

--
Lateralus [MCAD]


Dave said:
I created a C# Windows Application in VS 2003.

I test it with F5 and it runs fine.

When I look in the VS projects folder, I see a .exe file with my project
name.

Now what do I need to do in order to move this exe to another workstation
and have it execute there? (This other workstation has the NET Framework
installed in it).

Thanks
Dave
 
Thanks guys

I'm still having a bit of a problem though.

I went into the configuration manager and set the build to "release,"
rebuilt the application, copied the exe file from the rebuild folder (the
only file present in this folder) and pasted it on my desktop.

When I tried to execute the file from the desktop by double clicking on it,
I got an error: system.security.securityException.

I did this all on my own workstation.

Any ideas why I get this error?



Lateralus said:
If you're application doesn't use anything like crystal that needs to be
installed on the client machine you can technically copy everything from
either the Debug folder or Release folder to a folder on the other machine.
However, MS emphasizes using the package and deployment to create a setup
project. If this is just for testing then build it in release mode and copy
everything from that folder. If it is just for testing it doesn't matter
which you use.

--
Lateralus [MCAD]


Dave said:
I created a C# Windows Application in VS 2003.

I test it with F5 and it runs fine.

When I look in the VS projects folder, I see a .exe file with my project
name.

Now what do I need to do in order to move this exe to another workstation
and have it execute there? (This other workstation has the NET Framework
installed in it).

Thanks
Dave
 
Vinny:

Thanks but I don't have a dll file present.

Under bin\debug I have x.exe and x.pdb

Under bin\release I have only x.exe.

When I try copying the x.exe to my desktop and double-clicking on it, I get
the error regardless of whether I copy from debug or release. Even if I
copy the x.pdb to the desktop with the x.exe, I still get the error.

Can you think of anything I might be doing wrong?

The app functions fine within the VS environment.

What might cause it to throw a security exception?
 
Hi. If you execute it directly from the Release folder, does it work? I mean
by clicking on it, not by running it with VS.
 
Yes.

With VS closed, I double click on the exe file in the release folder from
Windows Explorer and it runs.

But if I copy this same file to the desktop and click on it, I get the
security error.

There are no other files in the release folder but the exe. So I wonder
what it is missing when I copy it to the desktop.

What do I need to do if I want my exe to run from anywhere other than the
release folder?
 
Do you have any roaming profiles or redirecting going on? I've tracked down
a different bizarre behavior I was seeing in VS to the fact that my
Application Settings are redirected to a server share and therefore VS sees
them as coming from the "local intranet" zone instead of locally.

Try just copying the files to another location on your C: drive (not
MyDocuments) and testing it there.
 
Back
Top