Effective January 1, 2016, Microsoft has mandated that software vendors digitally sign their products using the SHA256 algorithm. All XMetaL 11.0 and newer products are signed using the mandated SHA256 algorithm. As a result of using this new signing algorithm, attempts to install the software on older unsupported Windows systems such as Windows XP will fail. Please confirm the system requirements are met.
With the release of version 9.0, the software no longer requires an Internet connection to register or unregister a per-seat license. A new license file (e.g. XMDE.lic) is required to activate this software.
Note: Older .lic files are incompatible with this version.
Contact your JustSystems Sales representative if you have further licensing-related questions.
XMetaL® Developer is a plug-in to Microsoft® Visual Studio®. Your system must have one of the Microsoft Visual Studio standard language products, e.g., Microsoft Visual Basic® .NET Standard, or alternatively Visual Studio .NET Enterprise or Professional versions installed prior to installing XMetaL Developer. See https://www.visualstudio.com/.
Your operating system must meet the system requirements for Visual Studio for your particular Windows version. XMetaL Developer supports the following:
In addition, your system must have the following, or higher:
Required Memory:
XMetaL Developer runs on the following operating systems:
Prior to installing XMetaL Developer, you must have already installed Microsoft Visual Studio, preferably 2012 or newer.
With newer versions of Microsoft Visual Studio, the Microsoft Help feature is not installed by default. Please insure this feature is installed in order to view the XMetaL Programmer's and Customization Guides.
This version of XMetaL Developer can only be installed beside like versions of XMetaL Author and XMetaL XMAX (i.e. v12.0).
If you are upgrading from a previous release, you need to run Add/Remove Programs and remove any previous versions of XMetaL Developer before you install XMetaL Developer 12.0.
Note: If you plan on using the XMetaL Java API Toolkit included with XMetaL Developer, it's recommended that you install the Oracle JRE before installing XMetaL Developer.
Activating your XMetaL Developer software is required in order to be fully licensed to use the software. The license information required for activation is provided by a license file.
With newer versions of Visual Studio, you must enable the option which installs the Microsoft Help feature in order to view the XMetal Customization and Programmer's Guide content.
Please re-run the Visual Studio installer to modify its installation to include the Microsoft Help feature. After the Microsoft Help feature is installed, you can either re-run the XMetaL Developer installer to repair its installation which will add the XMetaL help guides. Or, you can use Visual Studio's Help Manager's features to manually add the XMetaL help guides (see next section below).
The XMetal Developer installer includes an automated script for integrating the Customization Guide and Programmer's Guide into Visual Studio. This automated script will not complete successfully if UAC is enabled.
To install these guides successfully with UAC disabled, follow these steps for Visual Studio 2012 and newer:
To install these guides successfully with UAC disabled, follow these steps for Visual Studio 2010:
You can re-run the installer by selecting XMetaL Developer from the Add/Remove Programs Control Panel.
If you have already installed XMetaL Developer, the installer presents various options if you run it again, including the option to uninstall XMetaL Developer. See the section Maintenance installations below for more information.
You must have certain components of Microsoft Internet Explorer, version 10 or above, installed on your PC in order for XMetaL Author to function.
At the start of the XMetaL Author installation, you will be warned if Internet Explorer is not installed, or if the version that is installed is an older incompatible version, and you will be given the option to install it.
You can also go to this web site: http://www.microsoft.com/windows/ie/default.htm and download the latest version of Internet Explorer. Internet Explorer is language-specific; if you are using a non-English version of Windows, make sure that you download the version (plus service pack if required) that applies to your system.
Microsoft regularly provides updates to their software. We strongly recommend that you visit Microsoft's web site to get any patches or updates to Microsoft Internet Explorer.
The XMetaL Database Import wizard requires Microsoft Data Access Components (MDAC) to be installed on your PC in order to function.
At the start of the XMetaL Author Enterprise installation, you will be warned if MDAC is not installed, or if the version that is installed is an older incompatible version, and you will be given the option to install it.
You can also launch the MDAC Installer from your XMetaL CD (in the redist folder). Alternatively, you can go to the Web site http://msdn.microsoft.com/en-us/data/aa937730 and look for "MDAC 2.1.2.4202.3 (GA) Typical install for x86" or greater (later versions are referred to as RTM instead of GA).
The Database Import wizard will not function unless these components are installed before XMetaL Author Enterprise is installed. If you have already installed XMetaL Author Enterprise, and the Database Import wizard fails with one of the following errors:
Automation server can't create object
ODBC Driver manager: Failed to load resource DLL odbcint.dll
then you should uninstall XMetaL, make sure the required components are installed, and then re-install XMetaL.
Viewers for PDF documents are available at the following locations:
PDF: http://www.adobe.com/products/acrobat/readermain.html
After the installer is finished, you may be asked to reboot your system prior to launching XMetaL Developer for the first time. If you do not, you may experience unpredictable behavior.
You can perform various additional installation tasks after you have installed the product. For example, you might want to do one of the following:
Note: In order to be able to perform maintenance installations (except for the 'Remove' option), you will need to have the files that you unpacked during the initial installation still available. If you installed from a CD you will need the CD media again.
If you have already successfully installed this version of XMetaL Developer, you will see a dialog box that gives you three options: Repair or Remove.
Select Repair if you suspect that the currently installed product has become corrupted in some way. Repair will reinstall the same set of components that were installed in the previous installation.
Note: Any files that you downloaded must still be available on your hard drive if you choose this option.
In some cases there may be two or more choices that the installer can make when installing certain components. In this situation a dialog box appears asking for your preference.
devenv.exe /setupNote that devenv.exe is normally found in C:\Program Files (x86)\Microsoft Visual Studio nn.n\Common7\IDE.
Other types of User Data, which might be files that were created directly by the user or that contain user preferences that a customer may wish to re-use in a later version installation, are not removed at uninstallation time. If you wish to remove them you must remove them manually after uninstallation has completed. Such files may exist here:
Due to bugs within the XMetaL Developer 9.0 installer, certain registry entries are removed by mistake. To fix this issue, goto the Add/Remove programs control panel and repair the XMetaL Author installation.
When running a form with the XFLayout program, script errors may occur if a script is executed that references XMetaL Author or XMAX top-level objects such as ActiveDocument or Selection. This is a known issue and can be worked around by running the form via XMetaL Author or XMAX directly. With the x64 version of XMetaL products now available and the XFLayout program being only 32-bit, it was necessary to stop injecting top-level objects when running a form.
After you upgrade to XMetaL Developer 12.0, you may see a program entry in Add/Remove programs left-over from a previous version. You can safely remove the old program entry and ignore any error messages given.
When debugging a customization using Visual Studio 2008 or older, the debug session does not end after quiting XMetaL. In order to work around this issue, simply "Stop Debugging" from the Debug menu.
Confirm that XMetaL Author (xmetal.exe) is version 12.0 or higher. If the version is lower, download the latest XMetaL Author Enterprise software (available at the same ftp link as before), uninstall your current version and reinstall the newly download software.
The XMetaL Developer Installer Setup program will warn you if you do not have sufficient privileges to perform the installation (e.g., if you are logged in as a normal or restricted user). The solution is to install XMetaL Developer by logging in as a User who has Administrative privileges.
Dialog boxes displaying the following unregistration errors might appear during uninstallation of XMetaL Developer 4 (if you are uninstalling XMetaL 4 prior to installing XMetaL 12.0):
Error 1905. Module "C:\Program Files\Corel\XMetaL 4\Developer\Bin\XMWizard.dll" failed to unregister. HRESULT...
Error 1905. Module "C:\Program Files\Corel\XMetaL 4\Developer\Bin\DTDDataProvider.dll" failed to unregister. HRESULT...
Error 1905. Module "C:\Program Files\Corel\XMetaL 4\Developer\Bin\CTMDataProvider.dll" failed to unregister. HRESULT...
Uninstalling the core XMetaL Developer after uninstalling an XMetaL Service Pack causes the error.
You can safely ignore the unregistration errors.
Anti-virus programs sometimes interfere with the installation process, causing the installer to hang, usually within a short time after it starts up. If you encounter this problem, and you have any type of anti-virus program installed on your computer, disable it while you are installing XMetaL.
Please add a reference to the group by do the following:
For more information on setting up Visual Studio IntelliSense, see this MSDN page.