Navigation:  »No topics above this level« Commandes des mises à jour (Administrateurs seulement)

You may want to impose the way users upgrade QDV7:

▪Either simply restrict the type of upgrades (Beta, Official) users can access from Publisher's web site

▪Or publish your own customized QDV7 application from your own Intranet web site.

 

For your own publishing, the principle is very basic: you install QDV7 on a test machine from which you can upgrade from Publisher's web site and you broadcast your directory through your own web site.

You can then add your own files, shortcuts to QDV7 installation directory and publish versions which are previously tested in your environment.

The publishing tool is installed with QDV7. Check your installation directory for Publishing_Tool.

It allows two separate publications: Official and Beta, so you can decide who is entitled to test the application. So, you can install a version on the "template application" machine, test it locally, decide that some beta testers can use it and later, publish it as an official version to address all users.

In order to cross firewalls barriers, the applications publish HTTP files which are converted to binary files at client side. The encoding used is Base64 which is supported by all platforms. Once your users are able to browse the web or your intranet, they are normally able to upgrade QDV7, you don't have to give specific rights.

 

If, after major updates of the operating system, you get the message "Cannot Get Identifier" and QDV7 cannot start without a new license code, this is generally because some hardware components or names changed and QDV7 cannot build the unique identifier the license is bound to.

A file named DEBUGCANNOTGETIDENTIFIER.TXT is located in the Fixing-Tools sub folder. By pasting this file to the installation folder, you can get clear messages explaining why the application cannot get an identifier.

Log file is in C:\Users\<USER_NAME>\Temp\UpgradeQD.

 

Previously Created Estimates

The administrator in charge of a central deployment can prevent the users from receiving the pop-up question "Do you want to upgrade the file ..." when they open a previously created estimate.

There are two ways to implement it.

 

USING A FILE

The file in the QDV7 installation directory must be a simple text file named QDVMigrationSettings.INF and containing only one line which can be:

▪PROMPT

▪YES

▪NO

 

The file takes over the key. So when a file exists, possible keys are ignored.

 

USING A REGISTRY KEY

You can place a registry key in HKEY_LOCAL_MACHINE\SOFTWARE\QDV\MAIN\ named MigrationSettings.

It can contain:

▪PROMPT: the question is asked (unless a file says otherwise)

▪YES: the question is NOT asked and the migration is carried out

▪NO: the question is NOT asked; instead a message says that you cannot upgrade the file.

 

When Deploying QDV7 with Click Once (deployment to user profile, a non protected folder), you must place it in HKEY_CURRENT_USER\SOFTWARE\QDV\MAIN\