Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. System Admin
  4. IIS not processing ASP.NET under Windows XP Professional

IIS not processing ASP.NET under Windows XP Professional

Scheduled Pinned Locked Moved System Admin
csharpasp-netvisual-studiosysadminwindows-admin
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    C Offline
    Chris Hansson
    wrote on last edited by
    #1

    Up until about 10 days ago, I'd been using Windows 2000 Professional as my development system, and everything was just fine. As my HD was dying rapidly I just bit the bullet, and got a new drive, new CPU, etc, including getting a copy of XP Professional. I did NOT do an upgrade, but a brand new install, and had IIS selected for install as well. Installed Visual Studio 7 Enterprise Developer Edition just fine as well. No errors, no warnings. Ok, now come the fun part.. IIS is NOT rendering ANY of my ASP.NET components when I make an ASP.NET application. No buttons displayed, no Textforms, NOTHING, except labels. I can take the exact same code and put it on my production W2K Server, and IIS there handles it all just fine. However I don't fancy using my production box for hosting development stage code. Has ANYONE run into this irritating problem? And if so, has anyone a solution. I am rather close to doing a fresh install of Windows 2000 Professional, but then I would have thrown away the $200 I paid for XP Professional, and that irks me. Thanks /CMH (who is really :mad: :mad: :mad: :mad: right now)

    P 1 Reply Last reply
    0
    • C Chris Hansson

      Up until about 10 days ago, I'd been using Windows 2000 Professional as my development system, and everything was just fine. As my HD was dying rapidly I just bit the bullet, and got a new drive, new CPU, etc, including getting a copy of XP Professional. I did NOT do an upgrade, but a brand new install, and had IIS selected for install as well. Installed Visual Studio 7 Enterprise Developer Edition just fine as well. No errors, no warnings. Ok, now come the fun part.. IIS is NOT rendering ANY of my ASP.NET components when I make an ASP.NET application. No buttons displayed, no Textforms, NOTHING, except labels. I can take the exact same code and put it on my production W2K Server, and IIS there handles it all just fine. However I don't fancy using my production box for hosting development stage code. Has ANYONE run into this irritating problem? And if so, has anyone a solution. I am rather close to doing a fresh install of Windows 2000 Professional, but then I would have thrown away the $200 I paid for XP Professional, and that irks me. Thanks /CMH (who is really :mad: :mad: :mad: :mad: right now)

      P Offline
      P Offline
      Paul Watson
      wrote on last edited by
      #2

      Chris Hansson wrote: Has ANYONE run into this irritating problem? And if so, has anyone a solution. I am rather close to doing a fresh install of Windows 2000 Professional, but then I would have thrown away the $200 I paid for XP Professional, and that irks me. It is not just WXP, I use WXP and ASP.NET works just fine. What does happen though (and it happens on W2K as well) is that the file associations in IIS for ASP.NET disapear. I have not found the cause, but it has happened to me once before. To check go into IIS and then: Right Click the Default Web, select Properties. Then click the Home Directory tab and click the Configuration button. Now in the list displayed in front of you look for the ASPX file. If it is not there or the Executable Path does not point to aspnet_isapi.dll then you need to run the following command which re-associates ASP.NET files in IIS. C:\WINNT\Microsoft.NET\Framework\v1.0.3705\aspnet_regiis.exe -i Obviously replace WINNT with whatever your Windows path is. Hope that helps :)

      Paul Watson
      Bluegrass
      Cape Town, South Africa

      Ray Cassick wrote:
      Well I am not female, not gay and I am not Paul Watson

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups