Its easy for users to create forms through Sitefinity. But the storage is a simple list and most people want some cool analytics and management of their form data such as provided by Salesforce or ActOn. In this post I look at an easy way to push our forms data to these third party services.
This is my third post of ideas to consider to help make your pages load and run faster. Some will help some projects while others may not be quite relevant. There will be some that contradict previous tips. But hopefully, you will find a few to improve your sites perfromance.
Sitefinity has added a security check named as the Signing Certificate. It is used to verify the issuer of the authentication token to enhance the safety of the site. But currently, the documentation is missing an important piece of configuration to allow this to work for Azure hosted sites.
Recently I came across (another) incorrect implementation of async code which has prompted me to write this post. Async methods are an encouraged code/design implementation but it is important to understand how it works and have some guidelines about using it. If you use it incorrectly, it will slow your application down rather than improving it.
Its not hard to spot a design that was created by a developer. Almost every Windows Form App up until 2010 suffered that horific left side brian effort. Thankfully today we often have a dedicated UI/UX designer sorting that out but even if you have no responsibity around what the front end pages look like you still have a major UX responsibility to ensure a successful project.
Sitefinity uses an in-memory cache service derived from the popular, (in it's day) Microsoft Enterprise Library application blocks. The trouble is that if you have a load balanced environment you are saving a copy of your cached data on every node. This extension adds a distributed cache option via Redis. It has some caveats to consider so make sure you understand those first.
This post continues a collection of ideas and options for you to pick from to help your Sitefinity projects run faster. Some are actualy Sitefinity specific. Some are for when developing. Some are for production. Most can be applied to any website. This post is a varity of bits and bobs.
This post is a collection of ideas and options for you to pick from to help your Sitefinity projects run faster. Some are actualy Sitefinity specific. Some are for when developing. Some are for production. Most can be applied to any website. This post focuses around resource loading. A second post will look at a varity of things.
When creating your own widgets one thing you don't want is if it throws an error to 500 the whole page. Maybe you do? This post is for those that don't want that but prefer to display something a bit more friendly and are looking for help tracking those, 'only happens in production with a random customer', errors.
Upgrading Sitefinity continues to improve. Back in the day, it was best to upgrade by each major version. Then NuGet packages came along and support for upgrading multiple major versions was supported. Now we have CLI and as of 13.1 it is quite robust and the way going forward I think.