mojoPortal Released

I'm happy to announce the release of mojoPortal, available now on our download page. This is primarily a minor bug fix release for issues reported in the forums since the last release, but also introduces alternate Web.config files that allow hosting mojoPortal in ASP.NET 4.0.

Hosting in ASP.NET 4.0 and the Plan for Transitioning to 4.0

Although the current release of mojoPortal is compiled for the 3.5 SP1 .NET framework, it is compatible for hosting under .NET 4.0, but requires different Web.config settings. So basically we have 4 different Web.config files

  • Web.config is configured for .NET 3.5 full trust hosting
  • Web.mediumtrust.config is meant for .NET 3.5 medium trust hosting
  • Web.net4.config is for .NET 4 full trust hosting
  • Web.net4.mediumtrust.config is for .NET 4 medium trust hosting

Whichever file you use needs to be named Web.config, so for example to run in .NET 4 medium trust you should rename the Web.config to Web.net35.config and then rename the Web.net4.mediumtrust.config to Web.config has been running under .NET 4 for several days now and seems to be working well. My recommendation would be for new installations to use .NET 4 hosting to be future proof. I might hold off a bit before migrating existing installations to .NET 4 but it is time to start thinking about migrating to .NET 4 at some point in the not too distant future.

UPDATE 2010-05-15 Several people have reported problems trying to get mojoPortal working in shared hosting under .NET 4. Therefore I recommend stay with 3.5 hosting until we put out a package compiled for .NET 4.

For developers

In the source code packages and in our svn source code repository, we currently have alternate project and solution files for Visual Studio 2008, but the main projects and solutions have already been converted to Visual Studio 2010. I recommend that everyone begin using Visual Studio 2010 as soon as possible. I will not be keeping the VS 2008 compatible files for long because it is more work to do so. You can also use the free Visual Web Developer Express 2010, so there should be no barrier to moving forward. After eliminating the VS 2008 project and solution files, I will then setup alternate project and solution files for .NET 3.5 and then the main projects and solution can be changed to target .NET 4. Once I do this, we will have to maintain separate release packages for 3.5 and 4.0 .NET and we will have to use conditional compilation to wrap any use of .NET 4 specific features so that we can continue to produce builds for 3.5 .NET. We went through a similar process with the transition from .NET 1.1 to .NET 2.0 back in 2005. it will be more difficult for a while having to manage supporting both 3.5 and 4.0 .NET while beginning to use some of the 4.0 features. We will probably do this for about 1 year and then we will drop the effort to support 3.5 framework. Hopefully this will give most users enough time to migrate to 4.0 .NET hosting.


  • Implemented option to allow users to choose which editor they prefer if enabled from site settings
  • Added setting to allow hiding the search box in forums per community request
  • made it possible to use a custom configuration file for the Vertigo Silverlight slideshow used in the Image Gallery and Flickr module, to be documented
  • upgrade from NeatUpload 1.3.22 to 1.3.24
  • updated Italian Translation from Diego Mora
  • added some Codesmith templates for VB.NET in source code package
  • some more refinements of TimeZone handling
  • previously we had added this to the layout.master file of skins to pre-zoom the screen for iPhone: 
    <meta name="viewport" content="width=670, initial-scale=0.45, minimum-scale=0.45"/>
    this has been removed from existing skins and I recommend you remove it from your layout.master if it is there after upgrading. The reason is that it also affects iPad, but we really don't want to pre-zoom the screen in iPad since the screen is much larger, so now we add this meta element from code only when the request is from iPhone, therefore it does not need to be in the layout.master file
  • fixed an issue where the wrong cart could be used if there were more than 1 WebStore in a site
  • other miscellaneous bug fixes for things reported in the forums

I'm still working on the series of developer training videos and you can expect to see more of them in May


Follow us on twitter or become a fan on Facebook

follow us on twitter become a fan on facebook

Gravatar Joe Audette is the founder of the mojoPortal project and was the primary developer until February 2017.