Welcome to my articles on Sitefinity and the and experiences I have had. I do love helping others out and it gives me a real thrill when people approach me for help and second when I actually help them out. So here I not only hope to help others out but also hope that others take the time to help me out. I don't mind being wrong but I do hate being wrong for a long time. So call me out if you can, help me to avoid writing another Doh story.
In a recent internal build the Sitefinity team has added a new feature request allowing one to control the Vary By options for output caching. I wrote a post a while back talking about how to add this functionality in. But now, I am glad to say, this post is almost completely obsolete.
Sitefinity recommend setting Dynamic Compression Before Cache to true. So why then do they set it as false by default?
After upgrading to Sitefinity 8.2 my login widget stopped working with a return url query string. Checking my other sites they too had the same issue after upgrading.
If your site is running on the Azure platform then you may be interested in leveraging the Azure Redis Cache to help reduce and improve your sites performance.
Many Sitefinity sites are based on Web Forms and Web Forms use ViewState. It is common knowledge that uncontrolled ViewState can create a very large amount of data in our web pages and this data is sent back and forth with every request. There are many ways to reduce and turn off ViewState when it is not required but when it is there is one more method to help keep down the page size.
Almost from day one I thought Azure Web Sites was a better platform than Azure Cloud Services for Sitefinity. I have been running my Sitefinity instances there for 2 years now even though there was no support. But now its been announced that 8.2 will support Azure App Services, (Formerly Azure Web Sites), and I am super excited.
I have done several reviews of Sitefinity releases and they and this one are all following a trend in what I write. But I do have to be honest in that all the good stuff that I like to see, (bug fixes are one), are often delivered on a fortnightly basis which is always brilliant and great to see.
The number one performance issue I have with my clients Sitefinity sites is their inability to manage their images. This last week I have had a job to review image management on one site and explain to another client the difference between 1MB and 20Kb image effect on their site. And to top it off a third client with a database of over 1GB of image storage. So I thought I would do a couple of posts on the subject starting with using a CDN.
Using the custom errors and redirecting 404 requests to a Sitefinity page doesn't set\return the 404 response status. The issue arrives when your 404 page is based on a master page. To get around this you can either create a custom master page and override the render method or a widget which is added to the page.
Currently Sitefinity supports Azure Cloud Services but in my honest opinion Azure Websites are today the much better option. I run all my Sitefinity sites on Azure Websites and enjoy all the benefits I get from it. Except no support for multiple nodes, (or load balancing) or official support from the Sitefinity team.
I love the release progress of Sitefinity. Regular internal builds if you are looking for a fix before the next release and a steady march of new features. Sitefinity 8 is in beta and due out soon with all the 'What's new webinars' scheduled. A previous release, 7.2, had me impressed and ho-umm'd at the same time. When the 8.0 feature list came out I was interested to see if it would have me rushing to upgrade.
Sitefinity is secure platform. It is PCI and FIPS compliant in all areas where user credentials are stored but there are some things still left in your hands to ensure it is secure. Password policy is one area that you are in charge of. Passwords are pain. If we use something we can remember it is weak. If we use something secure its hard to remember. And what some sites require for a strong password are often not that strong.
Sitefinity uses a In Memory cache. It is an implementation of the Enterprise Library Caching Application Block. This works fine but its a bit slack when in a multi server environment. You are effectively caching the same data on every server and thus, I think, a bit redundant. But you can create your own implementation of the CacheManger using the ICacheManager interface. I have done this and used the Azure Redis Cache, a leader in distributed cache systems.
Without doubt you should be using the built in cache features of Sitefinity. The difference is significant if you don't. One of the first tweaks is to extend the time in cache for objects. But there are a few more improvements I have found from browsing the web and I have put them together here.