10

I am trying to integrate a CMS into an existing ASP.NET Web site built with .aspx files and .aspx.cs code behind files (not compiled).

My research indicated that my best candidate is N2 CMS.

My ideal approach is to configure the editor with various editable content types and have my existing pages and user controls use the API to retrieve the content and place it pro grammatically into containers.

I couldn't find how this can be done, anyone have any idea how and if can this be done ?

Is there any other CMS that is better suited for the task?

BigJump
  • 15,561
  • 3
  • 31
  • 29
Variant
  • 17,279
  • 4
  • 40
  • 65

3 Answers3

6

We have had this exact setup existing web applications (WebForms + MVC) integrated with N2 in the same manner as you have described in previous projects and it was fairly simple to implement, but by now we have switched to using umbraco for the same purpose for the following reason:

  • better support (larger community)
  • better backend editors
  • more ready avilable modules (even commercial supported ones)
  • richer backend ( proper multi language support)
  • configurable rather than code oriented (this is a pro/con depending what you need)

One important note:
Don't waste time host the CMS + the actual application in the within the same ASP.NET application. We have all of the installations separate and we would have not done it differently looking back, especially when you have existing web applications with routing etc. in place already. The CMS is just going to mess this up at some point. Also this is not CMS specific.

ntziolis
  • 10,091
  • 1
  • 34
  • 50
  • Umbraco is indeed a great CMS and I have some experience with it however it seems like it would be very hard to integrate into my existing web site. – Variant Mar 14 '12 at 12:48
  • That's what I thought, but it is actually no problem, as long as you keep CMS and web application separate. You simply use thee CMS for value storage / editing. And query the data you need via the API. The trouble starts (for both N2 and umbraco) when you try to merge the CMS into your application, so stay away from this. – ntziolis Mar 14 '12 at 12:50
  • The idea of hosting in a different application is very good. How do your pages query the content from the umbraco? using HTTP or directly from the database using the umbraco API? – Variant Mar 14 '12 at 12:51
  • Sometimes both actually, but for the most part we use the Umbraco API for performance reasons, just make sure the DB is actually the same machine – ntziolis Mar 14 '12 at 12:53
  • Same machine or use the same database? (which means same connection string) ? My setup has several load balanced web servers connecting to a single database server. – Variant Mar 14 '12 at 12:56
  • Same db in your case. Just meant to emphasize to host it where both umbraco + the application can access is as fast as possible. – ntziolis Mar 14 '12 at 12:57
1

Traditional CMS are pretty intrusive, they dictate you the way you must build your system. And if you already have a web site, and just want to add some Content Management functionality into it you are out of luck - all traditional CMS want you to demolish your old web site and rebuild everything from scratch.

It's actually a good idea to keep CMS and web application separate. In that case all you need is some kind of markers on your web pages telling the CMS what should be manageable. "Software plus Service" solution. This is what ElasticWCM (http://www.elasticWCM.com) is trying to do.

For a web site developer ElasticWCM is just a set of ASP.NET controls you can wrap around your Html to make the content manageable. When you click on the "Edit Page" button on the PageToolbar control you get redirected to the rich page editor where you can manage all your content fields. Nothing to install, just reference the controls' DLL.

You can't get less intrusive than that. As a bonus you receive all bells and whistles of a full-scale multilingual CMS and a bunch of unique features.

Aleksey
  • 252
  • 2
  • 10
0

We have had a fair amount of luck with Sitefinity from Telerik. It's .net based, easy to extend, and has a good collection of plugins. On the downside it is pricey.

Rob Lauer
  • 3,075
  • 1
  • 32
  • 44