Hi Juan, This is because the result of the multiplication is too large to fit even in an Int64. The maximum positive value that can fit in the 64 bits of such a type is 9,223,372,036,854,775,807,as you can see with ? Int64.MaxValue:ToString() Your test number of 123,456,789,012,345,678 is already ve...

Hi Franz, There's a tool from Paul Piko (VOPP if I remember the name correctly), which can analyze .aef files, but I'm not sure if you can find it now and how easy it makes it to compare entities. Another thing you could do, is to export both aef files with VOXporter (after disabling all the options...

Hi Christian, I think that's a leftover from the VO help topic. In .Net, you cannot link specific functions, it's the complete assembly (dll or exe) containing them that is either loaded or not. So practically this command is not needed anymore, as it's highly unlikely that a dll used in a macro exp...

Hi Cyril,

The Zap problem was reported again some days ago and is already fixed, the fix will be included in the next X# release.
We were not aware of a problem with Reindex though, does this only happen after the Zap? If yes, then probably the Zap fix takes care of that, too.

Hi Kees,

I think what happens is that when adding the files manually, the resources are not triggered to be recompiled, as the code is. If you do just a "Rebuild" on the project where you added the files it will trigger it and it should be enough.

Ah, I just noticed that VO does require the use of SELF: for calling methods and properties, but not for accessing class variables! This is so bad... In X#, the /enforceself option covers all cases and I think we should keep it this way. But it means it's not the best solution in your case, since en...

Hi Basile, In order to prevent this, you'd need to enable the compiler project option "Enforce SELF", which will make VO require to use "SELF:" for accessing any class variables/properties/methods as in VO. Without SELF: in your code, when this option is enabled, the compiler wou...

Hi Kees, Ouch, adding existing windows this way is really pushing it, those are meant to be "one" entity. Just wondering, why is this way of adding "really pushing it" and what do you mean by that it should be one entity? The code for a window is always split in 3 files I think. ...

Hi Kees, I guess it's too late now, but you could just add the projects one by one in the main solution that you are working on. What you needed to do is to select Add Existing->Project and select the .xsproj file. Anyway, we will look into the vowindow add problem, maybe it can be improved a bit. A...

Hi Kees,

VOXporter already adds those files as part of the VS project that it creates, why do you need to add them again?