Reply to thread

Message

<blockquote data-quote="armandp" data-source="post: 1082826" data-attributes="member: 71896">it's caused by a version mismatch of referenced assembly WebSocket4Net.dll.Add this to your MediaPortal.exe.config and Configuration.exe.config while i sort this out:&lt;dependentAssembly&gt;&nbsp;&nbsp; &lt;assemblyIdentityname=&quot;WebSocket4Net&quot;publicKeyToken=&quot;eb4e154b696bf72a&quot;culture=&quot;neutral&quot; /&gt;&nbsp;&nbsp; &lt;bindingRedirectoldVersion=&quot;0.0.0.0-0.9.0.0&quot; newVersion=&quot;0.9.0.0&quot; /&gt;&lt;/dependentAssembly&gt;Within the assemblyBinding tag.Another option is to replace the WebSocket4Net.dll in the MediaPortal directory with the previous version (0.8.0.0) that is included in the older version of the plugin.(i'm sorry.. this isn't really an issue with the plugin.. it's a .NET thing unfortunately)</blockquote>

[QUOTE="armandp, post: 1082826, member: 71896"] it's caused by a version mismatch of referenced assembly WebSocket4Net.dll. Add this to your [B]MediaPortal.exe.config[/B] and [B]Configuration.exe.config [/B]while i sort this out: <dependentAssembly> <assemblyIdentityname="WebSocket4Net"publicKeyToken="eb4e154b696bf72a"culture="neutral" /> <bindingRedirectoldVersion="0.0.0.0-0.9.0.0" newVersion="0.9.0.0" /> </dependentAssembly> Within the [B]assemblyBinding [/B]tag[B]. [/B] Another option is to replace the WebSocket4Net.dll in the MediaPortal directory with the previous version (0.8.0.0) that is included in the older version of the plugin. (i'm sorry.. this isn't really an issue with the plugin.. it's a .NET thing unfortunately) [/QUOTE]

Verification