Publishing a console application?
-
I'm trying to figure out the correct way of compiling the final version of a console application for other people to use. I've done the "Build project" way, but then the user has to copy over all of the DLL files in my "bin" directory in order to get it to work. This way isn't very professional. I've also done the "publish project" option, however when I publish it, I get 2 "application manifest" files (1 names "MyProject_1_0_0_0" and another simply names "MyProject"), a directory containing the DLL's (usually called "MyProject_1_0_0_0"), and a setup.exe file. I'm unsure of which ones to send over, so I just send them all over. This way isn't very professional either. So, what's the correct way to compile my final version of a console application before handing it off to a user? Thanks. -Goalie35
-
I'm trying to figure out the correct way of compiling the final version of a console application for other people to use. I've done the "Build project" way, but then the user has to copy over all of the DLL files in my "bin" directory in order to get it to work. This way isn't very professional. I've also done the "publish project" option, however when I publish it, I get 2 "application manifest" files (1 names "MyProject_1_0_0_0" and another simply names "MyProject"), a directory containing the DLL's (usually called "MyProject_1_0_0_0"), and a setup.exe file. I'm unsure of which ones to send over, so I just send them all over. This way isn't very professional either. So, what's the correct way to compile my final version of a console application before handing it off to a user? Thanks. -Goalie35
Goalie35 wrote:
So, what's the correct way to compile my final version of a console application before handing it off to a user?
You dont have to publish anything (I think thats to do with click once). The content in the bin\Release directory should be sufficient :)
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008) -
I'm trying to figure out the correct way of compiling the final version of a console application for other people to use. I've done the "Build project" way, but then the user has to copy over all of the DLL files in my "bin" directory in order to get it to work. This way isn't very professional. I've also done the "publish project" option, however when I publish it, I get 2 "application manifest" files (1 names "MyProject_1_0_0_0" and another simply names "MyProject"), a directory containing the DLL's (usually called "MyProject_1_0_0_0"), and a setup.exe file. I'm unsure of which ones to send over, so I just send them all over. This way isn't very professional either. So, what's the correct way to compile my final version of a console application before handing it off to a user? Thanks. -Goalie35
