-
Posted to
IIS7 - Setup
by
John Happy
on
09-11-2008, 2:18 PM
Tried using procmon ... first time user of this tool. I could not pick out the activity of the command window and the appcmd application from amongst the other activity going on at the same time.
My gut feeling is that upgrading from Windows Server 2003 to Windows Server 2008 by simply inserting my 2008 disc and answering the upgrade prompt ...
-
Posted to
IIS7 - Setup
by
John Happy
on
09-10-2008, 3:40 PM
I am running a web server recently upgraded from Windows Server 2003 to Windows Server 2008. All my virtual server's (websites) are now working, but only using the Classic pipeline. I can't serve web pages using the Integrated pipeline. In order to take advantage of IIS 7.0's Integrated pipeline I was told that I should ...
-
Posted to
IIS 7 - ASP.NET Administration
by
John Happy
on
09-10-2008, 11:37 AM
Answers to my questions, above, appear to be addressed on the following web page:
http://technet.microsoft.com/en-us/mscomops/cc424869.aspx
-
Posted to
IIS 7 - ASP.NET Administration
by
John Happy
on
09-08-2008, 3:40 PM
My goal is to be able to choose between classic and integrated - and to continue to use FrontPage Extensions via SharePoint - to basically have everything I had when I ran my sites under IIS6 and whatever new stuff IIS 7 offered.
Apparantly, the place to uninstall IIS, is the Server Manager. I see that the Web Server (IIS) role can be ...
-
Posted to
IIS 7 - ASP.NET Administration
by
John Happy
on
09-08-2008, 2:40 PM
I had found the article called 'ASP.NET 2.0 Breaking Changes on IIS 7.0' which described using an executable named APPCMD to help migrate ASP.NET 2.0 apps to IIS 7.0. I'm trying to follow some of the instructions in the article but nothing I've done so far has helped.
Host headers distinguish one website from another on my web ...
-
Posted to
IIS 7 - ASP.NET Administration
by
John Happy
on
09-08-2008, 11:37 AM
Recently upgraded my web server from Windows Server 2003 to Windows Server 2008 and discovered that most of my aspx pages were broken. The only way, thusfar, I've found to fix the problem is to either set up a website in the Classic .NET AppPool or set up the website in its own App Pool and make sure the Managed ...
-
Posted to
IIS7 - Extensibility
by
John Happy
on
09-07-2008, 7:05 PM
I fixed my problem ...
I discovered that, although .aspx files were shown as 'enabled' under IIS Handler Mappings, the mapping for my troublesome website's .aspx pages pointed to the Framework v1.1.4322 rather than what I wanted which was v2.0.50727. I deleted the mapping pointed to the dll for v1 and created a custom ...
-
Posted to
IIS7 - Extensibility
by
John Happy
on
09-06-2008, 8:06 PM
File/Folder permissions appear to be correct, when compared to the website folder and file that is working. My Server Manager states that the Web Server role service is installed and found under that role service is Application Development and found under that heading ASP.NET is installed as well as .NET Extensibility, ASP, CGI, ISAPI Extensions ...
-
Posted to
IIS7 - Extensibility
by
John Happy
on
09-06-2008, 3:08 PM
Recently upgraded from Windows Server 2003 to Windows Server 2008. I develop my sites using VS2005. Microsoft SharePoint (FrontPage extensions) is installed.
My mystery is that the same web page (test.aspx), which has some text and and a few asp.net controls, opens up correctly in IE7 within one website but not within another. I get the following ...