Hi David,

 

The reason for the plug-ins breaking is we have changed to a newer version
of NetReflector. Because NetReflector is strong named, it doesn't like this
change K

 

However the good news is Microsoft has already thought of this scenario:
http://msdn.microsoft.com/en-us/library/7wd6ex19(VS.80).aspx.

 

Modify your app.config (ccnet.exe.config or ccservice.exe.config) to include
the following:

  <runtime>

    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

      <dependentAssembly>

        <assemblyIdentity name="NetReflector"
publicKeyToken="2f4dd8b32acbcd8e" culture="neutral" />

        <bindingRedirect oldVersion="1.0.0.120" newVersion="1.1.2009.1004"/>

      </dependentAssembly>

    </assemblyBinding>

  </runtime>

 

Not sure of the exact version numbers - but this works on my (dev) machine.

 

Craig

 

From: [email protected] [mailto:[email protected]] On
Behalf Of Ruben Willems
Sent: Monday, 25 May 2009 6:17 p.m.
To: [email protected]
Subject: [ccnet-user] Re: CC.NET Community Plugins : dead or alive?

 

Hi

The plugins are not maintained by the CCNet devs themselves. (We even do not
have the source of them).
So your best chance is to contact the owners of them for a fix, like you
did, 
or try to get the wanted functionality in CCNet itself.



with kind regards
Ruben Willems

On Mon, May 25, 2009 at 8:04 AM, David Keaveny
<[email protected]> wrote:


Does anyone know what the status of http://ccnetplugins.codeplex.com/
<http://ccnetplugins.codeplex.com/> is? The latest 1.4.4 release candidates
of CC.NET have broken it (and most other plugins around *grin*), but they
don't appear to be in any hurry to update. I've raised an issue, and posted
a patch for an unrelated issue, and all is quiet.

Regards,
David Keaveny

--
Senior .NET Developer
Fairfax Digital
The information contained in this e-mail message and any accompanying files
is or may be confidential. If you are not the intended recipient, any use,
dissemination, reliance, forwarding, printing or copying of this e-mail or
any attached files is unauthorised. This e-mail is subject to copyright. No
part of it should be reproduced, adapted or communicated without the written
consent of the copyright owner. If you have received this e-mail in error
please advise the sender immediately by return e-mail or telephone and
delete all copies. Fairfax does not guarantee the accuracy or completeness
of any information contained in this e-mail or attached files. Internet
communications are not secure, therefore Fairfax does not accept legal
responsibility for the contents of this message or attached files.

 

Reply via email to