Manage ASP.net Settings

From Hostek.com Wiki
Revision as of 02:28, 26 August 2017 by Justinm (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Managing ASP.net Settings via WCP

  1. First login to your WCP control panel for the account the domain is under: https://wcp.hostek.com

    Wcp url secure.png

    If you have any issues with logging into WCP then please see our tutorials on recovering your password if necessary


  1. Once logged into WCP if you have multiple domains you may need to select the appropriate domain to manage using the 'Hosted Domains' drop-down in the top-right of the page as shown in the screenshot below:

    Wcp change domain.png

  2. You will then click on the ASP.net Settings Icon

    Aspnet settings.png


  3. You will then be presented with a list of your domain and it's subdomains

    Aspnet configuration.png

    Click on the configuration button for the site you would like to configure.


  4. You will then be presented with a new box with multiple options to configure. Listed below are explanations of each option.

  5. Aspnet settingsbox.png

    Site Name

    • This field is self-explanatory. This will list the site name that is currently being configured

    ASP.Net Version

    Aspnet version.png

    • This field allows you to choose between 2.0/3.5 and 4.0-4.5.2 versions of ASP.Net

    Managed Pipeline

    Aspnet managedpipeline.png

    • Integrated - The IIS pipeline is integrated with the ASP.net request pipeline. The ASP.net service is no longer treated as an external plugin but as a part of IIS.

    • Classic - In this mode IIS will only interact with ISAPI filters and extensions. ASP.net acts as an ISAPI filter and is treated as an external plugin by IIS.

    File Permissions

    • This is a legacy setting for 2003 servers. This can be disregarded

    Wildcard Mapping (Required for MVC)

    Full Trust

    • Gives the asp.net application the same permissions as the user assigned to the site rather than the more limited permissions allowed by the asp.net medium trust security policy.