At what point in the development of a project will you have to move from sending a .exe file to another user vs. having to deploy and install the program on that users pc. I am assuming that the other user does not have vb/vb.net installed.
Thanks
Printable View
At what point in the development of a project will you have to move from sending a .exe file to another user vs. having to deploy and install the program on that users pc. I am assuming that the other user does not have vb/vb.net installed.
Thanks
the lame thing about vs.net is.
you have to install dotnetfx.exe (.net frameworks distribution package, 23mb) to be able to run vs.net coded progs.
the funny thing is, even if you have vs.net installed. You compile the project to an .exe.
you still wont able to run it on the same box where you have installed vs.net ? not until you installed dotnetfx.exe ?
Well i am not 100% sure about the last thing, but my .exe's didnt work till I install dotnetfx.exe (all my computers have vs.net installed). Its so weird ?
And dotnetfx.exe is still beta.
So you cant just send the .exe ?
nfz
As long as you have the .NET Framework (whether by installing VS.NET or the redistributable) installed on the PC, the exe will run by just copying it over providing the following:
HOWEVER...if you have external dependencies (3rd party tools) that you are using in your application, then you will need to create an installation package so that those dlls get registered.
You shoudn't have to install the dotnetfx.exe if you have vs.net installed on the pc in order to run your exe though.
Also, the .net framework is by default excluded and you can include it in your package if you are creating a MSI setup package.
HTH,
Greg