Hi @sivatejag
Could you explain each point in more detail (preferably with some screenshots)?
We value all user feedback and will definitely look into the performance issues you experienced, as long as we can recreate your situation. Some sample file would help here as well.
Moreover, after consulting our team, I can deliver some positive news :
- “Loading the xamls containing the activities from library takes forever to load it” - this is due to the high number of dependencies that are passed in by studio for a project and are loaded by activity initialization and is a known issue that will be addressed
- “Also libraries don’t allow dynamic invokes…for example if you want to use an expression in the Invoke XAML within a workflow” - in this case compiler identifies the case and reports it as unsupported. This is a feature that was already requested and we are looking into it.
Thank you for your feedback. I hope this is helpful for you to know the current situation