I have a pretty simple project. No need for registry. Can I just copy the release folder to another machine instead of going through the whole deployment method with setup etc.
Printable View
I have a pretty simple project. No need for registry. Can I just copy the release folder to another machine instead of going through the whole deployment method with setup etc.
Use ClickOnce for a quick "down and dirty" deployment. You can access the publishing wizard through the properties of your project. Look for the Publish tab.
Quote:
Originally Posted by circuits2
Isn't "publishing" for web projects?
No, not only. The publishing wizard will give you several options for deployment, including installation from a disk or network drive. You can even modify the application manifest to change the update and installation paths. Very versatile for it's simplicity.
Where are the program files located?
I also have a txt file in the bin directory of my project, the file is both read and written to. Can I add this?
Is the xcopy method more appropriate for me? And rather than use xcopy, cant i just copy the folder?
Yes. In most cases for a 'simple' project you can just copy the files in the bin directory and it will run, provided the target system has the appropriate framework installed.Quote:
Originally Posted by jeffnyc
HTH
kevin
You can't just copy the files any more. That went away with VB6. The files for your app will be located in the Publish folder that can be found in the project's directory. Also, you can add your text file to the distribution copy. Click around for a while, it's pretty straight forward. The wizard can help with a lot of your questions the first time around.
Yes you can. If your app compiles to a single EXE then you can simply copy that EXE to another machine and run it, assuming that the Framework is already installed. Even if your app depends on DLLs you can simply copy them to the same folder and it will still work.Quote:
Originally Posted by circuits2
Publishing a project creates a ClickOnce installer. The advantages of that include the fact that your app appears in the Add/Remove Programs dialogue, plus ClickOnce can manage updates. It also allows you to automate installation of the Framework, SQL Server Express and some other components too. It is by no means required though.
If you use a VS Setup project to create an MSI installer you can do more, including add registry entries, install assemblies in the GAC, register COM components and more. You lose ClickOnce's main feature of update management though.