Finance | Project Operations, Human Resources, ...

Visual studio 2022 - DevTools extension issue

(3) Share

Report

Posted on by Awaxx

229

Hi guys,

When i right click any object on VS2022 i got this error message : The type initializer for 'Microsoft.Dynamics.Framework.Tools.Extensibility.AddinFactory' threw an exception

Also when i look to addins it's empty :

If someone have a solution please.

I tried to uninstall and install VS2022 but nothing change.

Regards.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (7)

Answers (0)

Mariano G. 3,598 on at

Like (1)

Report
Copy link

Link copied!

You should find the extension under "Extensions\Manage Extensions...":

You can try to uninstall the extension, but before doing that, be sure to check the version installed in your visual studio, you'll need to download the platform update from LCS, once unzipped the platform update file, you'll find the visual extension in DevToolsService\Scripts folder:

Was this reply helpful? Yes No
Martin Dráb 239,029 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Please give us some context. Did it work before? If so, what has changed? For example, didn't you install any update just before it stopped working?

How did you setup the environment? Is it CHE, UDE or did you set up a VM from the VHD?

Was this reply helpful? Yes No
Awaxx 229 on at

Like (1)

Report
Copy link

Link copied!

Here's the context.

I was previously on VS2019 and D365 10.0.41 all was working good.

Then i update D365 to last version 10.0.43 quality update. There the devTools update asked for an update of visual studio to 2022 because the last devTool need it for an installation. So i downloaded and installed VS2022. Then i used the vsix files to install devTools like i did for VS2019 before.

Update D365 by using LCS update service.

After all that actions i opened VS 2022 to begin a new project but at the first attempt to use right click of an object to use findReference i got this error.

Regards.

Was this reply helpful? Yes No
Martin Dráb 239,029 Most Valuable Professional on at

Like (3)

Report
Copy link

Link copied!

It seems you mean a cloud-hosted environment (CHE). Consider simply deploying a new one, it may be more efficient then spending hour on trying to fix the current one.

Was this reply helpful? Yes No
Awaxx 229 on at

Like (2)

Report
Copy link

Link copied!

Yes it is an CHE.
I think you are right.

1 people found this reply helpful.

Was this reply helpful? Yes No
leedyj88 4 on at

Like (1)

Report
Copy link

Link copied!

I upgraded to Visual Studio 2022, installed the Dynamics 365 Finance ad Operations DevTools from the D365 10.0.43 upgrade package, and encountered the same issue. I got everything working again by making the following change to the file C:\Users\<user account>\Documents\Visual Studio Dynamics 365\DynamicsDevConfig.xml:

The path T:\Bin\AddInExtensions doesn't even exist on my D365 cloud hosted development VM so I guess the extension used some default path where the add-ins are found. It was previously set to C:\VSAddins which does exist containing the single file Waywo.DbSchema.AddIn.dll.

Was this reply helpful? Yes No
Suggested answer

Navneeth Nagrajan 2,538 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Awaxx,

As Martin rightly said, if it is a Cloud hosted environment and if you are getting the error message Add-in factory then better to re-deploy the CHE environment.

The Dynamics 365 F&O add-on for VS 2022 is corrupted. If you try to fix up the environment by troubleshooting and fixing the D365 F&O extension, you will continue to face issues either during SSRS report development or on the D365 Application explorer components. Better to re-deploy the environment again. Ensure you backup all your work before you blow away the environment.

Was this reply helpful? Yes No