Pages: 1
Print
Author Topic: Deploy a new XMAX version to clients  (Read 2640 times)
KdG
Member

Posts: 19


WWW
« on: October 28, 2010, 07:23:00 AM »

Our clients currently run XMAX version 5. We want to upgrade them to version 6.
I placed the XMControl.CAB version 6 on the server and changed the html-download page to:

<OBJECT CLASSID="CLSID:55EC30BE-EA43-45C4-ABD7-DDA7F6943D46"
  ID="myIDcode"
  CODEBASE="http://pc-kees/xmax/cab/XMControl.CAB#VERSION=1,0,3,6.0.0.159">
</OBJECT>

I also tried:
  CODEBASE="http://pc-kees/xmax/cab/XMControl.CAB#VERSION=6.0.0.159">

(I extracted the version number from the XMControl.dll)

Now the programmers guide says:

Note:....If you specify a number that is greater than the currently-installed CAB file, a newer version is sought and installed. You can use this mechanism to ensure that clients viewing your HTML page are always up to date with the latest version of the XMAX CAB file (provided you update the page with the new version number). If you erroneously specify a number higher than the latest version of XMAX, the CAB file is repeatedly installed with each page-view.

Somehow this does not work. The new CAB is only downloaded to the client after I manually remove the installed files from "C:\windows\Downloaded Program Files"

My questions are:
- Should the mechanism as stated in the PG-note work?
- If so are there conditions that I don'n meet?
- Is there another way to deploy the new version, without having to uninstall all "Downloaded Program Files" manually on each client?
Logged
Derek Read
Program Manager (XMetaL)
Administrator
Member

Posts: 2580



WWW
« Reply #1 on: October 28, 2010, 03:50:48 PM »

Yes, this should work. Note that this is not an XMAX feature, it is a Microsoft Internet Explorer feature. We merely provide the CAB file.

Microsoft specifies in their documentation that the major/minor version numbers are to be separated by commas (your example uses periods). That's what I would check first.

You can find the version numbers we declare inside the CAB file in the manfest, which is XMControl.inf.

These pages might also be of some help:

Pre-IE7: http://msdn.microsoft.com/en-us/library/aa741199(VS.85).aspx
IE8: http://msdn.microsoft.com/en-us/library/dd433049(VS.85).aspx
Discussion about non-admin deployment in older IE versions: http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/cb6f8b60-42b6-4ff0-bcd5-dd8f1ff13d1d
Mods to CAB files: http://support.microsoft.com/kb/176810
IE6 Bug: http://support.microsoft.com/kb/315498 (this last one would likely only affect you if you modified or repackaged our CAB)

If your specific issue still occurs you may wish to read Microsoft documentation for your specific version of IE on your specific version of Windows.
Logged
KdG
Member

Posts: 19


WWW
« Reply #2 on: November 01, 2010, 04:46:18 AM »

Hi Derek,

It works fine now. Thanks a lot

I did have the comma's wrong and the 1,0,3,xxx.
Both I found in the XMetal Prrogrammers guide.
Maybe something to correct in the PG for the next release:
In the page "Download the XMetaL XMAX CAB file"

Not
-  CODEBASE="http://www.mydomainname.com/XMControl.cab#VERSION=1,0,3,xxx">
-  The ‘xxx’ portion of the version number (above) should be replaced.
But the complete 1,0,3,xxx should be replaced.

Not
- Get the version from the XMControl.dll properties-version tab (this number has points instead of comma's)
But get it from the manifest  "XMControl.inf" (which is comma separated)

Cheers,
 Kees

« Last Edit: January 19, 2012, 01:40:17 PM by Derek Read » Logged
Pages: 1
Print
Jump to: