The following project options are specific only to ASP.NET projects.
The Project Properties dialog contains the following options.
|Configuration||Specify which Project configuration options you wish to set. Select Build or Release from the drop list provided. To change the Build target, use the Build/Set Configuration menu option.|
|Platform||Current default is AnyCPU.|
ASP.NET Project Options
Specify the name of the web site that will be used by IIS or the Development Server.
Specify what page will be opened first in the ASP.NET project
Specify which server to use when deploying from the IDE.
Specify which port to use when deploying from the IDE, or allow the system to auto-generate a port to use.
Lists all assembly references used by the active project. Use the buttons at the bottom to add new references, update existing references in the list, or simply remove a reference in the list.
When you have an ASP.Net project open, the IDE “Build” command validates the project and puts the assemblies into the ASP.NET temporary folder.
The values you enter on the new MSBuild tab of the Project Properties are valid if you want to build the project from the command line.
At a command prompt, use the following syntax:
|MSBuild <;projectfile>.aspxproj /target:Msbuild /property:ClaNetBinPath=<;Clarion.Net BIN folder>|
Specify the output folder to be used by the MSBuild command line.
Allow this precompiled site to be updatable
This option allows you to change the markup and client side functionality of the .ASPX pages.
Use Fixed Naming And Single Page Assemblies
Compile single assemblies that correspond to a single page or user control (that is to .ASPX, .ASCX, and .MASTER files). The fixed file-name option also preserves the names of your assemblies when you compile and publish your Web site. When you use fixed file names with single-page assemblies, batch compilation is turned off for precompilation. (Themes and skin files, along with other folders that do not contain pages or user controls, will continue to be compiled to a single assembly.)
When you choose to generate fixed assembly names, ASP.NET will do the following:
·Create an assembly for each .ASPX, .ASCX, and .MASTER file in the application. You should limit the number pages in your application to reduce the number of assemblies that are generated.
·Use the virtual path to the page as the name of the page's assembly. If the length of the virtual path exceeds the file-name length limit of the operating system, the tool uses a hash of the virtual path instead.
·Compile the files in top-level directories, such as the App_Code directory, into a single assembly, as is done during batch compilation.
Enable strong naming on precompiled assemblies
Specifies that your assemblies are strong named using a key file or container.
When this check box is enabled the following options are also enabled:
Use a key file generated with a Strong Name tool
The Strong Name tool (SN.EXE) is provided by Microsoft and used to create assemblies using strong names. A strong name consists of the assembly's identity'its simple text name, version number, and culture information (if provided)'plus a public key and a digital signature. Signing an assembly with a strong name ensures that a name is globally unique. Optionally check the Delay signing box to specify that only the public key is set at compile time and space is reserved in the file for the signature to be added later when the private key is known.
Use a key container
Specifies that you will use a generated key container. For more information regarding key containers, visit the following Microsoft web page:
Mark assemblies with AllowPartiallyTrustedCallersAttribute (APTCA)
Check this box to allow an assembly to reside in the GAC and at the same time be used by partially trusted code. When an assembly is marked with the APTCA attribute then the LinkDemand requiring all the callers to be full trusted is disabled.