The Artima Developer Community
Articles | News | Weblogs | Books | Forums
Artima Forums | Articles | Weblogs | Java Answers | News
Sponsored Link •

.NET Buzz Forum
CMS.RAPID v2 and Office 12 Server

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Mark Harrison

Posts: 3775
Nickname: mharrison
Registered: Dec, 2003

Mark Harrison is Microsoft UK Systems Engineer focussing on .NET eBiz and Portals
CMS.RAPID v2 and Office 12 Server Posted: Feb 3, 2006 2:06 PM
Reply to this message Reply

This post originated from an RSS feed registered with .NET Buzz by Mark Harrison.
Original Post: CMS.RAPID v2 and Office 12 Server
Feed Title: Mark Harrison
Feed URL: http://markharrison.co.uk/blog/xml.aspx
Feed Description: .NET Portals, Collaboration and eBiz 		Latest .NET Buzz Posts
Latest .NET Buzz Posts by Mark Harrison
Latest Posts From Mark Harrison

Advertisement
Ive just been in the CMS.RAPID R&D labs and seen the first cut at a RAPID v1 (MCMS2002) to RAPID v2 (Office 12 Server) migration utility. This enabled us to demonstrate the the RAPID example starter solution site RapidOrange converted and running under Office 12 Server.

The conversion took the MCMS content and RAPID metadata across to Office 12 Server. It also converted the RAPID xml templates to master pages / page layouts (check here) with the RAPID panel definitions being translated to web part zones. The RAPID components are now derived from web parts and so can be placed into the appropriate web part zones.

With MCMS2002 - page templates required Visual Studio.NET developers to create simple ASP.NET pages. Whilst Visual Studio made this very easy for a developer - it wasnt ideal. RAPID v1 shipped with an alternative template creation tool - the RAPID Definer which was aimed at enabling power users (rather than developers) to define templates.

The new approach for Office 12 Server page layout (think MCMS templates) development is for the developer to use Visual Studio.NET for encapsulating complex functionality into web parts and for the power user to use the new SharePoint Designer to assemble the page layout.

With the Office 12 Server support for the power user, the reasons for the RAPID Definer are no longer needed. RAPID v2 will drop the RAPID Definer and instead will embrace / extend on the SharePoint Designer functionality for defining the RAPID page layouts.

Read: CMS.RAPID v2 and Office 12 Server

Topic: Be careful when installing VS add-ins in localized Windows versions Previous Topic   Next Topic Topic: Did you say Unbreakable?
Sponsored Links


Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use