Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have VB project and I tried to use PUBLISH feature.
It seems to create nicely some kind of setup program, but the setup program does not ask where to copy files (it does not seem to copy filesto target machine “PROGRAM FILES”.)
Is this setup program somehow different from usual installers?
NOTE: I want that app files are installed to Hard disk( from USB stick source)
Is the signing recommended or necessary? My App is pretty simple, its just using access DB + printer api, should I still sign?
The “Publish” feature creates a ClickOnce installer. Such applications are installed per-user instead of per-machine, i.e., they are installed somewhere into the user’s profile. This is by design and has the advantage that the user installing the software does not need administrative privileges on the machine.
You can also create a setup project by going to
File/New/Project/Other Project Types/Setup and Deployment/Setup Project. This creates a “conventional” MSI-based installer, offering the “classic” C:\Program Files type of installation.On MSDN, two approaches are compared here.