T4MVCExtensions is not strong named?

May 8, 2013 at 5:52 PM
We have our website assemblies strong named at the moment, and when I added T4MVC it threw an error because that assembly is not strong named.

I will just turn off strong naming for the time being; the only reason we added it was when we were playing around with ngen for our website, but that never quite worked out anyway (site was no faster at startup). But, if someone does need a strong named website for some reason (maybe ngen works for them) the official assembly needs to be strong named.
Coordinator
May 8, 2013 at 5:55 PM
Actually it is strong named starting with 3.5. Are you using an earlier version?
May 8, 2013 at 7:33 PM
I got the latest from NuGet which looks to be 3.6.2?

<?xml version="1.0" encoding="utf-8"?>
<packages>
<package id="T4MVC" version="3.6.2" targetFramework="net40" />
<package id="T4MVCExtensions" version="3.6.2" targetFramework="net40" />
</packages>

But, when I look at the version of the assembly it is using, it is 3.0.0.0? And it is clearly not signed:

sn -Tp T4MVCExtensions.dll

Microsoft (R) .NET Framework Strong Name Utility Version 4.0.30319.17929
Copyright (c) Microsoft Corporation. All rights reserved.

T4MVCExtensions.dll does not represent a strongly named assembly
Coordinator
May 8, 2013 at 7:52 PM
Oops, looks like I messed up the signing in latest build. I just published 3.6.3. Can you try with that? Thanks!
May 8, 2013 at 8:22 PM
Will do, thanks!