What are the limitations of using Unmanaged Code from within a .NET assembly?

Q

Managed Code and Unmanaged Code related ASP.NET- What are the limitations of using Unmanaged Code from within a .NET assembly?

✍: Guest

A

Performance : Although native-code DLLs can perform some operations more quickly than equivalent code managed by the CLR, these benefits might be offset by the time it takes to marshal the data to pass between the unmanaged procedure and the .NET assembly.

Type safety : Unlike .NET assemblies, unmanaged procedures might not be type-safe. This can affect the reliability of your .NET application. In general, reliability is a paramount concern with ASP.NET Web applications.

Code security : Unmanaged procedures do not use the .NET Framework’s model for code security. Versioning:Unmanaged code does not support .NET versioning; therefore, assemblies that call unmanaged procedures might lose the benefit of being able to coexist with other versions of the same assembly.

2009-04-07, 4848👍, 0💬