In Project Properties under Publishing in Options there is a tab called "File Associations". I have entered there .mpg|MyDesc|MyDescID|myIco.ico. I have hoped that the mpg ext will be automatically associated after I start program. However it did not happen. Even when I choose open with and set the app as default it does not have the icon I have chosen.
How to use it?
I believe I have to create a published version, but I would rather not do it(since I change the app a lot). Is there any way to create the associations without creating an installer?
I believe this has to do with ClickOnce deployment, and is related to file associations when a user decides to install the ClickOnce bundle for your app.
When you say "start" the program - are you referring to F5 or Ctrl+F5? If you "Publish" your ClickOnce bundle and then install from there, I believe your file associations should work.
Related
I have been tasked to change the Icons associated with a WPF VS2017 application that I did not create. I am trying to change the desktop short-cut icon that is automatically loaded on installation of the app's .msi.
This solution uses a Visual Studio Installer Project to generate the deployment .msi.
I have tried to change the file reference in the deployment project, but it seems to hang on to the original icon.
I have even gone to the extent of renaming the new .ico file with the original .ico filename and putting it into the directory where the original was located, but the .msi continues to load the old icon to the desktop on the application's installation.
Is there user documentation (not tutorials) on the Visual Studio Installer add-on?
More directly, how is the desktop short-cut icon specified in the deployment project?
Extensive web searching and experimentation have not presented an answer.
The installer project has a "file system" view.
Click round on your files under setup and it should appear in your code editing area.
Under File system on target machine will be folders.
These might have been configured to explicitly add a specific icon for the shortcut.
Click users desktop in the left panel.
You will have a shortcut in the right.
Select this and take a look at properties.
There's an Icon property which is probably set. Click the icon, browse and choose the one you want. This should be in the list of setup files.
If not, check your main entry point project has an icon set.
Choose it's properties > Application
In there under Icon and Manifest set the ico file.
Then try again.
I publish my application from project properties of visual studio and i set the update-path to one of my local drivers E:\WebSiteupdate. The update must run before application starts but i do not really know what should i put on E:\WebSiteupdate to update the application.
here what i used to do for update:
another publish from new application
copy all of new publish folder in E:\WebSiteupdate
but nothing happened and still show old program
what kind of files should i put on update path for update application?
Clickonce's auto updates are meant to update installed applications. That has nothing to do with the project run from VS. When you set Update location, each time the app launches it will check for a newer build/publish in that location. If there is a different build, it will automatically update your installed app. To answer your question what kind of files...? Its is the same contents that you get while you publish your app.
To try this:
Set your Upload location(Project properties --> Updates...) to a path accessible from your pc.
Publish your app to a different location lets say D:\Publish\
Install the app in your pc. There should be D:\Publish\setup.exe. Double-clicking that will install. This will put a shortcut menu in the start menu.
Make any minor change in the UI of your project (in VS).
After clearing the contents in D:\Publish do another publish.
Clear the contents from the Update location and copy over the contents from D:\Publish.
Now (don't do another install) close (if already open) and open the app again (shortcut should be present in Start menu)
The app should update automatically before opening. This is how we are expected to give app updates to the clients. Further, if you like to automate this I found the below link by deadlydog very helpful: http://blog.danskingdom.com/continuously-deploy-your-clickonce-application-from-your-build-server/
I have an application I want to build and deploy via ClickOnce. But we want this to be a process that can be run outside of VS through scripts, for either test, business UAT or production environment.
Each separate environment requires a different .config file to be used and a different web server to be deployed on and for update location.
The application also has prerequisites of .NET runtime 3.5 and Crystal reports.
I have looked into using MAGE to create application and deployment manifests, and if I do a code BUILD, then use MAGE afterwards as per each environment, as well as having the script copy over the correct .config file, this creates what I think are the correct manifests for each environment at the time of running the script.
But what I'm struggling to do is include the prerequisites. If done through VS, you can specify a setup.exe package which gets built with the pre-reqs and deployed alongside the application and when you click on the download link, it installs the pre-reqs from setup.exe and then the application.
But how can I do this manually outside VS? I can build the setup.exe through VS with the right URl location but then how do I link the setup.exe to the application as a pre-req using MAGE to generate the manifests?
The problems we have are 1) The users do not have admin rights to download and install packages, only to install things via clickonce so the pre-reqs have to be installed under the click once security umbrella.
Thanks
ClickOnce and prereqs cause lots of confusion. The setup.exe that Visual Studio generates has nothing to do with ClickOnce. The only minor link between the two is that the setup.exe will launch the ClickOnce application once it finishes. That's it. So thinking users will be able to install your prereqs "under the clickonce security umbrella" is a mistake. If they are not an admin and a prereq install requires admin privileges, they won't be able to install it.
My advice would be to generate your setup.exe one time. You shouldn't need to keep doing it unless your prereqs keep changing. Use Visual Studio, generate the setup one time, then use Mage for the rest.
Edit
In general you make the setup.exe available and depend on the user to know if they need to run it or not. If they already have the prereqs and run the setup.exe, nothing bad happens. It sees that everything is installed then launches the app.
Usually you're going to direct users to run the setup.exe. The next time they want to launch the app they should use the start menu shortcut (assuming you didn't go with "Online Only"). I've found this to be the least confusing set of instructions for users.
Remember how Visual Studio does extra, non-ClickOnce stuff when you publish (like the setup.exe)? It also creates a simple html page that has links to both the ClickOnce manifest and the setup.exe and an explanation. It also has some javascript that checks the UserAgent string to determine if they have the .NET Framework installed. Again, this isn't ClickOnce. It's just something nice Visual Studio does for you. If you like it, use it. I kind of like skipping it and going with the run setup.exe to install then launch from the start menu.
codeConcussion is right, you can't ever actually have the prerequisites instill directly from ClickOnce. You should just generate it once and then you have it ready for your external ClickOnce tool.
There is an option other than Mage. You could use my companies tool, ClickOnceMore, as your ClickOnce build software. It's been designed for people who want to use ClickOnce but don't want to build with Visual Studio.
It can hook into the setup.exe generated from Visual Studio (details here) so should satisfy all your needs.
Why do you want to build setup manually if everything can be done via clickonce ?
You can select "Download pre-requisites from same location" option from prerequisites form if you want to include .netfx or crystalreports, download bootstrap packages for .netfx3.5 & crystalreports and add to folder (for windows 7) "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages" . The deployment project will automatically include netfx & other packages along with setup.exe.
hope this helps.
I have created a winforms project, and created an installer for it.
When installed i can run the exe from the install location, however if i create an entry in my install package to add the project output (the exe) to the users programmes menu or desktop then it fails
Does anyone know why this might be?
Thanks for your time
If this is a VS Deployment project, you don't add the project output directly, you create a shortcut from within the File System Viewer pointing to the primary output (which you will probably find in the 'Application Folder' in the shortcut dialog). You can then assign the shortcut a name and icon etc.
You need both the EXE and the MSI.
HI,
I have a windows application in C#. I created and added a set up project to this solution. Then, built the solution. I refered to this link http://www.codeproject.com/KB/install/SetupAndDeployment.aspx. I even added the shortcut of "Primary output of my application" to "User's Desktop" folder. But I am not able to find the installer file in Desktop, so that I can "double click" this installer file and install my Windows application.
KINDLY HELP ME WITH THE PROCEDURE THAT NEEDS TO BE FOLLOWED AFTER CREATING A SET UP PROJECT, ADDING IT TO A SOLUTION AND BUILDING THE SOLUTION. WHERE AND HOW TO FIND THE INSTALLER FILE. IS THERE ANYTHING THAT I AM MISSING.
The installer file should be located in the bin folder of your installer project. Right click on the project in the project tree, and select "Open folder in windows explorer", and you'll find the bin directory.
The link on the desktop will only be present once the installer file has been run.
Whether this is 100% applicaple I don't know but it's something I'd think is worth a try which is if u know what the installer file is called why not do a search for that file to see if it's been stored somewhere else?
I apologise If I am stating the obvious to you, I have probably misunderstood your question if i am.
When you make a setup project the built setup files are in the Debug or Release folder of the setup project depending on your build settings
-setup.msi
-setup.exe for example
clicking setup.exe will run the install the application
You copy them to the user's desktop and click to install your application?