KnowledgeSync Ideas

The WinWrap scripting system isn't fit for purpose.

1. References are not possible.

   1. As far as I can see the inability to add references is due to WinWrap licensing model meaning each script has to be called by a standard KS script. Calling them inline using reflection is impractical.

2. The scripting language is not well known. It's another language to learn and all it's intricacies.

3. It's not free.

If this was replaced with Powershell modules we would have the following benefits:

• Community Support - PowerShell has a large and active community, leading to an abundance of resources, scripts, and solutions. This community support can be crucial when you need assistance, encounter issues, or want to explore best practices. You can even ask ChatGPT to write you a module to get you started.

• .NET Framework Integration - PowerShell seamlessly integrates with the .NET Framework, allowing you to leverage its extensive class library. This is extremely difficult to implement with WinWrap .Net, it is the polar opposite of seamless.

• Simplified Deployment - PowerShell is a standard component in Windows operating systems, ensuring its availability across Windows environments without additional installations. This could simplify deployment and maintenance.

If this was implemented I would also like to see the limitation of a script being the only trigger in an event removed.