Having trouble installing developertools.msi [Inv 2023, VS Community 2022]

[Anonymous]

Hi,

I was wondering if there's a compatibility issue between Inventor 2023 developertools and Visual Studio Community Edition 2022.

I'm trying to access the EventWatcher tool.

Thanks

[vcondarcuri5VKNC]

It'll only install on non-Community version.  Also only in earlier version.

Use msi viewer to extract: https://apps.microsoft.com/store/detail/msi-viewer/9MZTR9QS01GN

[Frederick_Law]

Forum switch account again 😒

PS

2023 SDK work with VS 14.0 to 16.0, VS 2015, VS 2017, VS 2019

[Anonymous]

Oh I had no idea .msi's could be inspected and used like that.

But you're saying it's not going to work anyway, with just the community edition.

Do I need the developer tools to make an add-in? I know I'm going to have a hard time convincing my company to just upgrade the subscription. I'm not even sure what the benefits of the SDK are in general.

[Frederick_Law]

You don't need SDK to make addin.

The SDK has VS Wizard which won't work in VS Community.

As least I can't get them to work.

SDK does have addin Template.

You may not need Addin, iLogic can do a lot.

[Anonymous]

Ok great, that's good to hear.
Yeah I've been working with iLogic for over a year, but a lot of our routines run on save, and there's a huge performance burden I want to distribute across a more granular set of events, so users aren't waiting literal minutes for Inventor to check the material of an .ipt (among other things) is good, when really the .ipt was dirtied for some negligible reason. Instead I'm hoping to put that, for example, on a material-change event, if one exists.

[Frederick_Law]

iLogic should be pretty fast.

VBA macro could be slow.

I went from VBA to addin long time ago and do some iLogic now.

Check condition before running any loop or do anything.

If 'this' is 'true then

  loop

end if

Condition check are much faster then loop or any other operation.

[Anonymous]

Yeah I'm using a class library with minimal code in the rules themselves, and I early return everywhere.
I think the performance burden comes primarily from switching among model states.
Also I'm still unclear on when and when not to use the FactoryDocument member vs opening the document.
And I had been using the ModelStateTable to shortcut certain operations and avoid switching model states, but it ended up producing a lot of bugs (those messages you see when switching model states where it says the values are desync'd and asks if you want to update them or not), and when we switched to 2023, crashes, at which point I stopped writing to it at all.