Friday, October 27, 2006
Saturday, October 21, 2006
Wednesday, October 18, 2006
Monday, October 16, 2006
Wednesday, October 11, 2006
- Make sure Vista is configured to recognize IIS6 actions/scripts etc. This can be done by checking the appropriate boxes under the IIS part of the "Turn Windows features on or off".
- Install .NET Framework 1.1 (and updates).
- Turn the UAP off (not sure if this really is needed, but that's what I did).
- Run the installer as administrator (right click the installer, "Run as Administrator").
For me it still crashes in the beginning with that InstallDriver Module error, but after that the installer runs (read "is now running" since i'm installing right now) smoothly..
Well, the happiness of the first update was not kept alive for long. After the installation finished (which it did and that was nice) I'm now stuck at the next obstacle - When trying to access localhost all I got at first was an error message saying it couldn't read the config file and a wierd "Could not load all ISAPI filters for site". So, like every other time something goes wrong, I added Network Service and the other system roles to the website and it's content, allowing full access for ease of use. Voila, time to see the next error, and this one is regarding changes made to the handling of the actual web.config file itself. This part was a little more tricky since it's not at all that well documented..
Below is what i've done so far (and as of right now I'm not at all sure about this solution, maybe there's a best-practice way to go about all this, but since I haven't seen one yet I'll keep on trying).
- Create a system.webServer node
- Move HttpModules and HttpHandlers from system.web to system.webServer
- Rename HttpModules to modules
- Rename HttpHandlers to handlers
So far all I get is that it's missing a http handler and nothing will load, but perhaps I'll have it fixed soon..
Well, this is a situation with IIS7 having two options to run the site in: "Classic .NET Mode" or "Integrated .NET mode", the later of the two is what they recommend for IIS7 and future versions. Fine, they want us to move up, that's alright. But right now I don't care, I just want it to run. So, if you want to try and load it into the Integrated .NET mode (which I'm trying to), keep thinking and comment, otherwise you can run a command in the command promt to switch it to Classic .NET mode.
%systemroot%\system32\inetsrv\appcmd.exe set app "SITENAMEHERE/" /applicationPool:"Classic .NET AppPool"
When all else fails, admit you've probably done something stupid and save yourself the worry by simply scrapping the old installation and do a new one. Lesson learned.
Hope this will help you install it on Vista if you run across these problems as well.Take care, P.