Hi @juileetikekar ,

The update to dotnet 8 is making all plugins not to work because the path definition in the config file that load them is wrong. See the image below.

You need to refactor the paths to ....net8.0-windows.... for packageExplorer to be able to load the plugins.

In my oppinion, two config files are affected and their path are

src\AasxPackageExplorer\options-debug.json
src\AasxPackageExplorer\options-debug.MIHO.json

with the latter taking precedence.

Hi @Kaz040,

that is strange, when I downloaded the AASPE (https://github.com/eclipse-aaspe/package-explorer/actions/runs/13583846578) on my end, the plugins work fine:

I will have a look.

Nice that there is a test release. Maybe the release action overwrite those paths....

I actually used my forked repo which I synced with upstream repo.

If everything is working with released package, there might not be a need to mess with main repo. You can take your time to look at it and decide if refactor is necessary.

Hi @Kaz040,

Although I could not reproduce the issue. I have refactored the files to remove the inconsistency. Could you please test the plugins on your end?

Thanks in advance.

@juileetikekar, Thank you for your work and quick response. I will test the repo now.

I looked at the release also, it is working fine for plugins because the program now points to release path and not debug path.

Another thing that I noticed in the release is that, Project AasxPluginAssetInterfaceDesc.csproj is not part of the projects that is compiled in the release(see image below) so it functionality is missing in the release.

I think this issue can be resolved by adding AasxPluginAssetInterfaceDesc to BuildForRelease.ps1 file (from line 40 - 57).

Please could you add this project and rerun the Action that compile the release.

Thank you so much for work and prompt response.

Hi @Kaz040,

Although I could not reproduce the issue. I have refactored the files to remove the inconsistency. Could you please test the plugins on your end?

Thanks in advance.

After testing the repo this morning. The plugins are loaded as expected. Thank you.

@juileetikekar, Thank you for your work and quick response. I will test the repo now.

I looked at the release also, it is working fine for plugins because the program now points to release path and not debug path.

Another thing that I noticed in the release is that, Project AasxPluginAssetInterfaceDesc.csproj is not part of the projects that is compiled in the release(see image below) so it functionality is missing in the release.

I think this issue can be resolved by adding AasxPluginAssetInterfaceDesc to BuildForRelease.ps1 file (from line 40 - 57).

Please could you add this project and rerun the Action that compile the release.

Thank you so much for work and prompt response.

The issue with AasxPluginAssetInterfaceDesc not being part of release, is still there, right?

Also, do you see this plugin as a part of Blazor explorer?

@juileetikekar, Thank you for your work and quick response. I will test the repo now.
I looked at the release also, it is working fine for plugins because the program now points to release path and not debug path.
Another thing that I noticed in the release is that, Project AasxPluginAssetInterfaceDesc.csproj is not part of the projects that is compiled in the release(see image below) so it functionality is missing in the release.

I think this issue can be resolved by adding AasxPluginAssetInterfaceDesc to BuildForRelease.ps1 file (from line 40 - 57).
Please could you add this project and rerun the Action that compile the release.
Thank you so much for work and prompt response.

The issue with AasxPluginAssetInterfaceDesc not being part of release, is still there, right?

Also, do you see this plugin as a part of Blazor explorer?

Hi @juileetikekar , Yes the plugin is still missing. Unfortunately, the job was half way done. I looked into the Action that run the Check-release job(see image below).

The Build for release job ran successfully (see image below)
.

But however, the Package job ran without copying the directory of AasxPluginAssetInterfaceDesc project into the package. Looking into the package job, I saw that it is using this script https://github.com/eclipse-aaspe/package-explorer/blob/main/src/PackageRelease.ps1.

To complete the task, I think AasxPluginAssetInterfaceDesc need to be added to the PackageRelease.ps1 (inside $smallPlugins -->from line 33 and $blazorPlugins --> from line 51 variables ). see image below.

Yes, I noticed that too. I will add the project to both the packageExplore (windows) as well as Blazor Explorer (web), if the plugin supports both.

done

done

I just made a quick test on the release. It is working as expected. Thank you for the support!!!