Consider adding a strong name to DLLs.

[loicmorvan]

I and my company use ATF for our little product.

Our product will soon be released and we want to add a strong name to - or sign - our executables and libraries to "secure" things.
As you should know, when an assembly is signed, all the assemblies it depends on must also be signed.

So, can you consider adding a strong name to - or signing - the generated DLLs of ATF?

Thanks a lot!

[ansjesnault]

Hello,

We have same issue...
We signed ATF 3rdPaty dlls (removing friend assemblies dependencies and signing ATF dlls directly from the provided .sln file) in order to signed our own dlls.
But at runtime, we got a xaml exception while InitializeComponent() of our custom control which reference a local other UserControl class (all in our self Views project).

All works well without ATF dlls signed.
Do you have any idea of the problem ?

See complete log attached.
ErrorLog.txt

It seems that our Views assembly is loaded but somewhere in runtime, no PublicKeyToken is found for that assembly, whereas we signed it and we checked it with the sn tool...

Then we tryied to not sign our Views.dll and we got also exception where the last inner exception come from somewhere in Sce.Atf.Resources when trying to do System.Reflection.RuntimeAssembly.GetExportedTypes()...

Any clues would be nice.

Thanks.

[abeckus]

Hello,
Thanks for using ATF.
Since ATF is open source, we expect user to sign assemblies with a strong name if desired when building ATF.
Currently ATF is in feature freeze mode. Only major bugs will be fixed.

Alan