Something very weird happened to me last week, I could not run any Sitefinity 11.1 application from the new SitefinityCMS.exe Project Manager. Chrome kept reporting a refused connection as you can see in the image below
While upgrading your Sitefinity site to 11.0, you might be surprised that after you deploy your Sitefinity site to your production server, you might get an error complaining about a missing method exception.
WebActivator allows us to execute a code long before application start-up. There may be requirements when you need to load external assemblies or instantiate a particular object before the application start up.
Sitefinity’s MVC widgets are fantastic. They allow untold amounts of customization and enable you to create an MVC framework as complex or as simple as you need. There is a caveat to using them, however: Because the controllers are typical ASP.NET MVC controllers, going to particular pages on your site might make them disappear! There is a simple workaround for this problem, and with this information you can ensure that your Sitefinity MVC widgets consistently display no matter what current state your web site is in.
Feather widgets in Sitefinity are a significant improvement over traditional Sitefinity widgets. They are more responsive, provide better tooling, and are easier to customize (both the main area as well as designer views). However, I recently encountered an issue with one of the basic default Feather widgets included with more recent versions of Sitefinity. In this post we’re going to see how to modify this behavior, so that when working with the Feather Content Block widget we have it behave the way we would like. This post also serves a second purpose: Introducing how to modify a built-in Sitefinity Feather widget’s behavior. This technique can be used to modify any custom or built-in Sitefinity Feather widget.