Yep, I know. But I hoped something more "transparent"... if we deal with several instances and change with certain frecuency (as it's my case), having to define direct accesses when we have a link in the "cube" menu, doesn't seem too clean. For Linux/Mac users, the solution is clean. You just define your aliases file, and you just can install your IRIS instances... all of them would make use of them seamlessly... that's the functionality. Right now, for windows users, it's incomplete. A pity because it's a really very good feature to have, our terminal/shell needs these kind of tools, but it has to be much easier to reuse among instances.  IMHO. 

Perhaps it would be as easy as to change our installer so to include that argument out-of-the-box in the call to Terminal in the cube... and then let the developers build their own script in their own home directory.

2 decades went by Robert??? 😰 Time flies... CSP was great at that time... it was a breath of fresh air for our installed base and competed very well with other technologies in those years... But current front-end technologies make magic nowadays... they're powerful and change a lot and fast. Which is good... and bad... Angular versions change in a blinking... in 7 years, 11 major versions.....difficult to follow them up. I realize the beauty and simplicity of our proposals...with CSP, ZEN,... when you start to learn other front-end frameworks... but the communities behind them let them improve and grow up day-to-day... no way that a single company can compete against that.

I'm running also with last Windows 10 version and WSL2... it goes really well till now. I found that WSL fights for resources with Windows and although it releases RAM and processors when they're not used in a while, it's not as agile as I would like... so, the only tweak I had to do was to limit the resources that the WSL2 could take... to do that it's just required to add a new file in your user profile folder: c:\Users\<youruser>, call it .wslconfig and add something like:

[wsl2]
memory=6GB # Limits VM memory in WSL 2 to 6 GB
processors=2 # Makes the WSL 2 VM use two virtual processors

Terminate WSL2 and launch it again and that's all...  from then on, your WSL2 won't take more resources than specified... if, for some tests for example, you need more, you can change the file and increment the resources.... this is something that likely will be addressed in a more unmanaged way in the future... at least is what Microsoft WSL teams is saying in the forums.

BTW, you can find WSL2 well under c:\Users\<youruser>\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu.....  in the case of my Ubuntu distribution... but you can change where is stored: https://github.com/MicrosoftDocs/WSL/issues/412

ZPM forces to use categories in the folder structure... perhaps, to make it easier, VS Code ObjectScript extension should be configured with that option by default... just an idea.

Also, is it there any place with full doc about module.xml? Articles are full of really useful info but having to navigate through all of them is a bit confusing.