Problems Porting VWD 2008 Express to Windows 8 RSS

• • Reply
  

  uick383937

  Member

  81 Points

  117 Posts

  Problems Porting VWD 2008 Express to Windows 8

  Nov 18, 2012 10:02 PM|LINK

  I am setting up new Win 8 laptop.  Have added IIS8 and .Net Framework 3.5 and4.5 using "add Windows features", and downloaded and installed VWS2008 Express, since I have used this tool extensively a on prior Vista laptop and have several websites targeted to .NET2.0.  VWS2008 actually targets to .NET 3.5 which is supposedly compatible with .NET 2.0.

  When I create a new test website using VWS 2008.  It tells me that "ASP.Net 2.0 has not been registered on the web server.  You need to manually configure your web server for ASP.NET 2.0 in order for your site to run correctly"

  I did change the .NET Framework version to v.2.0.50727  in the IIS root directory, which is my account name on this computer. 

  Question: if this doesn't "register" ASP.Net 2.0 on my IIS8 web server, what does?

  So I ignore the warning, and it creates a site, but the web.config file seems grossly incompatible with the installed IIS8.

  My attempt to run the default webpage created by VWS 2008 failed, first because it detected duplicate .config sections (the parent sites not allowing overrides of things like ScriptResourceHandler). 

  After resolving these problems, it reports that it cannot find my Default.aspx file.  It can find and display a .htm file from the site.  So the issue is with ASP.Net 2.0 running under IIS8.  The error message (below) suggests that it attempted to handle the .aspx file using static file handler.  I looked at Handler Mappings in IIS Manager, and .aspx is not shown (shown are *.rules *.asmx *.svc *.xoml).  Should *.aspx be on this list?  Seems like that should be automatic, along with *.ascx , etc.  Seems kind of crazy to be manually adding a .aspx handler.

  Any advice would be GREATLY appreciated.

  Here is the error message

  ------------------------------------

  <div class="content-container">

  HTTP Error 404.3 - Not Found

  The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.

  </div> <div class="content-container">

  Most likely causes:

  • It is possible that a handler mapping is missing. By default, the static file handler processes all content.
  • The feature you are trying to use may not be installed.
  • The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should not download, such as .ASPX pages or .config files.)
  • If ASP.NET is not installed.

  </div> <div class="content-container">

  Things you can try:

  • In system.webServer/handlers:
    • Ensure that the expected handler for the current page is mapped.
    • Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool.
    • Pay extra attention to typographical errors in the expected handler line.
  • Please verify that the feature you are trying to use is installed.
  • Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe.
    1. To set a MIME type, use the following syntax: %SystemRoot%\windows\system32\inetsrv\appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string']
    2. The variable fileExtension string is the file name extension and the variable mimeType string is the file type description.
    3. For example, to add a MIME map for a file which has the extension ".xyz": appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain']
    Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them.
  • Install ASP.NET.
  • Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

  </div> <div class="content-container">

  Detailed Error Information:

  <div id="details-left">

  Module	StaticFileModule
  Notification	ExecuteRequestHandler
  Handler	StaticFile
  Error Code	0x80070032

  </div> <div id="details-right">

  Requested URL	http://localhost:80/WebSitez/default.aspx
  Physical Path	C:\inetpub\wwwroot\WebSitez\default.aspx
  Logon Method	Anonymous
  Logon User	Anonymous

  </div>

  </div>