locked
Indispensable? IIS7 original "Default Web Site" RRS feed

  • Question

  • As the result of that I could not change the state of the original "Default Web Site" from 'stopped' to 'started', I replaced it under the steps below, on PS IIS> command console:
    1. Create new web site
    2. Move 2 files, iisstart.htm and image file, to temp directory.
    3. Removed original 'Default Web Site' from virtual directory and remaining contents in physical directory inetpub\wwwroot.
    4. Renamed new web site as "Default Web Site, and moved back 2 files from temp to inetpub\wwwroot directory.
    5. IIS7 seems working well, 'http://localhost/' display IIS image as mentioned in ASP.NET 3.5 StepByStep book. It was happy to me.
    6. However, new problem came out on the Visual Studio 2008.
    7. An error message come out
                 " Unable to create the Web site
                   'http://localhost/ASPNETStepbyStep/NewWebSite' The Web server
                   'http://localhost/' could not be found                                            "
         under  "New", "Web site", "HTTP", C#
    Is there any relation between my action and the sabotage of Visual Studio??
    Then, I tryed to have a look the condition of the new "Default Web Site". and list the objects as below;
     
     PS IIS:\sites> gi 'Default Web Site' | select *

    PSPath                     : WebAdministration\WebAdministration::\\NORTH02\sites\Default Web Site
    PSParentPath               : WebAdministration\WebAdministration::\\NORTH02\Sites
    PSChildName                : Default Web Site
    PSDrive                    : IIS
    PSProvider                 : WebAdministration\WebAdministration
    PSIsContainer              : True
    name                       : Default Web Site
    id                         : 1
    serverAutoStart            : True
    state                      : Started
    bindings                   : Microsoft.IIs.PowerShell.Framework.ConfigurationElement
    limits                     : Microsoft.IIs.PowerShell.Framework.ConfigurationElement
    logFile                    : Microsoft.IIs.PowerShell.Framework.ConfigurationElement
    traceFailedRequestsLogging : Microsoft.IIs.PowerShell.Framework.ConfigurationElement
    applicationDefaults        : Microsoft.IIs.PowerShell.Framework.ConfigurationElement
    virtualDirectoryDefaults   : Microsoft.IIs.PowerShell.Framework.ConfigurationElement
    ftpServer                  : Microsoft.IIs.PowerShell.Framework.ConfigurationElement
    advancedLogging            : Microsoft.IIs.PowerShell.Framework.ConfigurationElement
    Collection                 : {application}
    applicationPool            : DefaultAppPool
    enabledProtocols           : http
    physicalPath               : C:\Inetpub\wwwroot
    userName                   :
    password                   :
    ItemXPath                  : /system.applicationHost/sites/site[@name='Default Web Site' and @id='1']
    Attributes                 : {name, id, serverAutoStart, state}
    ChildElements              : {bindings, limits, logFile, traceFailedRequestsLogging...}
    ElementTagName             : site
    Methods                    : {Start, Stop}
    Schema                     : Microsoft.IIs.PowerShell.Framework.ConfigurationElementSchema

    I compared the detail with a sample listed in the "PowerShell Snap-In: Navigating the IIS Snap-in Namespace".
    Sample one use "IIsProviderSnapIn\WebAdministration"  instead of "WebAdministration\WebAdministration"
                            "Microsoft.Web.Administration.ConfigurationElement" instead of "Microsoft.IIs.PowerShell.Framework.ConfigurationElement"
    All the same for other objects.

    My goal is recovery of the function of Visual Studio, Looking forward to the pleasure of hearing good solution.

    Wednesday, April 1, 2009 7:18 AM

Answers

All replies