I assume, that the packaging error under Windows will never be removed: so the packaging process for a WBPro oriented application still crashes (and prevents output - to remeber: the packaging processes queries all OLE interfaces on the system and some of the interface do not behave as the ST code expects). Perhaps this will only be a case for developers having VisualStudio installed ... so mentioning WBPro is not quie right - its the OLE subsystem
We can solve these issues pretty quickly, but I think we are not clear on exactly what packaging configuration and steps are needed to reproduce this.
Would you mind either sending something to Vast-support or otherwise some exact detail on how to reproduce.
We’ll be happy to fix
its my faulty code and its has been my faulty code for years now which produces this package error ....
The classes below are indeed my own classes I once wrote for a windows extension to communicate with .NET - I did not follow the protocals VASmalltalk suggests for the OSI* classes on windows side ...
Am Montag, 6. August 2018 18:08:26 UTC+2 schrieb Seth Berman:
A couple of issues.
The first is...these classes are not familiar to anyone on the team.
I've loaded all features and windowbuilder...and I don't see these.
Is this Instantiations code? Looks like .Net interop. Can you help me locate these?
OSICLRMetaHost class OSICLRRuntimeHost class OSICLRRuntimeInfo class
The second is if this gets more involved...we're going to need to move this to our case tracking system
and that gives an opportunity for our whole team to collaborate and historically track this issue.
On Monday, August 6, 2018 at 8:15:13 AM UTC-4, Seth Berman wrote:
Thanks Marten for the additional info.
We have someone actively looking at this.
On Monday, August 6, 2018 at 5:49:20 AM UTC-4, Marten Feldtmann wrote:
The following classes are throwing the exceptions during packaging an OLE (WindowBuilder App) based application:
Am Mittwoch, 25. Juli 2018 18:09:22 UTC+2 schrieb Seth Berman:
Thanks for the link Marten.
We’ll work on reproducing it and figure out what the issue is