09 Jan 2009
21 Nov 2011
Link to this post
We are on a POC phase working with Sitefinity and Web User Controls. Management's goal is to have a single set of Web User Controls (Compiled Widgets) that can be used on both Sitefinity CMS and on a standard ASP.Net app (a non-sitefinity web app). Mainly reason is minimize the UI code duplication and, by consequent, development effort.
However, I just concern about what Pure Sitefinity functionality could I dropping following this approach, so far my web user controls inherit from ASP.Net BASE System.Web.UI.UserControl class but not from Telerik.Sitefinity.Web.UI.SimpleView class for instance, since our ASP.Net web app has no reference to Sitefinity Dlls. For instance, I'm under impression that "Widgets Templates" doesn't work for System.Web.UI.UserControl controls... if that correct. what else?
Actually, I'm not sure if this approach (a single version for both Sitefinity and non-sitefinity ASP.Net web app) is the right path. I'm concern on end up with a nightmare because we would not able to get the best from both worlds and have to accept that we have a functional but limited web user controls version, you know... "Hey, let's do this great new feature in our web users controls this guys of sitefinity just released... ooh.. no we can't because it wouldn't work in a standard non-sitefinity web app, or viceversa..."
I'm really open to hear your thoughts...