Tuesday, July 10, 2012 5:08 PM
I strongly named a third party assembly with .Net 4.x. My VS project is using 3.5 and cannot be upgraded. How do I strongly name the third party assemblies with .Net 3.5? I pulled down the 3.5 SDK, but Ilasm.exe is not included. Is there a way to target 3.5, ith Ilasm 4.0?
Thursday, July 12, 2012 5:49 AMModerator
Welcome to the MSDN Forum.
So far there is no way to achieve this goal.
You can ask for the 3.5 version third party DLL or upgrade your project to 4.0.
MSDN Community Support | Feedback to us
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Tuesday, July 17, 2012 4:58 AMModerator
ilasm.exe is part of .NET Framework redist itself, not part of its SDK:
%WINDIR%\Microsoft.NET\Framework\v2.0.50727\ilasm.exe (2.0, 3.0 or 3.5 version as .NET 3.x versions are in-place updates of CLR where ilasm lives)
Wednesday, August 01, 2012 9:56 PM
Thanks for the reply. I pretty much figured out what you described, over time. I forgot check up on the forum. In the end I dumped the Strong Name stuff and reverted back to .Net 2.x versions of the dlls. It seems most developement systems work best when one develops new code in the current version. Upgrades are always an issue. We have the same problem with our applications. But it keeps us busy.