Hi, I am building an application which requires just about every feature in DNN. I just started looking at it last nite. I looked at Sitefinity yesterday for awhile. I am a VB Visual Studio guy with 10 years experience.
My application requires localization: How easy is this to implement, support, and maintain?
Does everything that is custom have to be added via the creation of a new module?
Does creation of a module really mean the creation of custom user controls that are uploaded? I kind of get this impression.
If the above line is true, do you lose flexibility for quick changes or is it pretty straight forward?
Can DNN support many different companies through 1 portal, where look and feel is defined by on the fly Themes swap?
Can DNN support the scenario where when a user logs in to a generic login page, that users company will be determined from a single database table and the Themes applied accordingly. I know that applying Themes on the fly is doable, I am wondering if there are any limitations with DNN that would prevent this or limit it's usage.
Can DNN support a scenario where as each company or even each user has a profile configuration table which would enable and disable certain ASP.NET controls?. In general, can you do anything, in DNN, that you can do in VS 2008, straight away?
Does DNN use ASP.NET Membership or does it use another custom configuration system.
Is there any reason why Telerik Rad tools or ComponentArt controls cannot be fully implemented in DNN?
this may be a bad question but... how do you compare yourself to Sitefinity? ( i think i know your answer already :))
thanks for any feedback. This seems like an awesome platform to build on but... this is part of the research.