WinAppDriver is shipped with MSI package and it requires admin to install/uninstall it. Although WinAppDriver is already shipped with Microsoft hosted build agents, but I want another version, how I can switch WinAppDriver to another version.
You can download the most recent version from their github page.
If you need a older version, please check their release page. You will need to click the "assets" toggle in order to see the downloadable files.
Related
I have my project in visual studio and i am using installshield as my windows installer. When I am installing new updated version of my application it will shows
Another version of this product is automatically installed like this...
How can I install new version by overwriting my old version?
Is there any way to configure in installshield or give me any other way
?
The error that you're getting is because the ProductCode has not been changed. This code is what makes your product/installer unique. Generally to author the upgrade you'll need to change this code and make sure the UpgradeCode is the same so that it recognizes what is already installed.
Authoring upgrades is a much wider topic and far too much information then can be covered here. I would suggest this page for learning about Windows installer upgrading.
Every upgraded version of install should have a different ProductCode. UpgradeCode is what tells the install package that this product has been installed. If ProductCode is also the same, install assumes you are installing the same product again. ProductCode needs to be different for each of the updated packages.
Under The Upgrade Paths, create a new path. Leave the min version blank (unless you need it), include min version yes, Max version should be set to the version You are installing now. Include max version to yes.
Each time you are installing an update, Increase the Product version(If u want to change) in the General Information section. Click on a new Product Code in the General Information Section Do not change the upgrade code.
Go back to the upgrade path, and set the Max version to the same version you are deploying now.
And make sure the Upgrade code in the "General Information" and "Upgrade path" are same.
This process uninstalls previous version, and installs the latest. No duplicates in add/remove programs.
If any doubt on this, comment your question...
I'm opening a solution which has a dependency on an outdated version of the Azure SDK such that Web PI wont install it.
This leaves me with the following error when I build the project:
WAT080 : Failed to locate the Microsoft Azure SDK. Please make sure the Microsoft Azure SDK v2.7 is installed.
What's the least amount of
steps I need to execute and
junk I can put into my environment
to make it load in VS and compile?
Navigate to the archived downloads page: https://azure.microsoft.com/en-gb/downloads/archive-net-downloads/
Follow the trail via the appropriate Azure SDK for .NET (As of Mar 2017, v2.7.1 is here)
Click the download button
Select MicrosoftAzureAuthoringTools-x64.msi
Select MicrosoftAzureLibsForNet-x64.msi <- x86 is not useful
Select MicrosoftAzureTools.VS140.exe <- 14:- VS 2015
I downloaded and installed each separately
HACK: My installation of VS2015 was slightly mangled, so I was still seeing a message from VS offering to install the 2.7 tools. I was able to get over that by installing the latest (2.9 at time of writing) tools, whereupon I got a clean build. I'll be doing a clean reinstall of VS and will research whether that can be avoided
I have upgraded a shipping Windows Desktop application from version 6.0.15.0 to version 6.1.0.0. I am using the Limited Edition of InstallShield, with Visual Studio 2013, for the installation program. Upon running the installation program on a PC that has version 6.0.15.0 installed, the installation program says "Another Version of this product is already installed"
I set the Product Version to "6.1.0.0." in the upgraded version. I did not change the product code or the upgrade code GUIDs (from version 6.0), because the documentations says not to change them. The documentation says,
"Because the product code uniquely identifies your product, changing the code after distributing a release of your product is not recommended."
"The upgrade code, stored in the UpgradeCode property, should remain the same for all versions of a product."
What must be changed in the InstallShield Visual Studio project to enable it to replace 6.0 with 6.1, without a need to uninstall the previous version (6.0) of the program?
There are a couple ways to do do this.
Assuming you want a major upgrade ( deploy everything again), you just need to go to the upgrades and right click, add major upgrade.
Once you have the major upgrade, you can choose any previous version.
Using Visual Studio 2010 Professional Windows Form App. Currently a ClickOnce application has only been incrementing the Revision value (1.0.0.15). Settings are to Automatically increment revision with each publish. Client app updates automatically before application opens.
If I manually increment the Major value (2.0.0.0), is this going to install another version of the application or just overwrite/update the existing version on a client's machine? I recall using the express version and this happened.
If you are using the minimum version in the Updates dialog, or your application is online only, ClickOnce only keeps one version on the client machine.
If you are not pushing the update as required (minimum version is filled in), and your application is online/offline, ClickOnce keeps two versions on the client machine. This means that the user can go to Add/RemovePrograms and back out the most recent version if needed.
ClickOnce installs whatever version number is in the deployment manifest (.application file) in the root folder of the deployment folders. If you change your version to 2.0 and deploy it, it will install 2.0. If you then decide you don't like it and want to go back, you can pull an earlier version of the .application file out of one of the Application Files folders and copy it to the root folder, and the next time the user runs the application, it will install that version. This doesn't work if you are pushing updates as required (min version).
If you want to run multiple versions of the same application on the same machine, you have to change the assembly name, the product name, the publishing folder location, and the installation URL.
Incrementing any part of the version number will not install another version of the application. It will simply update the existing installation.
I have a windows installer (MSI) project. I want to ensure that when i build it , it will be compatible with msiexec version 4.5.
Normally, compatibility is a problem with a lower verions. Windows Installer 4.5 is the latest version of windows installer and I would expect it to be backward compatible. So, most likely things that you are using will be supported.
What you should worry about is compatibility with older versions of Windows Installer. Most IDEs for creating installers would let you know if you are using something that is available only after some version of Windows Installer onwards.
If your IDE does not provide this feature then you should be aware of what all you are using in your MSI and make sure thats its available in the Windows Installer version you intend to you target with your installer.
That depends on the tool you use to build the MSI, you should be able to specify the required installer version there.
For example, WIX, which I frequently use has a "InstallerVersion" attribute at its "Package" XML Element. There I can specify which Windows Installer Version is required.
(Currently I do not require Installer 4.5 as it isn't deployed everywhere yet and I don't want to require customers to install the new installer on XP.)
Update:
Re-reading your question I get the impression that you use a Visual Studio Installer project. I believe you can't configure the Windows Installer Version there, but it defaults to Windows Installer 3.whatever (I'm not sure about the specific minor version). Setups created with that are compatible with Windows XP in any way.
I don't believe you WANT to require a newer version of Windows Installer when you use a Visual Studio setup project, as the setup project is very limited in what it can do. So to require a newer version of the installer you probably have a specific feature in mind (for example elevation on Vista). To use that feature you'd need a better tool to build installers anyways (like WIX, or Installshield or Wise or ...)