Defining Compile Options for a File System or SlxJobService target portal

By default, ASP.NET Web pages and code files are compiled dynamically when you request a resource, such as a page, from the website. After the pages and code files are compiled for the first time, the compiled resources are cached to ensure that the subsequent requests to the same page are efficient.

Note: Basic pre-compile options are enabled by default, however, you can use advanced compile options that allow explicit control over available pre-compilation options.

To define compile options:

  1. Select Manage Deployments from the Developer Tools menu. The Deployment Manager window is displayed.
  2. Expand the Deployments tree view and select a File System or SlxJobService target portal.
  3. Select the Precompile check box in the Portal Settings section.
  4. Click Compile Options. The Compile Options window is displayed.
  5. Select the Use In-Place Compilation check box, if required.
    Note: The Use In-Place Compilation option performs the same compilation that occurs when you request pages from a Web site; all ASP.NET file types are compiled (this excludes HTML files, graphics, and other non-ASP.NET static files).
  6. Specify this information:
    Strong Name
    Select the required option and specify a name in the below field. For more information on strong name assemblies, see MSDN Online Help.

    Possible values

    • Key Container: A cryptographic key container. For example: /keycontainer:string
    • Key File: A cryptographic key. For example: /keyfile:file
    Compiler Flags
    The available compile options. Possible values:
    • Overwrite Target: Overwrites the existing target directory. The existing content is deleted.
    • ForceDebug: Includes debug information in the compiled application. Overrides the settings defined in the source configuration files. Otherwise, no output is captured.
      Note: You cannot use the -d option for in-place compilation, as in-place compilation honors configuration settings for debugging options.
    • Clean: Indicates the precompiled application is built clean. The previous compiled components are recompiled again.
    • CodeAnalysis: Performs quick desktop error detection on small code bases. You can view the results in the log, make fixes, and run the CodeAnalysis again.
    • AllowPartiallyTrustedCallers: Enables partially trusted callers to access an assembly. Must be applied to the strongly named assembly that Aspnet_compiler.exe generates.
      Note: This option must be combined with the -keyfile or -keycontainer option.
    • DelaySign: Specifies that the AssemblyDelaySignAttribute, which indicates that an assembly must be signed only with the public key token rather than with the public.private key pair, must be applied to the generated assembly.
      Note: This option must be combined with the -keyfile or -keycontainer option.
    • FixedNames: Specifies that only one assembly must be generated for each page in the application. Each assembly is named with the virtual path of the original page unless the name exceeds the operating system limit for file names.
      Note: You cannot use the FixedNames option for in-place compilation.
  7. Click OK.