Cruise Control 1.4.4 and Fortress 1.1.4

[chris.bradley]

Hey guys, I tried to upgrade Cruise Control to version 1.4.4 and can't get it working. It looks like Cruise Control 1.4.4 has a reference to an assembly called NetReflector 1.1.2009.1004 but the Fortress Plugin for Cruise Control has a reference to NetReflector 1.0.0.120.

I tried messing around with the cruise control app.config to do an assembly redirect but it looks like maybe the public key token changes on that assembly and I couldn't make it work.

Is this something where we just need to have the fortress cruise control plugin recompiled for the latest assemblies in Cruise Control?

Thanks

[chris.bradley]

I think I spoke too soon on this. It looks like the problem is with the latest version of Cruise Control. They changed the signing information on that NetReflector.dll because they lost the key. It looks like they're working to find the old signing info so this doesn't become a major issue.

I've gone back to Cruise Control 1.4.3 and it's working fine.

[shannon]

Is this the modification you tried?

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>

[chris.bradley]

Yes, that's what I tried. The problem is because they changed the AssemblyKeyFile the public key token on the DLL has changed. You can't perform an assembly redirect if the public key token changes.

[shannon]

Yeah, I think it best to wait til they figure it out and just use 1.4.3 for now. That config block actually came from them and they seem to think it works

Thanks for the update!

[shannon]

Just an update here...CC.Net 1.4.4SP1 is now available and should have the old public key token.