Is there any difference between Interop.AZROLESLib and Microsoft.Interop.Security.AzRoles? -


microsoft provide microsoft.interop.security.azroles interop library in server 2003 azman (authorization manager). built under .net 1.0.

can tell me if there's difference between , creating reference "azroles 1.0 types library" (c:\windows\system32\azroles.dll) ends interop.azroleslib? apart namespace? , fact created under current version of .net?

the main purpose of commonly-provided interop dll (such microsoft.interop.security.azroles) make sure type identifiers match when 2 independently-produced assemblies need pass references underlying types each other. in other words, if assemblya.dll needs provide collection of objects of type icominterface (from comcomponent.dll) public property, , assemblyb.exe needs to, in turn, pass 1 or more of objects comcomponent.dll, need common interop dll. that's microsoft.interop.security.azroles.dll for. when add reference project azroles.dll, visual studio build new interop.azroles.dll assembly has identifiers unique assembly.

bottom line might not care passing these references around, there's not point in creating own interop dll (even if automatic) when there 1 made you. use microsoft.interop.security.azroles assembly). also, while don't see evidence of this assembly, interop assembly could, in theory, provide additional adapter-like functions make managed-unmanaged interop work better.


Comments

Popular posts from this blog

unicode - Are email addresses allowed to contain non-alphanumeric characters? -

C#: Application without a window or taskbar item (background app) that can still use Console.WriteLine() -

c++ - Convert big endian to little endian when reading from a binary file -