However, when I tried to open the mojoPortal solution in VS 2008 the first thing that happens is the project conversion wizard starts, so apparently the projects and solutions are not backward compatible. I of course immediately cancelled the operation because it said the projects and solution would no longer work with VS 2005 so if I do this that means that no-one can work with the solution unless they have VS 2008.
So we face a hurdle for the project that I'm sure other open source .NET projects will also face. Obviously at some point we must move forward but the question is how long should we wait?
I invite your feedback if you are actively using mojoPortal in your development, how soon will you be getting VS 2008? How long do you think we should wait before making the change and leaving behind VS 2005?
UPDATE: I stand happily corrected!
Thanks to the readers who pointed out that only the solution files changed. This is great news! I'm in the process now of making bakup solution files for VS 2005 and upgrading the solutions for VS 2008. Should have this in svn trunk in the next few hours.
Note for those who don't have VS 2008 you will need to use the alternte solution files which have been renamed like mojoportal-complete-vs2005.sln
This means that those of us with VS 2008 can move forward without leaving behind the VS 2005 developers. Though at some point we will need to make the decision to target the 3.5 framework instead of the 2.0 framework I think we can potentially add projects to the solution that do target 3.5, we just can't change the target on projects that are shared in he VS 2005 solution files.
Happy Day! Go get your free 90 day trial of VS 2008 or if you are an msdn subscriber you can get it there.