Strong Naming on Compact Framework Development strategy?

[Joe]

I have developed an application on the .Net Framework (I mean the full
framework, not the Compact Framework), and used strong naming delayed
signing for my day to day build/test cycles. In other words, I
specifed AssemblyKeyFile and DelaySigning(True) in assemblyinfo.cs. I
did not do a "sn -Vr" on every build.

I am now developing an equivalent Compact Framework application
(reusing all of the non-UI code), and trying to use roughly the same
day to day development process.

Along the way, I was careful to only use CF supported functionality.

Is there an equivalent to "sn -Vr" on the compact framework? How can
I tell the CF to ignore partially signed assemblies?

Should I not use strong naming with the CF? I would prefer to use it
if at all possible, but I dont want to fully sign my assemblies on
every build.

I am using both the emulator (most of the time), and sometimes an iPAQ
1945 (running Windows Mobile 2003).

Thanks for any help,

Joe

 

[Peter Foot [MVP]]

..NETCF doesn't support delay signing, so its all or nothing when you build
the assembly I'm afraid.

Peter

--
Peter Foot
Windows Embedded MVP
www.inthehand.com | www.opennetcf.org

Do have an opinion on the effectiveness of Microsoft Windows Mobile and
Embedded newsgroups? Let us know!
https://www.windowsembeddedeval.com/community/newsgroups

 

[Joe]

OK, so I take this to mean that I must fully sign the assembly, or not
sign it at all. There is no way to put something in the registry to
ignore partially signed assemblies?

Thank you so much for your answers,

Joe