CMS advice

[John Goodfellow]

I'm trying to find a .NET-centric alternative to the Plone CMS package. For
those not familiar, Plone is an open source CMS built on the Zope
application server which is built on Python. I'm the developer, trying to
weasel out of learning the very large and complex Zope system. Criteria
would be:

1. low purchase cost, hundreds instead of thousands
2. geared towards medium-sized intranet development, rather than community
site building
3. good document handling capabilities, some forms facilities
4. at least somewhat open source & extensible using .NET development tools,
preferably VB.NET

I have been crawling the web for days, and found many. Now I am looking for
your personal experiences and favorites .

Thanks.
John G.

 

[Erik Funkenbusch]

1. low purchase cost, hundreds instead of thousands
2. geared towards medium-sized intranet development, rather than community
site building
3. good document handling capabilities, some forms facilities
4. at least somewhat open source & extensible using .NET development tools,
preferably VB.NET

DotNetNuke works pretty well, but it is more community oriented. It's got
a pretty good module development model though. It's also one of the most
supported .NET CMS's out there.

 

[John Timney \( MVP \)]

try

http://www.axcms.net/en_axcms_services.AxCMS?ActiveID=7251

Free............always a nice to have.

 

[Darren Kopp]

http://csharp-source.net/open-source/content-managment-systems

There's a list of some. Some are c#, some vb.net, some are both. I
have only used DNN and Rainbow.

HTH,
Darren Kopp
http://blog.secudocs.com/

 

[clintonG]

Windows SharePoint Services should be considered.

<%= Clinton Gallagher

 

[Nick Malik [Microsoft]]

Just to expand on Clinton's answer:

Windows Sharepoint Services is FREE and runs on Windows Server 2003 (and
newer offerings ;-). It uses SQL Server to manage the content, has a very
well documented API, and provides basic portal capabilities for intranet
use. It integrates very well with Microsoft Infopath, which is a forms tool
that comes shipped with Microsoft Office (scores of folks have this tool and
are not aware of it). Not to be confused with Sharepoint Portal Services
which is a retail product (e.g. it costs a little money) that is built on
TOP of Windows Sharepoint Services. Here's a link to more info on both WSS
and SPS
http://www.microsoft.com/windowsserver2003/technologies/sharepoint/default.mspx

For some intranet requirements WSS is fine. For very large intranet
deployments, I'd suggest Sharepoint Portal Server. Note: Microsoft's
internal intranet is mostly Sharepoint Portal Server. It is managing
terabytes of document data. For more info on how Sharepoint is used within
Microsoft, see:
http://www.microsoft.com/technet/itsolutions/msit/sps.mspx

Hope this helps,

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.