Pages: « 1 2 3 4 5 6 7 8 9 10 »
 on: February 21, 2018, 03:47:26 AM 
Started by hico - Last post by hico
Thanks for your advice! That sounds like we've done everything fine till now, we use XMetaL API in a dll, which seems to work. If we have more than one Macro, all macros are packed into the .mcr build by XMetaL Developer, right?

The thing is...we have a lot of different schema DTDs. How can we deploy these? In the past, we handled this with the help of a catalog file, that referenced sub-catalog files and so on, so that referenced schema DTDs could be resolved. I know that there's a catalog in "Rules" folder, but can I reference my own catalog in any way? Or does I have to build my own document level customization for every schema DTD? How would I deploy the .xac, that means, in which folder do I have to place it, or reference it?

We are on the very beginning of our customization, so, sorry for your time.

 on: February 20, 2018, 01:11:41 PM 
Started by hico - Last post by Derek Read
It sounds like this is an application-level customization. In that case you can ignore the XAC file. Both are built just because that is how XMetaL Developer was designed but the XAC file isn't really useful. You can consider your application-level customization to consist of the MCR file itself (unless it calls other code like an XFT form or a DLL that you need to deploy as well).

XAC files are ZIP files containing a copy of whatever was "built" when you select build in Visual Studio, together with a manifest that lets XMetaL Author know what to do with the file(s). A XAC is (arguably) slightly more useful for a document-level customization where your customization consists of DTD/XSD/RLX/RLD, CSS, CTM, MCR, XFT and possibly other files. All of those files are zipped into a single XAC file. When that file is read by XMetaL Author (or XMAX) it is first unzipped to a temp folder then all the files are read in as they would be if opened directly. The single benefit (if you can call it that) is that you can then deploy a single file. However, this can add to the complexity of debugging issues, and it makes it much more difficult to tweak a customization after deployment.

I did a webinar a few years ago on customization deployment. The accompanying document that describes the subject in detail now lives here:

 on: February 20, 2018, 06:28:07 AM 
Started by hico - Last post by hico
We have installed XMetaL Developer recently. The output of a customization project is, e.g., a .mcr and a so called .xac. So, how do I deploy the .xac? If I copy the .mcr in the "Startup" folder, the .mcr seems to run, I also can debug it with "debugger" keyword, as I read here. But what about the .xac? I did not find anything about .xac deployment in the developer and customization guides and would be very thankful for your assistance. Kind regards

 on: January 22, 2018, 03:25:17 PM 
Started by lerche - Last post by Derek Read
Any MCR file you place in the Startup folder is Application-level (available before any documents are open and for every document type).

 on: January 21, 2018, 03:12:47 PM 
Started by lerche - Last post by lerche
Thank you very much for your answer!

It's a great pity, but it is good to know. What would you suggest for writing a global macro that can analyse the content for several kinds of XML documents? I think the only way is to write a macro for a specific dtd. After that i would deploy the resulting macro in the startup folder. Are there any other good options?

 on: January 19, 2018, 08:03:09 PM 
Started by lerche - Last post by Derek Read
This is a known limitation. It is documented in the readme for XMetaL Developer as "Application-level XAC debugging does not work".

You will need to deploy the MCR file in this case, and if you need to debug it you can insert a debugger statement into the file at the location you want to trigger script debugging. It isn't as elegant as being able to start it from Visual Studio with the ability to set a break point but it should give you script debugging.

For JScript insert the keyword "debugger" (without quotes) at the line you wish to trigger the debugger.

 on: January 18, 2018, 04:35:06 PM 
Started by MichaelLohr - Last post by XMetaLOldTimer
Hi Michael,

When you add a project reference to the XMAX dll, Visual Studio should auto-generate these two dlls.  You can search the project directory to see if the Ax...dll is there.  If the Ax….dll is not generated, you can use aximp.exe to generate it.  Generally, it is recommended to delete these two project references prior to reimporting the reference to a newer version of the XMAX dll (or any other COM dll).

Beyond the information provided above, we recommend searching Visual Studio forums for more help.  Here are few links I found while researching your question:


 on: January 18, 2018, 02:50:03 PM 
Started by lerche - Last post by lerche

First of all: Thank you Derek Read for activating my profile on this board.

My Question relates to the following system:

XMetaL(R) Author Enterprise
XMetaL(R) Developer Version
Visual Studio 2015 (Community Edition) Update 3
OS: Windows 10 Pro, English

I am new to XMetaL Developer and I plan a small Application Customization for XMetaL Author Enterprise with my Experience in JavaScript. Therefor I created a new project with Visual Studio and tried to write a simple 'Hello World' program by testing different events like

  • On_Application_Open
  • On_Application_Close or
  • On_Update_UI

When I start the program out of Visual Studio by pressing the 'Start' button, it is strange that the code will not be executed. By creating a breakpoint in the line
Application.Alert('Hello world');

I can see that the breakpoint would not be hit. You can see it by the red circle with the white filling (have a look at attachment). But when I copy the build artifact (*.mcr file) into the startUp folder (C:\Program Files\XMetaL 12.0\Author\StartUp), the code will be executed. I know it, because I can the see my 'Hello World' alert boxes.

Is this problem a bug of XMetaL Developer or am I doing something wrong?

I would be grateful for your help.


 on: January 17, 2018, 04:41:58 AM 
Started by MichaelLohr - Last post by MichaelLohr
Hi Derek,

I'm new to the XMAX development and try to update our existing application from "XMAX 10" to "XMAX 12".

We have a C# client application where the XMAX control is used inside.

In VisualStudio we have currently the following two references:
* Interop.XMetaLControlLib
* AxInterop.XMetaLControlLib

I can renew the first reference by making an reference to the "XMetaL XMAX 12.0 Type Library" in the "COM"-category,
but I do not know who to update the second one.

Could you give me a hint who to renew this?

Best regards,

 on: January 11, 2018, 02:40:27 PM 
Started by KdG - Last post by Derek Read
It does appear to be functioning oddly. I'll let the development team know.

Pages: « 1 2 3 4 5 6 7 8 9 10 »