windows - Is it necessary to use unique WIX product ID for all product versions if upgrade not supported -

-

We have a product that uses the WIX installer and only our support team has demonstrated the installation routine. There are two steps in the only way used for the upgrade application:

  1. Delete the previous version of the installed app. We have a list of all product GUIDs by which we can remove all possible versions (MSIXAC / X GUID)
  2. Install the latest one

Upgrade, Repair Or older versions of the installation will never be used for this product (this is impossible because the deployment is done by the script).

Is it necessary to make product ID unique for all upgrades, if we do not use the upgrade functionality, or is it possible to place the same product and upgrade ID?

From the documentation of: This ID should be different for different versions and languages. Therefore, you should generally set id = "*" in the product element, so that you are unique to each installer package.

I can not think of a reason because you want this ID to be for different versions of your installer; This window will confuse the installer, e.g. You may get correction dialog when you try to install a new package without uninstalling the previous one.

The upgrade code should only be relevant when you use MajorUpgrade , but it seems that you are not using it.

Edit : OK, so you want to keep the product ID the same so that it msiexec / x {GUID} .

Alternatively, the installer allows itself to record the product code GUID somewhere, such as by. Or you can write product guides at a certain place in the registries, and then you can write the script that reads to uninstall that value.


Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more