Interops and Strong Names
-
Does anyone out ther know how to work around the problem that Interops (Office one for sure) cannot be included in assemblies that are strong named?
-
Does anyone out ther know how to work around the problem that Interops (Office one for sure) cannot be included in assemblies that are strong named?
If the product includes a Primary Interop Assembly (PIA) those should be strongly named already. Office has Primary Interop Assemblies available, check the general MSDN downloads section for them. If you are generating your interop assembly using VS.NET; in the project properties you will find a setting which lets you specify a keyfile to use for the generated interop assembly. Unfortunately this feature isn't available in VB.NET, so you'll have to resort to using the command line tools
aximpandtlbimp(refer to MSDN for their usage). HTH, James "then when you go to bed...wait, you dont do that do you....ok....when you plug into the 'hive mind' to charge yourself, ill hack into your head" Nnamdi Onyeyiri over MSN -
If the product includes a Primary Interop Assembly (PIA) those should be strongly named already. Office has Primary Interop Assemblies available, check the general MSDN downloads section for them. If you are generating your interop assembly using VS.NET; in the project properties you will find a setting which lets you specify a keyfile to use for the generated interop assembly. Unfortunately this feature isn't available in VB.NET, so you'll have to resort to using the command line tools
aximpandtlbimp(refer to MSDN for their usage). HTH, James "then when you go to bed...wait, you dont do that do you....ok....when you plug into the 'hive mind' to charge yourself, ill hack into your head" Nnamdi Onyeyiri over MSNThank you sir... It would have been much easier if MS read the AssemblyInfo file for the project (but maybe is in the next release)