A VS 2005/ASP.NET 2.0 release of mojoPortal coming soon

Things are shaping up on the VS 2005/ASP.NET 2.0 branch of mojoPortal. I am shooting for a release of that branch this weekend to ring in the new year.

It seems to be working very well on Windows and on mono with a few tweaks. There is really not much holding us back from just going forward with the vs 2005/ASP.NET 2.0 version.

So now I'm trying to figure out at what point we fully transition to 2.0 and how long we keep making releases for the 1.1 framework.

Most Windows developers I know already have VS 2005 and of course those of us who have it would rather work with the new version than the old version. But I get a lot of downloads of the release files so I'm not sure its only developers I need to consider. I would love to hear feedback on that question if you have a point of view.

This decision I think will have to factor into my versioning scheme. If we are going to support 2 release branches for a while I might bump the version for the vs 2005 branch of mojoPortal to 2.0 to distinguish it clearly from the 1.x branch but if we are just going to drop development on the vs 2003/1.1 framework version I'd be more likely to version the next release 1.x and from thence forward its not for ASP.NET 1.1/vs 2003 but for vs 2005. Obviously the second choice requires less effort than maintaining 2 branches, but will anyone be left behind? Speak up if you will be negativley impacted by a quick transition to 2.0

Posted by mojoPortal Thursday, December 29, 2005 3:14:42 PM Categories: Releases

Comments

Dean Brettle

re: A VS 2005/ASP.NET 2.0 release of mojoPortal coming soon

Thursday, December 29, 2005 7:09:55 PM
Regardless of whether you do additional releases that target .NET 1.1, I think you should call the first release which targets .NET 2.0 "mojoPortal 2.0".  To me, the bump in major version number is a clear indication that it is not compatible with earlier releases.  In this case it isn't compatible, because it won't work on a .NET 1.1 installation like mojoPortal 1.0 did.

In general, I prefer the x.y.z release naming scheme, where bumping x signals an incompatible change, bumping y signal new features, and bumping z signals bugfixes.

From a source-code management perspective, I recommend branching (svn cp trunk branches/mojoPortal-x.y) for each release that includes new features and tagging every release (svn cp branches/mojoPortal-x.y tags/mojoPortal-x.y.z).  The former makes it easy to do bugfix-only updates to earlier releases, and the latter ensures that you can always get back to exactly the code you released.

--Dean
Joe

re: A VS 2005/ASP.NET 2.0 release of mojoPortal coming soon

Friday, December 30, 2005 3:10:29 AM
Good advice as always Dean!
Aaron King

re: A VS 2005/ASP.NET 2.0 release of mojoPortal coming soon

Friday, December 30, 2005 9:33:58 AM
I don't think any of my clients will be left behind.  I can easily set my server up for ASP.NET 2.0 to be default instead of ASP.NET 1.1.  I currently develop in both VS 2003 and 2005. 

I also currently have to release to both versions of the framework.  It limits my capabilities because I can't use anything in 2 that isnt in 1.1. 

I would vote for moving on past 1.1.
Aaron King

re: A VS 2005/ASP.NET 2.0 release of mojoPortal coming soon

Friday, December 30, 2005 9:35:13 AM
FYI My firewall can't get to your 80?? ports.
Joe

re: A VS 2005/ASP.NET 2.0 release of mojoPortal coming soon

Friday, December 30, 2005 9:43:13 AM
My site is hosted through a proxy that routes traffic from port 80 to another port. I think you can get to port 80 but sometimes on a re-direct it redirects to the real port which is probably what is the real issue. In other words the proxy listens on port 80 but routes to apache on another port but sometimes after postback mojoportal code redirects to the proxied port and that is probably not open in your firewall.
This technique is how my hoster allows us each to have our own instance of apache that we can start and stop as needed. Each instance runs on a different port but the proxy makes it seem as if all are running on port 80.

I think it is something I can workaround in the mojoportal code but haven't bothered yet.
Tom Opgenorth

re: A VS 2005/ASP.NET 2.0 release of mojoPortal coming soon

Friday, December 30, 2005 6:11:30 PM
FWIW, I'd think that migrating to ASP.NET 2.0 is a good idea.  It seems that most of my development is for .NET 2.0 these days.
sohbet

re: A VS 2005/ASP.NET 2.0 release of mojoPortal coming soon

Monday, May 21, 2007 7:38:51 AM
Comments are closed on this post.