Is Sharepoint like a ferari where Dnn is like honda. Or is it much more than that?

Thanks.

No I think it would be better to say that DNN is a Ford Explorer and Sharepoint is a Lincoln Navigator. Very similiar in function, one has more bells and whistles and a higher price tag, but they both could be used for off roading.

A year for customization really isn't that much. We've spent 8 months doing a DNN site. It would have been shorter using other software, but our budget was a grand total of 7K for non-internal resources, which rather limited our ability to go with a high-end CMS.

You really can't compare DNN and Sharepoint, as has been said. They don't really fulfill the same job, unless you are looking at them purely as a CMS.

If you're looking at them as part of a workflow, intranet system which integrates into an existing MS-based product offering... Which is what most Sharepoint users are looking for, then DNN has nothing on it.

As a pure-play CMS though, DNN is good enough, for the price and has a lot that other CMS's could learn from.

Hi Guys
Are there any estimators out there who could let us know how much a Sharepoint -V- DNN implementation could cost. Lets say in a middle ground senario where the features & additions to DNN might be comparable to sharepoint...

Paul

Sharepoint 2003 is going to cost my company around $19,000. That is for the server license and all the client licenses. The client licenses are $71 each...there is volume licensing available, and that makes larger implementation more "cost effective"

DotNetNuke is free, but doesn't have some all the slick corporate features of SharePoint.

I have no idea how import and this is to you or your company, or how many users you'll have.....my company can afford SharePoint...so they chose to use it for thier Intranet. I would rather have seen DNN get used :)


The main thing that is missing from DotNetNuke that would make it really usefull in a corporate environment is workflow...and that is coming in the future.

you can integrate other CMS's that have workflow into DotNetNuke, such as Ektron CMS. I have spoken to Eltron about this, and they were able to integrate it with IBuySpy, but they didn't not try it with DNN..but I'm sure its possible.

If money were an issue..and you wanted a really robusy Portal, you could rollout DotNetNuke and wrap it around somethying like Ektron CMS and potentially save lots of money.....

Bot MS and Ektron have different licensing requirements, and one can be more expensive than the other depending on your needs....generally, for smaller companies you save with Ektron....but money may not be your only concern

The peopel that run my company have a serious Microsoft hard-on...so they like to stick with MS and generally don't care about the money.

If workflow is the main piece missing from DNN compared to Sharepoint...there is a workflow module available for DNN on Snowcovered for $29.95.

I haven't purchased it so I can't say how good it is...but it is there.

Regards,
Mike

Guys ANyone knows..why I am getting this error.

tks in adv.
Raj
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load type 'DotNetNuke.CDefault'.

Source Error:


Line 1: <%@ Page CodeBehind="Default.aspx.vb" language="vb" AutoEventWireup="false" Inherits="DotNetNuke.CDefault" %>
Line 2: <%--
Line 3:


Source File: C:\TITES\DotNetNuke\Default.aspx Line: 1


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573

This is tough question to answer without all of the facts. To implement Sharepoint 2003 you need Office XP or Office 2003 and MS Server 2003. If the customer already has the proper version of Office and Server the price can be pretty 'cheap'. If they're running Office 97 they'll need to upgrade. That upgrade could get pretty expensive, cost of licenses and training, installation, they might have to upgrade desktop computers, etc. Same with Server 2003.

Ted

Ektron is pretty expensive too. For 1 URL it is $500. Atleast for me this is very expensive i don't know about others.

Thanks.

Just a note for anyone doing searches for this type of stuff.

Ektron CMS-300 $5,500 for a single url and 10 users and $22,200 for a single url and unlimited users.

Ektron CMS-200 $3,300 for a single url and 10 users and $14,400 for a single url and unlimited users.

Integration between DNN and SharePoint would be really interesting. I think lots of companies who are setting up an intranet environment (smaller companies) aren't ready for sharepoint at the start. Not because of the money, but because it takes time to get people used to working with an intranet. These people want to use the intranet for "giving information" at first and will develop to an environment where they will also "share information" and "work online together", but that will take time (I did some research about it during graduation).

These people will be happy to use DNN during the first stages of their intranet.
Probably most of these companies aren't using windows 2003 yet. They would probably be ready to use an application like sharepoint by the time there's a sharepoint 2004. This will give sharepoint some time to develop (2003 is allready much better than the previous version).
I think these kind of companies would love to use DNN in the future as an information giving environment and will use sharepoint as a sharing environment. Integration between the two would be an opportunity.

I'm using Ektron for two medium sized projects right now. It is a really great product, has fantastic workflow, easy implementation and the price is affordable for most medium size businesses. It costs around $5500 + support contract to manage one website with 10 content editors. It really is a great product and I think its the best CMS in its class for managing traditional corporate websites that have tons of static content that changes often. It really is worth the money. Ektron is also reengineering CMS 200/300 with .NET from the ground up, so the future is going to bring some yield some great advantages to developers and very nice integration with VS.NET.

Sharepoint is not bad, but it can be overkill for many small and medium businesses. Its license model can make it unaffordable too. Altough, building the Sharepoin equivalent of "Modules" can be easier than DNN because of integration with VS.NET...but in my opion its not worth shelling out $10,000 for corporate wide end user licenses.

DNN. I can't say enough about DNN. It rocks. Althoguh I don't think DNN is best suited for managing websites that are full of static content (at least not yet), but it EXCELS when you need to build a "Web Application" or Portal such as. I've been toying with the idea of builind an Ektron CMS and DNN integration layer. DNN's portal building capbilities mixed with Ektron's CMS and Workflow features woudl be a killer solution.

For some of my projects I've used DNN to build a Beta Tester portal for a company. The Portal hosted a forum, provided software downloads and announcements to the. It took only hours to set it up and develop some nice skins.

I also used DNN for another customer in the Medical Billing and MEdical Evaluation industry. They imaged all important customer documents. This portal let partners login and view new document images, search for old ones, ect ect. Using DNN as the base for this shaved off weeks of development time.