This project is read-only.

T4MVC Extensions and Strong Named Assemblies

Feb 8, 2013 at 8:32 PM
I'm signing my assemblies that are referencing T4MVCExtensions.dll and it's giving me grief because the T4MVCExtensions.dll isn't strongly named it self. Can the dll please be signed so it doesn't prevent projects that reference it from being signed?
Feb 8, 2013 at 8:46 PM
Yes, we should do that. I'm going through the same thing with WebActivator though for T4MVC I think we could just change it without using a new package name. I doubt that would break too many people.
Feb 8, 2013 at 9:18 PM
I would be very grateful if you do this.

Thank you.
Feb 8, 2013 at 11:28 PM
Ok, the change is in T4MVC 3.5. Can you please give it a try and check that everything looks good? Thanks!
Feb 9, 2013 at 12:20 AM
I downloaded the new package and I was able to sign the assemblies consuming it.

Thanks for your help, you made my day.
Feb 9, 2013 at 12:21 AM
Awesome! :)