I managed to convert a copy of mojoPortal to VS 2005 this evening without too much trouble. I had a few compile errors that were easily remedied then the Solution built fine and most importantly, the site works!

The next step is to test a deployment on mono and make sure things still work. I think they will since I'm really not using any of the ASP.NET 2.0 features yet. I know some of the 2.0 features are ready in mono so I expect I will tiptoe into changes to the new 2.0 way of doing things and test each change on mono as I go.

Then the next logical step is to tag the current VS 2003 code in svn and update the trunk to VS 2005. My timeline on this will depend on how the testing goes but I'm inclined to do it soon if things go well.

I invite comments from those of you actively working with the mojoPortal source code in VS.NET. Are you going to have access to VS 2005 anytime soon or will it cut you out of the loop if the main branch of development moves to VS 2005?

I'm excited about the 2.0 .NET stuff. There are definitely some major changes and new ways of doing things though it seems to support the old way fairly well so I think we can effectively pace our changes to coincide with mono support. I'm definitely not planning on doing anything that doesn't work under mono. It will be interesting to find out how much is already working.