 |
|
|
Joined: 1/1/2004
Posts: 56
|
|
|
We are just starting to compare DotNetNuke with SiteFinity.
We have no developers with SiteFinity experience and one developer with DotNetNuke experience.
Here are some of our thoughts/questions......
1) Most of our developers understand the ASP.NET MasterPage model, so the transition to SiteFinity might be easier.
2) DotNetNuke has been around for some time, and has a mature 3rd party market.
3) Most of our developers have used (and liked) the Telerik controls.
4) DotNetNuke is backward compatible - Will SiteFinity offer the same in future releases?
5) Can we use VS2010 to develop ASP.NET 4 modules for SiteFinity.
6) Is DotNetNuke slower?
7) SiteFinity is not open source. Is this a problem or benefit?
8) We would like to authenticate user login with our existing MS CRM system. Can this be achieved easily or will we have to write our own provider?
9) We need to evaluate how easy content management is for the end user re. SiteFinity vs DotNetNuke
10) We need to evaluate security re. The granularity of Role allocation eg. Page, Module, Content etc.
11) SiteFinity is not a Portal based CMS. Do we need this?
12) Telerik seems to support DotNetNuke eg. Telerik grid is shipped with DotNetNuke - Are these competing products? If not, how do they differ.
13) The Pro version of DotNetNuke is more expensive than SiteFinity, but DotNetNuke has a free Community version
14) How good is the DotNetNuke Pro support compared to the SiteFinity support eg. Does SiteFinity have a support ticketing system.
15) How easy is it to understand the API? re. SiteFinity vs DotNetNuke - Is Telerik documention better than DotNetNuke?
16) How easy is it to deploy modules? re. SiteFinity vs DotNetNuke
17) Can we consume webservice methods? re. SiteFinity vs DotNetNuke
This is the starting point for our evaluation.
I'll be asking the SiteFinity guys the same questions, so any comments from you would be appreciated.
Regards,
Pau.
|
| |
|
|
 | |
|
|
|
I'll take a stab at some replies for you.
1) Most of our developers understand the ASP.NET MasterPage model, so the transition to SiteFinity might be easier.
That might be true, I haven't done much more than poke around with SiteFinity, but I know that most developers can get to the DNN way a bit faster.
2) DotNetNuke has been around for some time, and has a mature 3rd party market.
This is a big thing depending on what you are doing, the 3rd party vendors and modules are great and can save a lot of time
3) Most of our developers have used (and liked) the Telerik controls.
You can still use them with both systems
4) DotNetNuke is backward compatible - Will SiteFinity offer the same in future releases?
That is a question for Telerik
5) Can we use VS2010 to develop ASP.NET 4 modules for SiteFinity.
You can do the same with DNN
6) Is DotNetNuke slower?
Not from what I have seen, DNN performs very well, if properly configured.
7) SiteFinity is not open source. Is this a problem or benefit?
This is going to depend on what you are doing and what level you want to do. The nice thing with OpenSource is if push comes to shove and you have an issue that you have to deal with you could fix it yourself.
8) We would like to authenticate user login with our existing MS CRM system. Can this be achieved easily or will we have to write our own provider?
For working with DNN you will need to create a custom authentication provider, but it is a fairly simple task.
9) We need to evaluate how easy content management is for the end user re. SiteFinity vs DotNetNuke
This is going to be something you will have to play with, as each individual is going to look at this differently
10) We need to evaluate security re. The granularity of Role allocation eg. Page, Module, Content etc.
This is going to be something you will have to play with, as each individual is going to look at this differently
11) SiteFinity is not a Portal based CMS. Do we need this?
This depends on what you are trying to do
12) Telerik seems to support DotNetNuke eg. Telerik grid is shipped with DotNetNuke - Are these competing products? If not, how do they differ.
They are competing, but they are also mutually supported. Not sure how to explain it. I see DNN as being much more flexible though
13) The Pro version of DotNetNuke is more expensive than SiteFinity, but DotNetNuke has a free Community version
This depends on your needs, I have a large number of very large sites all running on CE without issue....
14) How good is the DotNetNuke Pro support compared to the SiteFinity support eg. Does SiteFinity have a support ticketing system.
I'm not going to comment on this one
15) How easy is it to understand the API? re. SiteFinity vs DotNetNuke - Is Telerik documention better than DotNetNuke?
DotNetNuke documentation isn't perfect....and can be hard to find, but there are MANY other sources to get help/support/information.
16) How easy is it to deploy modules? re. SiteFinity vs DotNetNuke
The DNN model is very easy once you get the hang of it, site finity I'm not too sure.
17) Can we consume webservice methods? re. SiteFinity vs DotNetNuke
You can consume web services in DNN modules without issue.
|
| |
|
|
| |
|
|
Joined: 1/1/2004
Posts: 56
|
|
|
Hi Mitchel,
Just for the record..... I'm a big fan of DNN, but I need to have my beliefs challenged from time to time.
As you can see, some of these questions can only be answered by ourselves.
Thanks for your time in getting back to me. I appreciate your comments.
BTW - Can you point me in the right direction re. developing DNN modules using VS2010 and ASP.NET 4
Regards,
Paul.
|
| |
|
|
| |
|
|
 |
Joined: 6/3/2005
Posts: 2799
|
|
|
Paul Wade wrote:
BTW - Can you point me in the right direction re. developing DNN modules using VS2010 and ASP.NET 4
Michael Washington. Know him. Love him. Worship him. Or at least visit his website at adefwebserver.com and look at his DNN 5 book from Packt Publishing. Mitch's book from Wrox is also a good one, though it was published before ASP.NET 4.0. Basically DNN doesn't care if you use ASP.NET 4.0 and VS 2010, provided you have the framework installed and configured for the site.
Jeff
|
| |
|
|
| |
|
|
Joined: 6/28/2010
Posts: 1
|
|
|
I would like to suggest you to get Kentico CMS in your consideration as well. It's priced at the same level as Sitefinity if you use the Small Business license, or you can go with the Free Edition which can be used even for commercial purposes.
My comments on your list:
1) Most of our developers understand the ASP.NET MasterPage model, so the transition to SiteFinity might be easier.
Kentico CMS uses the same model, fruthermore it can be opened as a project in Visual Studio so developers can work in an environment common to them.
2) DotNetNuke has been around for some time, and has a mature 3rd party market.
Kentico CMS is on the market for 6 years already and it is full-featured platform with 250+ webparts, what makes it out-of-the-box solution. Anyway it can be easily enhanced with custom webparts/controls. There is also a marketplace where developers can share their work (most of the modules, webparts and templates are for free).
3) Most of our developers have used (and liked) the Telerik controls.
-
4) DotNetNuke is backward compatible - Will SiteFinity offer the same in future releases?
Downgrade isn't supported.
5) Can we use VS2010 to develop ASP.NET 4 modules for SiteFinity.
Kentico CMS 5.5 is fully integrated with VS2010, and supports .net 4.0.
6) Is DotNetNuke slower?
Performance report tells the best: http://devnet.kentico.com/Blogs/Martin-Hejtmanek/May-2010/Kentico-CMS-5-0-Performance-report.aspx
7) SiteFinity is not open source. Is this a problem or benefit?
Of course having the source code makes you sleep well :) Source code of Kentico CMS can be purchased, naturaly the price coresponds with it. Anyway, even without source code you have still the 7day bug fixing policy what keeps you safe.
8) We would like to authenticate user login with our existing MS CRM system. Can this be achieved easily or will we have to write our own provider?
For experienced .NET developers it should not represent any major block.
9) We need to evaluate how easy content management is for the end user re. SiteFinity vs DotNetNuke
Version 5.0 made Kentico the moste intuitive CMS I have ever worked with.
10) We need to evaluate security re. The granularity of Role allocation eg. Page, Module, Content etc.
Kentico CMS provides a flexible security model that allows you to configure granular access permissions for content and modules.The model consists of: roles, users, module permission, document permission and UI personalization...
11) SiteFinity is not a Portal based CMS. Do we need this?
Really depends on your needs, Kentico is Web based CMS.
12) Telerik seems to support DotNetNuke eg. Telerik grid is shipped with DotNetNuke - Are these competing products? If not, how do they differ.
-
13) The Pro version of DotNetNuke is more expensive than SiteFinity, but DotNetNuke has a free Community version
Kentico has free edition for your domain name which lasts for lifetime.
14) How good is the DotNetNuke Pro support compared to the SiteFinity support eg. Does SiteFinity have a support ticketing system.
Kentico has highly reponsive support for clients, if you go only with free edition you have still support via forums.
15) How easy is it to understand the API? re. SiteFinity vs DotNetNuke - Is Telerik documention better than DotNetNuke?
API is open and well documented.
16) How easy is it to deploy modules? re. SiteFinity vs DotNetNuke
It's very easy, you can check the developer tutorial Kentico has.
17) Can we consume webservice methods? re. SiteFinity vs DotNetNuke
You can consume web services in Kentico modules without issue.
|
| |
|
|
| |