Calling Windows App from command line prompt?
-
I have a VB.NET windows app that i have built an exe file for. I orignally put the .exe file on the c:\ for ease of testing but the app didn't work. It complained 'PublicKeyToken=null or one of its dependencies. The system cannot find the file specified.' I have solved this by Publishing and installing the application, instead of just copying the exe file and config file across. However the publish wizard gives me the option of were to publish the install to but not where the install puts the exe file. How can i do this?
-
I have a VB.NET windows app that i have built an exe file for. I orignally put the .exe file on the c:\ for ease of testing but the app didn't work. It complained 'PublicKeyToken=null or one of its dependencies. The system cannot find the file specified.' I have solved this by Publishing and installing the application, instead of just copying the exe file and config file across. However the publish wizard gives me the option of were to publish the install to but not where the install puts the exe file. How can i do this?
ClickOnce deployment does NOT give you the option of specifing where to install the application. You have to use a traditional Setup project (MSI-based) to specify the installation directory. Also, what was the EXACT error message you got when you just did the copy of the .EXE and config file?? Did you also make sure you copied over any .DLL files that were in the Debug or Release folder??
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
ClickOnce deployment does NOT give you the option of specifing where to install the application. You have to use a traditional Setup project (MSI-based) to specify the installation directory. Also, what was the EXACT error message you got when you just did the copy of the .EXE and config file?? Did you also make sure you copied over any .DLL files that were in the Debug or Release folder??
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007Did'nt copy ALL the DLL's but only got an error message for one of the DLL's. Anyway, i have now created a MSI install which works better. Thanks
-
Did'nt copy ALL the DLL's but only got an error message for one of the DLL's. Anyway, i have now created a MSI install which works better. Thanks
barney_1972 wrote:
Did'nt copy ALL the DLL's but only got an error message for one of the DLL's.
They end up in the bin\Debug and bin\Release folders for a reason. Without them, you can expect your app to crash at some point.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007