Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ASP.NET vs CMS (Content Management Server)

0 views
Skip to first unread message

Andrew Hopper

unread,
Sep 5, 2001, 11:40:47 AM9/5/01
to
ASP.NET is not a content management product. It is a development platform
that one could use to build a content management product. If you were to
purchase Content Management Server, you would find that 90-100% of the
functionality you need for your application is there and the remaining 10%
will be customization (or reducing requirements to better match the
capabilities of CMS). If you decide to use ASP.NET, you would find that 95%
of the work remains to be done - you would have to develop virtually
everything (document submission, workflow logic, versioning, security) using
the framework ASP.NET provides.

Like all projects, this all depends on the customers' requirements/budgetary
constraints. If the budget is $2k, whip up a simple (and I mean SIMPLE) app
with ASP.NET (but it won't have as many features as CMS), if the budget is
$100k, purchase CMS and spend the rest of the money on customization and UI
design.

-Andrew Hopper

P.S. Please don't cross-post to groups that don't directly pertain to your
question. The ASP.NET group (microsoft.public.dotnet.framework.aspnet) is
the appropriate group for such a question.

""Adam Cogan"" <adam...@ssw.com.au> wrote in message
news:#tMkpHGNBHA.1796@tkmsftngp03...
> Hi
>
> I am very familiar with ASP.Net - I have completed specifications for a
> client and proposed an ASP.Net solution. It is what I would call a
standard
> site. It has:
> * some of the site driven by data in a SQL database and
> * some of the site which is content and users will create html pages and
add
> them there.
> * I will be creating maintenance pages for these and the site menu etc
>
> The customer knows the costs of CMS and he has come back to me and said:
>
> "Could you provide a few paragraphs detailing why you think ASP.NET is a
> better platform for this application than Content Management Server."
>
> I am not sure what to say to him. I assume the solution I have suggested
is
> more mainstream than CMS and I expect ASP.Net is more flexible that CMS.
>
> Comments?
>
> Adam
> * Keep up-to-date by attending the monthly meetings at the 'Access/SQL
> Server/ASP.Net User Group, Sydney" www.ssw.com.au/AccessUG
> --------------------------------------------------------
> Check out these HOT UTILITIES FOR ACCESS AND VB DEVELOPERS....
> www.ssw.com.au
> * SSW Data PRO - Version Control for your data.mdb
> * SSW Data Renovator - Compare the differences between two data.mdb's
> * SSW Upsize PRO! - Don't UPSIZE to SQL Server without it
> * SSW SQL Script Wizard - A utility to run .sql files
> * SSW Performance PRO! - Find out what is slow in your Access App
> * SSW Contactor - An Outlook 2000 and 2000 Add-in
> --------------------------------------------------------
>
>
>
>


0 new messages