[Run] Remove tlpimp-Microsoft.Search.Interop nuget package from the Wox project

[alekhyareddy28]

Actual behavior

• The tlbimp-Microsoft.Search.Interop nuget package is used by the Microsoft.Plugin.Indexer project. However, right now the nuget package is also being added to the Wox.csproj file because in .NET Core, the dlls are not automatically created. Rather they are only referred to in the .deps.json dependency file.

Expected behavior

The nuget package must only be added to the plugin project and not the wox project file.

[crutkas]

@saahmedm any objection for 2007 milestone for launcher?

[mykhailopylyp]

@enricogior @crutkas
It is not so trivial to delete that reference. We load plugins without their dependencies at runtime.

PowerToys/src/modules/launcher/PowerLauncher/Plugin/PluginsLoader.cs

Line 37 in dc3e645

var assembly = AssemblyLoadContext.Default.LoadFromAssemblyPath(metadata.ExecuteFilePath);

And because these dependencies are added to PowerLauncher.csproj, Launcher does not fail during runtime.

Basically, we need a solution that would load assemblies with their dependencies. Here is an example of how it can be done. They propose to load a plugin with its dependency into a separate context. So we will have some libraries loaded several times. I am not sure it can be easily accomplished with AssemblyLoadContext.Default. It seems like loading plugins with dependencies into separate contexts is required if we want to allow a user to write their own custom plugins.
Should we proceed with it?

[enricogior]

@mykhailopylyp
I think this is a very low priority and we can postpone it.

[crutkas]

@snickler didnt we do this with the .net upgrade?

[snickler]

@snickler didnt we do this with the .net upgrade?

That is correct. We did this during the NET 6 upgrade.