Julian Verdurmen
Julian Verdurmen
yes we need to port the page http://npe.codeplex.com/wikipage?title=How%20to%20write%20a%20plugin%20for%20NuGet%20Package%20Explorer indeed. I think it still works, could you test that?
thx for the feedback. Currently NuGetPackageExplorer.Types isn't maintained (jumped here in without the info). Have to look at that.
this seems the same prob. https://github.com/NuGetPackageExplorer/NuGetPackageExplorer/issues/160
[NuGetPackageExplorer.Types.5.0-alpha1.nupkg.zip](https://github.com/NuGetPackageExplorer/NuGetPackageExplorer/files/974774/NuGetPackageExplorer.Types.5.0-alpha1.nupkg.zip) could you please try with the attached one?
Sure no problem!
> Sorry. Maybe a binding redirect can help? Yes, please try. I will check the assembly version numbers. > Unfortunately VS2017.1 doesn't let me add a local package source anymore,...
FYI this is the project graph  the attached nupkg was built with: (assembly version, not file version) types: 3.21 (strong named) core: 3.22 (not strong named) packageexplorer: 3.22 (not...
this could be the issue: (in packageexplorer) (app.config) ``` ``` please try to change it to ``` ``` mine is located at "C:\Program Files\WindowsApps\50582LuanNguyen.NuGetPackageExplorer_3.21.6.0_neutral__w6y2tyx5bpzwa\win32" See  you need to restart...
great news! PR would be great, but I'm not sure what is the best fix: 1. remove strong name of types (probably bad idea) 2. make the assembly of types...
> If we want to do right, we should also keep NuGet package version reflecting the dll version. To not break anything (4.0 is already public, 5.0-alpha in codebase) we...