I could have sworn in WP7 whenever you deployed your application it overwrote the previous version. However it seems that it no longer does that? Is there a setting to turn that back on, or do I have to keep deleting the app before I deploy.
In my experience, deploying to the phone will do an in-place update (keeping all isolated storage, very similar to an actual store update) unless it detects a clean-rebuild has been performed or some other metadata has changed (such as the app ID).
So if you are seeing it do an incremental-deploy, that is normal. If you want it to do a clean reinstall, then do a clean-rebuild from visual studio (or just uninstall it from the phone before deploying again).
Related
I am trying to make autoupdate check and upgrade procedure (now from location on shared drive, in future maybe from server).
I have created "Visual Studio Installer" project that creates setup and it is possible to install the app. Also I have created another binary that searches for updates - if there are updates and user wants it, it runs the setup and app ends - if no updates, it runs main program. I have selected 2 binaries system in order to have possibility to run app without updates checking.
But If I confirm the update I am getting "Another version of this product is already installed. error code..." dialog.
I am not sure if my approach is right, probably not. But I found only commerce solutions and ClickOnce which seems to be for updating from network.
Thank you in advices for your answers.
It seems you are looking for something that allow you to have folder in your disk or a shared drive that can be used as local server to help you make updates without using internet connection , I introduce you to Squirrel.Windows its an open source installation and update framework for Windows desktop apps.
Here is link for Getting Started With Squirrel.
And here is a Youtube Video by Tim Corey where he explain Squirrel practically with demo windows forms project.
Happy Codding...
I'm currently working on a .Net framework 4 Windows application that I've inherited from another developer(that's left my place) that updates from a UNC location.
Whenever I take the old version of the app and publish the new version on top of it and run the setup it installs a separate instance of the application on the machine as opposed to updating the previous version, my suspicion is that this is due to the ClickOnce manifests being signed with a . PFX key that we have lost the password to, but I can't be sure that this is definitely the reason why.
does anyone know how I'd be able to publish the app up to update the previous version without the user having to uninstall/reinstall the app?
As (demanded) by Google, I added x64-Bit Support to our Xamarin.Forms app. When I sideloaded it onto our test-devices running the currently existing store version, I couldn't finish the install.
After uninstalling the current app, the new one installed just fine and everything worked as expected.
I forwarded the app package to our testers, told them to uninstall the old app and called it a day.
Today I learned, that the Play Store Version (v1.1.0) silently updated the current app (v1.2+) back to the old version.
I confirmed this via sideloading.
In my Android options I have two build targets:
armeabi-v7a (the old one)
arm64-v8a (the newly added one)
I thought, the device would select the right architecture and do its thing. How come, that the old app with obviously lower version number can update the new, but not the other way around?
Did I mess something up? Missed some settings or set the wrong ones?
If I inspect my built apk, the folders for each architecture are side by side, just as expected. The right .so files are present.
I'm working on Visual Studio 2017.
Android Build Config
I think you should pay attention to the app's versionCode.
A positive integer used as an internal version number. This number is used only to determine whether one version is more recent than another, with higher numbers indicating more recent versions. This is not the version number shown to users; that number is set by the versionName setting, below. The Android system uses the versionCode value to protect against downgrades by preventing users from installing an APK with a lower versionCode than the version currently installed on their device.
The value is a positive integer so that other apps can programmatically evaluate it, for example to check an upgrade or downgrade relationship. You can set the value to any positive integer you want, however you should make sure that each successive release of your app uses a greater value. You cannot upload an APK to the Play Store with a versionCode you have already used for a previous version.
I've been using this certain application among previous windows versions (Windows XP-Vista-7-8-8.1) and it has worked perfectly without having any issues, after upgrading to Windows 10 though it started showing EAccessViolation error and spams the place with message boxes saying "Runtime error at XXXX" (memory address)
So what I've been trying to achieve is creating a program in C# which runs the application under all compatibility modes one by one, to check which one works and which one doesn't - and sadly, none of them did.
The application is not mine and has stopped development.
Do you guys have any idea what has changed in Windows 10 code-wise, and how am I able to fix this issue? Is there a way to fully emulate another windows version and run it for this application alone? (Without having to set up a Virtual PC or anything)
Thank you in advance.
Note: Microsoft said that Windows 10 is completely backwards compatible, which it doesn't seem like it? The application does not use any driver, it's just a standalone EXE coded in C++/Lua.
Note2: The EXE calls a DLL which might be outdated for Windows 10, any idea what to do about the DLL? Is there a way to make it work as it did in previous windows?
You can help prevent these kinds of errors from occurring by updating your device drivers after formatting and reinstalling your operating system or installing a Windows Updates. Always install the latest Windows Updates before going through and updating your device drivers.
I am creating a WPF application and publishes it on the IIS. However when I am re-publishing the application since I do have code and UI changes, it doesn't show the changes on the application when I run it.
Anyone encountered this before?
These may be some of those obvious checks you have already done:
Have you checked that the version number is higher and the application did in fact update?
Has the application been set to automatically update?
Is this a online-only or offline mode application?
I found it out! It has something to do with the publish version. I am not incrementing the publish version since I am just publishing minor changes but the consequence is that ClickOnce will not let the application to download the updates from the server since the last version on the client is same as the publish version on the server and ClickOnce assumes the client is already updated.