- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I am starting to move some of my external rules into an addin. I just moved a rule in that process components and it is behaving differently than when I run it as an external rule.
The difference occurs when I activate a sub assembly's ModelState. I have no dialog boxes at all when running the external rule, but when I execute the addin function button I get a prompt to save the changes to the part files within the sub assembly as I'm activating another ModelState.
I can workaround this difference by manually toggling SilentOperation on temporarily and back off after I activate the ModelState, but I don't know why I need to do that for the addin function but not the external rule.
Is there something I can set up in my addin to make it behave like the external rule when activating ModelStates?
Why is the Activate Method silent by default in iLogic but not when called in a vb.Net addin?
Solved! Go to Solution.