iFinity

1. Use Html in the File for better layout in the install pages This one comes from the blog of Erik VB : use html in the manifest file by including A CDATA section is a way of including xml/html within an xml file.  As a manifest file is just a big xml file, you can use this to your advantage and include cdata sections for various pieces of information.  For example, instead of providing an email address, here’s what’s in my manifiest file:

Contact Page]]>

When the module installs, instead of getting a plain listing of an email address, this gives a link to the page on the iFinity website for contact.    You can also see in the below screenshot that the Url is an actual link to the site.

...

A question that I field on a regular basis is ‘what performance implications are there for switching off page extensions on my DotNetNuke site?’.   If you peek around various posts and blogs, you’ll see dire warnings from people predicting the end of your server as you know it.   The main problem people have is that, when you switch off page extensions, all of the processing for all requests on the server are routed through the ASP.NET runtime, which has to serve up not only the dynamic ASP.NET pages, but all of the static content (js files, jpg files, css files et al) as well. 

My response to people has always been : switch it on and see what happens,  if your site becomes too slow then turn it back off again.  My advice tends to be of a practical nature in this respect.  My own site has been running without extensions for years, and while it is known to have the occasional hiccup, that’s never been to do with the missing .aspx on the Urls.

However, I decided to do a little bit of comparison with...