[BUG] Plugins showing installed when not

[tdashworth]

Describe the bug
Our plugin "CDS Data Migrator" is showing as installed enough though it's not. When I try to install it, it doesn't (the NugetPlugins folder is updated but that's all).

To Reproduce
Do a clean install of XrmToolBox. See the plugin is showing as installed. Notice that when installing, it doesn't change things

Expected behavior
Install to work.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• XrmToolbox Version 1.2023.1.63
• Tool version 2.0.0 onwards

Additional context
Add any other context about the problem here.

[tdashworth]

Capgemini/xrm-datamigration-xrmtoolbox#90

[MscrmTools]

The issue in your repository seems to indicates the issue is with the legacy tools library.
The new tool library should handle this better. The issue was due to version comparison between file version on 4 numbers and Nuget package version on 3 numbers (semantic)
Please tell me if new tool library works better or not

[tdashworth]

Thanks for the quick response!

I'll take a look tomorrow.

What do you mean by "file version"?

[MscrmTools]

Right click on tool assembly -> properties.
You can see the version in the details tab

[tdashworth]

Ah, yes, we use GitVersion so the "Assembly File Version" and "Nuget Version" are different formats. Should these match? e.g. 2.0.5.0 for both?

[tdashworth]

FYI, the new tool library (LOVE IT) doesn't improve things... While it lists the previous versions, the same behaviour occurs (claims it's installed but silently fails to install).

[MscrmTools]

Ok, I will debug this tomorrow and let you know my findings

[MscrmTools]

I can see you released an update to your tool and I don't reproduce the issue:

CDS Data migrator is not installed and displayed as installable

[tdashworth]

Hi,

Things are looking good for me too.

What might have changed apart from releasing a new version? We upgraded our visual studio solutions to the vs17 style - could that have caused it? (v2.0.4 reverted that change)