751
We're running GP2015 and have built a number of customizations using VSTools.
At startup, does GP go through each DLL file in /AddIns to check if they implement IDexterityAddIn and then attempt to load them? Would having extra files in that folder that do not implement IDexterityAddIn cause a performance hit?
*This post is locked for comments
All the above responses are correct, however, you can direct the Runtime Engine to load specific assemblies and versions by editing the Runtime Engine Configuration file (Dynamics.exe.config), under the <addins> section. The Runtime Engine first looks at the configuration file to determine if it should load specific assembly versions (whether in the GP root folder, the AddIns folder, or loaded in GAC), then loads all other assemblies contiguous to the engine. Finally it scans the AddIns folder looking for all other assemblies implementing the IDexterityAddIn interface.
So, yes, this can be taxing performance wise if there are numerous assemblies to evaluate.
Yes it scans through the AddIns folder looking for dlls that implement IDexterityAddIn, so as you can imagine this can impact startup times, especially if then also has to instantiate large complex addins.
I see 10-15 seconds from login form to actually being able to login.
Hello Jerry,
In earlier versions of Dynamics GP, all of the dll files and such were placed into the addins folder, but in newer versions, those dll files are mainly in the main GP directory and not in the addins folder itself.
With newer versions of GP, it's mainly 3rd party and customization dlls that get put into the addins folder. Looking at a new install of GP 2018, there is one file, Microsoft.Dynamics.GP.PreviewPane.dll, that exists in the addins folder.
When you launch Dynamics GP, I believe it does look at the dlls in the GP code folder and addins folder, because for certain products, such as SmartList Builder, if you remove it from the Dynamics.set and attempt to launch GP, you'll get an addins error message.
So, based on that, if you have a large volume of files in the addins folder, it could potentially cause a performance hit when launching the application.
The best way to test would be to install a 'clean' Dynamics GP 2015 without any 3rd parties or customizations, then test launching GP to see how much of a change that is compared to your existing install(s).
From there, you could add 3rd parties and/or customizations one by one until you find it starting to slow down again.
Please let us know if you have further questions.
Thank you,
#1
André Arnaud de Cal...
292,865
Super User 2025 Season 1
#2
Martin Dráb
231,723
Most Valuable Professional
#3
nmaenpaa
101,156
Moderator
Share
Report
All responses (
Answers (
