I help maintain a WPF application deployed via ClickOnce. When I first installed it, we were using Icon #1 as our app icon (specified by clicking Properties on the Project and setting the "Icon" field); this is the icon that shows up as the Desktop shortcut.
Recently our company's logo changed so I updated the icon to Icon #2 and deployed a new release to the ClickOnce server. On some of the computers running the software, upon receiving the updated release, the icon changed as expected. However, on a few, the old icon is still showing, even though I can see the program has updated to the latest version deployed in ClickOnce.
Why is this? Has anyone else encountered this? And what can I do to fix it? By the way, the program is self-signed; not sure if that makes a difference.
Related
I am ready to publish my WPF APP. I am using Visual Studio 2015 and everything works well when debugging. Since the App will only be used for some research data collection I didn't plan to publish on web. The approach I adopted was publishing wizard to my local machine from the project property on Visual Studio.
After publishing, there were several files in the published folder: a setup file, a file with my app name, a file called autorun, a folder called application files. If I double click set up file, there would be a short installation process and an icon of my app appearing in start menu. However, the app could not be open by clicking that icon. The weird thing was: if I right click set up file, and "run as administrator" the app will lanuch automatically after the short process of installation and worked well as it in Visual Studio. But when I tried to search from start menu, it turned out the App was not installed at all. That means, the App could not be open and running by right clicking the set up file and "run as administrator"! This is not what I want, does anyone has any cue?
I also tried many solutions like this but no one helps.
It sounds like your anti-virus software is blocking the installation process.
I had many users with the same installation problem when they had installed bitdefender on their system.
Give it a try and deactivate your anti-virsu software.
thanks for your help. I finally found the problem. It was because I tried to set a value in register table in order to get the App automatically launch with the system start up. There was neither error nor warning when running on Visual Studio. However, it didn't work after publishing.
So what I did was remove the code of setting value in register table and I also figured out another way to launch it with the system start up.
I have written a simple application in VS 2015 and published the build.
I have applied the icon and every thing works fine. However, I have decided to change the icon to a better looking one. The projects publishes OK and it contains a new icon in the bin\Release folder.
However, when I copy the same exe file onto the desktop, it displays the old icon. It appears OK on my windows laptop...
I have cleared the icon cache file and restarted the machine. Stopped and started the explorer.
Using windows server 2012 VM machine.
Any clues?
Icon is not being displayed in Share menu next to my app name. But its displayed correctly in icon
I have added icons to all the options in visual studio
The assets you are using are right. At first, I didn't see any problem when I used RTM OS version (Version 1511, OS Build 10586.494). However, from your screenshot, it seems you are using Insider Preview Build. So I tested it again on Windows 10 Insider Preview Build 14393 and I can reproduce your issue.
Actually, your app icon is not invisible. It seems that System has cached the app icon used in Share menu when your app is deployed for the first time. After this, even we reset the app icon and redeploy the app, the icon in Share menu still won't change. I guess you've run your app with the default assets before you set your own assets. So in Share menu, it still use the default icon, but in Start panel, it is correct. You can created a new project with your own assets and then run this new project, you icon should be able to display in Share menu correctly.
This issue seems only affect Insider Preview Build. For Insider Preview issues, please feel free to share feedbacks with Microsoft. You can report this issue with Windows Feedback app. Your feedback has made Windows better!
All Logos Related to UWP are stored in Package.appxmanifest. Edit it using an xml editor. See if there is any image that is still a default icon.
I have one Windows Forms application, and I deployed that using ClickOnce. I changed the project icon. After publishing and installing, that icon is appearing on the desktop. That much is OK.
But when I search that application in Add/Remove programs in the control panel, it shows one default icon and not mine. How can I change that icon or is it not possible?
According to the thread in the MSDN forum, Missing Icon in Add/Remove Programs for ClickOnce Application, it seems to be possible.
I'm pretty sure ClickOnce does not give you ability to change the icon. I use Visual Studio Setup Project in my deployment, and if you go to the Properties, the first one is 'AddRemoveProgramsIcon', where you can specify what icon you want to be used there.
Currently I have a solution with Windows and WP7 XNA projects in it.
Whenever I try to debug just the Windows project it thinks it needs the WP7 emulator and decides to launch it. I opened up the Configuration Manager and created a new configuration just for Windows debugging and unchecked the building and deploying of all my WP7 projects yet it still insists on having the WP7 emulator open.
Is there a way to stop this behaviour?
In Configuration Manager uncheck deploy next to windows phone project
I bet it's very similar to this issue with multiple ASP.NET Development Server instances loading up no matter what project is being debugged. I can't check this right now to be sure, but I bet there might be a similar setting to this "Always start when debugging" option for the emulator.
So opening the Properties Window (View->Properties Window, not the View->Property Pages one) and then clicking on the project in Solution Explorer, then look for a similar setting to "Always start when debugging".
Alternatively, have you tried setting the target to a be Device instead of the emulator? That might also be a workaround.
It's probably because It's set as the startup project:
How to: Set Startup Projects