A wrapper for telerik's r.a.d. Menu control allowing MCMS specific properties to be set at design time.
Recently, Microsoft and Telerik announced the availability of the r.a.d. Editor MCMS Edition. This extended version of the r.a.d Editor Web Control provides a replacement for MCMS's out of the box HtmlPlaceholder, offering a rich content editing experience, integration with MCMS Resource Galleries all without the requirement for client side ActiveX. In addition to the r.a.d Editor control, Telerik offer a suite of superb Web Controls for ASP.NET development which are also ideal for use with MCMS. This sample is a simple wrapper for the r.a.d Menu control which includes a number of additional MCMS specific design time properties.
Saturday, October 28, 2006
Code Samples - Extended Attachment Placeholder Control
An extension of the SingleAttachmentPlaceholder control afforing more control of Presentation Mode rendering.
The SingleAttachmentPlaceholder Control that ships with MCMS 2002 is a great way to include links to binary files on your site. However the Presentation Mode rendering of the control, especially when using the MustUseGeneratedIcon property leaves much to be desired. This control avoids the cost of dynamic rendering of icons, allows for full transparency in icons, more precise rendering control and the addition of a target attribute to open the link in a different frame or new window.
The SingleAttachmentPlaceholder Control that ships with MCMS 2002 is a great way to include links to binary files on your site. However the Presentation Mode rendering of the control, especially when using the MustUseGeneratedIcon property leaves much to be desired. This control avoids the cost of dynamic rendering of icons, allows for full transparency in icons, more precise rendering control and the addition of a target attribute to open the link in a different frame or new window.
Code Samples - Floating Console
An implementation of a Floaing Console for MCMS 2002, based on the MSDN article and sample for MCMS 2001.
You cannot access Content Management Server 2002 when you use a user from a universal group that belongs to a domain and the domain differs from the d
Consider the following scenario. You use a user from a universal group membership that belongs to a domain, and the domain differs from the domain of the universal group. You try to access Microsoft Content Management Server (MCMS) 2002. In this scenario, you cannot access MCMS 2002.
OFC202 - Windows SharePoint Services (version 3): Overview and What's New
This session covers technical fundamentals of the next generation of Microsoft's Web workspace technology - what's new, what's changed, how it works, and why you should deploy it and develop on it. This session is a prerequisite for "Office SharePoint Server 2007: Overview and What's New".
OFC207 - Microsoft Office SharePoint Server 2007: Overview and What's New
Office SharePoint Server 2007 is much more than an upgrade to SharePoint Portal Server 2003 and Content Management Server 2002. This session covers technical fundamentals, feature overviews, new sets of server functionality, and implications for developers and IT professionals alike. NOTE: Since Office SharePoint Server 2007 is built on Windows SharePoint Service 3.0, this session requires that you attend "Windows SharePoint Services 3.0 - Overview and What's New" first.
Web Content Management with MOSS 2007
Microsoft published this presentation to describe al about WCM with MOSS.
This is an important document to start working in WCM.
Download the document here
This is an important document to start working in WCM.
Download the document here
Friday, October 27, 2006
WSS vs. MOSS vs. WF
What about the workflow in office system 2007?
Microsoft published a word document to describe the workflow in one word document Check it out here
Understanding Workflow in Windows SharePoint Services and the 2007 Microsoft Office System.
Microsoft published a word document to describe the workflow in one word document Check it out here
Understanding Workflow in Windows SharePoint Services and the 2007 Microsoft Office System.
Bye Microsoft CMS, Hello MOSS WCM
This is a good article By Brice Dunwoodie
Bye Microsoft CMS, Hello MOSS WCM
By Brice Dunwoodie :: Filed Under »
Web CMS
The Microsoft Content Management Server (MCMS) has been emerging in its new form
over the past two and a half years. Beta 2 is out and we’re told production
will arrive in the environs of late 2006.
As for MCMS 2002 as we have known it? Its gone. Its history.
Its a fading memory.
…well that is, unless you have a very expensive
MCMS web infrastructure that you’ve invested hundreds of
thousands of dollars in. In that case, its high time you sit back and start figuring
out if your organization will jump the gap to the next gen Microsoft offering, or
if you’ll brave the waters of Web CMS
product selection and chart a new infrastructure road map.
Either way, both proud and pained owners of MCMS
2002 need to know two things. Firstly, the new Microsoft Content Management catch
phrases are “Microsoft Office SharePoint Server (MOSS)” and “Web
Content Management (WCM)”. Secondly, there are big changes on your horizon.
MOSS 2007 Web Content Management
is an out of the box feature of MOSS. MOSS
itself is built upon the Windows SharePoint Services (WSS) v3.0 foundation
layer, just as SharePoint Portal Server (SPS) 2003 was built upon
WSS v2.0. WSS
is the evolution of SharePoint Team Services (STS).
Its a mouthful of capital letters just to get started. Once you’re ready to digest more, here are some good starting points:
And stay tuned here as we continue to explore the next generation of Microsoft’s
Web and Enterprise Content Management solutions.
Bye Microsoft CMS, Hello MOSS WCM
By Brice Dunwoodie :: Filed Under »
Web CMS
Published: Jul 21. 2006
The Microsoft Content Management Server (MCMS) has been emerging in its new form
over the past two and a half years. Beta 2 is out and we’re told production
will arrive in the environs of late 2006.
As for MCMS 2002 as we have known it? Its gone. Its history.
Its a fading memory.
…well that is, unless you have a very expensive
MCMS web infrastructure that you’ve invested hundreds of
thousands of dollars in. In that case, its high time you sit back and start figuring
out if your organization will jump the gap to the next gen Microsoft offering, or
if you’ll brave the waters of Web CMS
product selection and chart a new infrastructure road map.
Either way, both proud and pained owners of MCMS
2002 need to know two things. Firstly, the new Microsoft Content Management catch
phrases are “Microsoft Office SharePoint Server (MOSS)” and “Web
Content Management (WCM)”. Secondly, there are big changes on your horizon.
MOSS 2007 Web Content Management
is an out of the box feature of MOSS. MOSS
itself is built upon the Windows SharePoint Services (WSS) v3.0 foundation
layer, just as SharePoint Portal Server (SPS) 2003 was built upon
WSS v2.0. WSS
is the evolution of SharePoint Team Services (STS).
Its a mouthful of capital letters just to get started. Once you’re ready to digest more, here are some good starting points:
- MCMS MOSS WCM Overview (PPT by Andrew Connell)
- Enterprise Content Management with MOSS 2007 (webcast)
- Preparing for WCM with MOSS 2007 (webcast)
- Planning Your MCMS to MOSS 2007 Migration
- MOSS 2007 Developer Center (MSDN)
- MOSS 2007 and WSS E-Book (Microsoft Press)
- MOSS WCM Team Blog (not very active)
And stay tuned here as we continue to explore the next generation of Microsoft’s
Web and Enterprise Content Management solutions.
Friday, October 13, 2006
CMS console and JavaScript errors
If you are creating CMS web site so I think you will face this problem, you did every thing but when you try to open the console and switch to edit it gives JavaScript error and doesn't work so what is problem?
Solution
Solution
- open IIS
- expand the your website node
- you will find a virtual site called MCMS
- expand this virtual
- a folder called CMS will be under this virtual
- right click on this folder and choose properties
- copy the path in the Local Path
- click cancel
- right click on the main site and create new virtual directory and name it CMS
- in the directory step paste the path that you copied before
- complete the wizard
- right click on this virtual site and remove the application from it
- Browse your site and enjoy it.
Why This solution?
this Virtual Folder contains all the CMS menus and forms and it has to be part of every CMS site. The trick you do with the Virtual Folder enables you to share the same folder between several sites.
When you create a new CMS site using the CMS this Virtual folder should exist.If you create the CMS site manually , then you'll probably have a problem.
Subscribe to:
Posts (Atom)