topic Re: Execute addin code after opening project in ArcPro 2.7 in ArcGIS Pro SDK Questions

Execute addin code after opening project in ArcPro 2.7

PrashantKirpan — Tue, 09 Feb 2021 23:56:52 GMT

Hi,

I want to execute my addin code after opening project in arcpro. I've config file which stores project related data. Now whenever I open project I need to activate addin and execute code to retrieve config file, to avoid this behavior I would like to execute some code by default on opening project.

Any help would be appreciated,

-Prashant

Re: Execute addin code after opening project in ArcPro 2.7

Anonymous User — Wed, 10 Feb 2021 00:21:51 GMT

Hi @PrashantKirpan ,

It sounds like once our addin is installed, we just want it to execute code in response to the ProjectOpened event. You can find an example of subscribing to this event to execute code when a project is opened in the BackStage_PropertyPage community sample.

Hope that helps!

Re: Execute addin code after opening project in ArcPro 2.7

PrashantKirpan — Wed, 10 Feb 2021 04:56:07 GMT

Thank you JamesBrander, perfectly working for me.

-Prashant

Re: Execute addin code after opening project in ArcPro 2.7

Wolf — Wed, 10 Feb 2021 21:02:17 GMT

It seems that you got your add-in to work, but I just wanted to point out that by default add-ins are 'Just-in-time' (JIT) loaded, meaning they are not loaded and running until you interact through the UI with your add-in. If you want your add-in to work from startup (i.e. in order to listen to a project open/close event) you have to change the JIT default behavior by turning the 'autoload' (in config.daml) to true. You can find more documentation here: ProConcepts Framework · Esri/arcgis-pro-sdk Wiki (github.com)

Re: Execute addin code after opening project in ArcPro 2.7

JamalWest2 — Wed, 21 Apr 2021 16:31:04 GMT

If I have a proWindow in my add-in how can I cause that prowindow to initialize when the add-in is loaded? right now it only happens ona click of the button.

Re: Execute addin code after opening project in ArcPro 2.7

Wolf — Wed, 21 Apr 2021 19:07:26 GMT

Usually you would not initialize a ProWindow before the class is instantiated, which happens when the ProWindow needs to open. I would recommend to move any initialization code into the Module class and make it accessible through an internal (or public) property in the Module class as in this example: Framework - ProWindowMVVM Community Sample