PluginPackager in Petrel 2014 - Could not load file or assembly
I am migrating a plugin from 2013.1 to 2014. Petrel Ocean version. When I try to create a PIP file via PluginPackager.exe in 2013.1, its functions are usually executed. However, in version 2014.1, the following problem occurs:
Plug-in DID NOT PASS validation.
The path of external libraries (e.g. assemblies that are shared between plug-ins) has to be added to the probing paths defined in PluginPackager(-32).exe.config.
Could not load file or assembly 'PluginModule.dll, Version=2012.6.1.1618,Culture=neutral, PublicKeyToken=f95240d2d568401b' or one of its dependencies. The system can not find the file specified.
Source: mscorlib
Unlike what happened in version 2013.1, all indications are that executing PluginPackager.exe (2014.1) pre-checks and loads all assemblies and their references present in the output directory.
Some plugins I could carry out the transfer, but added and removed links like I was blindfolded.
Please, how can I find out the links that are missing? Is a LOG written somewhere? I want to confirm that the project is compiling normally. The error only occurs when creating a PIP file.
source to share
Coming from linux as my main development platform, I am amazed at the lack of tools provided by the .NET framework to analyze dependencies. I found links to some third party tools (Dependency Walker, .NET Reflector) and ended up finding:
http://msdn.microsoft.com/en-us/library/e74a18c4%28v=vs.90%29.aspx
I couldn't get it fuslogvw
to work (or maybe I just didn't know where to look - what is cache wininet
?), But there is a community at the bottom of the page explaining which registry setting to tweak:
IN HKLM\Software\Microsoft\Fusion\
-
EnableLog (DWORD) = 1
allows you to "register in Exclusive Text" (whatever it is) -
LogFailures (DWORD) = 1
logarithms for disk-bound failures -
ForceLog (DWORD) = 1
writes ALL bindings to disk -
LogPath (String) = C:\tmp\
defines the directory for placing the log files
After installing (1), (2) and (4), PluginPackager created log files in C: \ tmp \ that shed some light on the missing links.
source to share