There are times when testing custom features or skins on a mojoPortal implementation that the Cassini web server built into Visual Studio 2010 isn’t quite up to the task, or doesn’t reveal a problem that only manifests in a hosting environment. One great (and free!) way to even the odds is to utilize IIS Express 7.5 as your testing web server.
By default, whenever you run your mojoPortal instance in Visual Studio 2010, it will use the internal web server (Cassini). It’s actually amazingly simple to switch over to using IIS Server Express 7.5 as your development web server – just follow these steps.
1) Download IIS 7.5 Express here. Learn More
If you are doing custom development within mojoPortal, your users will find it extremely beneficial (and you’ll have a much more peaceful deployment) if you leverage mojoPortal’s built-in help system.
There are two ways to include “help” references in a custom module or page: the first way, which is specific to module settings, is to add a “helpKey” attribute to a “FeatureSetting” element within the feature’s Feature Definition config file. To see an example, open up one of the config files under mojoPortal.Web/Setup/applications/KDMediaPlayer/FeatureDefinitions. You’ll notice the “helpKey” attributes reference a file name – these files are located under the /Data/HelpFiles section. Learn More