.NET Framework: Difference between revisions

Revision as of 22:03, 19 February 2024

Revision as of 20:20, 15 March 2024

Line 65:

Compiled CIL code is stored in [[assembly (CLI)|CLI assemblies]]. As mandated by the specification, assemblies are stored in [[Portable Executable]] (PE) file format, common on Windows platform for all ''[[dynamic-link library]]'' (DLL) and ''executable'' [[EXE]] files. Each assembly consists of one or more files, one of which must contain a manifest bearing the [[metadata]] for the assembly. The complete name of an assembly (not to be confused with the file name on disk) contains its simple text name, version number, culture, and [[public key]] token. Assemblies are considered equivalent if they share the same complete name.

A private key can also be used by the creator of the assembly for [[strong name|strong naming]]. The public key token determines the real-world identity of the assembly's signer. Only whothose knowsknowing their private key (of the double-key cryptography system) can sign assemblies that have the same strong name as a prior version assembly. Strong naming is required to add assemblies to [[Global Assembly Cache]].

Starting with Visual Studio 2015, .NET Native compilation technology allows for the compilation of .NET code of [[Universal Windows Platform apps]] directly to machine code rather than CIL code, but the app must be written in either C# or Visual Basic.NET.<ref>{{cite web|url=https://docs.microsoft.com/en-us/dotnet/framework/net-native/|title=Compiling Apps with .NET Native|last=rpetrusha|website=Microsoft Learn|access-date=December 2, 2017|archive-date=December 3, 2017|archive-url=https://web.archive.org/web/20171203082710/https://docs.microsoft.com/en-us/dotnet/framework/net-native/|url-status=live}}</ref>