Executables compiled with anycpu32bitpreferred execute on the 32-bit CLR.Executables that are compiled with the anycpu execute on the 64-bit CLR.A DLL compiled with the anycpu executes on the same CLR as the process into which it's loaded.Assemblies compiled with x86 execute on the 32-bit CLR running under WOW64.Itanium compiles your assembly to be run by the 64-bit CLR on a computer with an Itanium processor.x86 compiles your assembly to be run by the 32-bit, x86-compatible CLR.圆4 compiles your assembly to be run by the 64-bit CLR on a computer that supports the AMD64 or EM64T instruction set.ARM64 compiles your assembly to run by the 64-bit CLR on a computer that has an Advanced RISC Machine (ARM) processor that supports the A64 instruction set.ARM compiles your assembly to run on a computer that has an Advanced RISC Machine (ARM) processor.You can specify this option only for projects that target. Your application runs in 32-bit mode on systems that support both 64-bit and 32-bit applications. anycpu32bitpreferred compiles your assembly to run on any platform.Your application runs as a 64-bit process whenever possible and falls back to 32-bit when only that mode is available. anycpu (default) compiles your assembly to run on any platform. ![]() Specifies which version of the CLR can run the assembly. The OutputAssembly compiler option is required in order for an exe to be the target of a friend assembly. Use ildasm.exe to view the assembly manifest to see the associated files. netmodule will take its name from the first source code file.Īny modules produced as part of a compilation become files associated with any assembly also produced in the compilation. exe will take its name from the source code file that contains the Main method or top-level statements. Old style projects use the following rules: If you don't specify the name of the output file, MSBuild uses the name of the project to specify the name of the output assembly. Specify the full name and extension of the file you want to create. The output path specifies the folder where compiler output is placed. The OutputAssembly option specifies the name of the output file. For more information, see DocumentationFile property. To disable warnings related to documentation comments for a specific file or section of code, use #pragma warning. The DocumentationFile option applies to all files in the project. For examples, see How to use the XML documentation features. ![]() Unless you compile with, file will contain and tags specifying the name of the file containing the assembly manifest for the output file. For more information about generating code comments, see Supplying Code Comments. When the assembly is referenced in a Visual Studio project, the. xml file must be in the same directory as the assembly. xml filename must be the same as the assembly name. The source code file that contains Main or top-level statements is output first into the XML. The XML file contains the comments in the source code files of the compilation. The value specifies the path to the output XML file. To learn more about documenting your code, see Recommended Tags for Documentation Comments. The DocumentationFile option allows you to place documentation comments in an XML file. The following options control compiler output generation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |