Update
I am using Fusion Logs to see how the assemblies bind. And this is what I get in the fusion log:
//----------------------------------------------------
*** Assembly Binder Log Entry (29-04-2015 @ 6:46:58 PM) ***
The operation failed.
Bind result: hr = 0x8013101b. No description available.
Assembly manager loaded from: C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
Running under executable C:\globalConnection\SalesChannel\sales_channel.exe
--- A detailed error log follows.
=== Pre-bind state information ===
LOG: User = vm-g4-goc\user
LOG: DisplayName = silverbyte.common.mailing, Version=1.0.0.1, Culture=neutral, PublicKeyToken=null
(Fully-specified)
LOG: Appbase = file:///C:/globalConnection/SalesChannel/
LOG: Initial PrivatePath = NULL
LOG: Dynamic Base = NULL
LOG: Cache Base = NULL
LOG: AppName = NULL
Calling assembly : (Unknown).
===
LOG: This bind starts in default load context.
LOG: Download of application configuration file was attempted from file:///C:/globalConnection/SalesChannel/sales_channel.exe.Config.
LOG: Found application configuration file (C:\globalConnection\SalesChannel\sales_channel.exe.Config).
LOG: Using application configuration file: C:\globalConnection\SalesChannel\sales_channel.exe.Config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Attempting download of new URL file:///C:/globalConnection/SalesChannel/silverbyte.common.mailing.DLL.
LOG: Assembly download was successful. Attempting setup of file: C:\globalConnection\SalesChannel\silverbyte.common.mailing.dll
LOG: Entering run-from-source setup phase.
ERR: Error extracting manifest import from file (hr = 0x8013101b).
ERR: Failed to complete setup of assembly (hr = 0x8013101b). Probing terminated.
//---------------------------------------------------
The manifest for the silverbyte.common.mailing.DLL (a .NET assembly from PB.NET) is located in the same directory. Yes the assembly manager fails to load it. Could it be that the problem is that the assembly manager is from .NET framework 2. If so, how can I make the app to use one from version 4 (the assembly is also v4) ?