JoeAudette.com

I spent most of the day yesterday backing up my main development machine and then upgrading to Windows Vista and reinstalling all of my development tools. I'm finally setup to continue working on mojoPortal under Vista. After many years of working under XP, its nice to have a shiny new interface.

There were a few things I encountered while setting up the web app under IIS7 that are worth keeping in mind.. You don't actually need IIS because you can use the VS Web server but I like to setup IIS and make sure things work as expected.

The first thing to know is that you need to make sure you install the IIS Metabase and IIS 6 configuration compatibility as noted in this helpful blog post.  I'm still learning where they moved my cheese but I found the IIS Management tools by right clicking My Computer and choosing Manage. You could get there that way in XP as well but it was more common to go to Administrative Tools > Internet Information Server.. under XP or Win 2003 Server.

Instead of adding a Virtual Directory, you right click and choose Add Application to setup a Virtual Directory configured for ASP.NET.

I also had to give permission because it couldn't read the Web.config file. So I gave permission to the aspnet user and the IIS_WPG account

Then I got an error about the configuration:

Server Error in Application "Default Web Site/mojo"
HTTP Error 500.0 - Internal Server Error

Description: This application is running in an application pool that uses the Integrated .NET mode. This is the preferred mode for running ASP.NET applications on the current and future version of IIS.

In this mode, the application should not specify ASP.NET module components in the <system.web>/<httpModules> configuration section. Instead, it should use the <system.webServer>/<modules> configuration section to load ASP.NET module components. You have the following options:
1) Migrate the application to work with the Integrated .NET mode (PREFERRED).
You can migrate the application configuration, including the contents of the <httpModules> configuration section, by using the following from a command line window (the window must be running as Administrator):

%systemroot%\system32\inetsrv\APPCMD.EXE migrate config "Default Web Site/mojo"

After you migrate your application, it will run in both Classic and Integrated .NET modes, as well as on downlevel platforms.
2) Move this application to an application pool using the Classic .NET mode.
You can move the application to the default application pool using the Classic .NET mode by running the following from an command line window (the window must be running as Administrator):

%systemroot%\system32\inetsrv\APPCMD.EXE set app "Default Web Site/mojo" /applicationPool:"Classic .NET AppPool"

Alternatively, you can use any other application pool on your system that is running in the Classic .NET mode. You can also use the IIS Administration tool to move this application to another application pool.

It is preferred that you migrate this application by using option 1 to take advantage of the benefits provided by the Integrated .NET mode.

Error Code: 0x80070032

Notification: BeginRequest

Module: ConfigurationValidationModule

So I changed the AppPool to use the "Classic .NET AppPool", since I want to keep mojoPortal compatible with IIS 6 and Mono xsp2

and now its working fine.

Speaking of Mono, progress is being made to get mojoPortal 2.x working under Mono. This week we got past this bug that was blocking progress for us. Big thanks to Marek, Paolo, and Miguel for all their help! We still have some issues to work through but I have a feeling we're getting much closer to working now.

I remember that magic feeling when I got the first version of mojoPortal working on linux with Mono, when the latest 2.0 ASP.NET version of mojoPortal works I think I'm going to feel it again.