I continue to hear that competitors are spreading FUD that Microsoft CMS is dead. This is far from the truth and Content Management has a big future in Microsoft plans.
We know that from talking to our customers and partners there is great interest in having our web content management and portal strategies more closely aligned, and for this reason the CMS development team has moved into the Information Worker organisation. So the next version of CMS will be architecturally consistent with the SharePoint products and technologies. Whilst it is too early to discuss plans what packaging/licensing and specific functionality will look like, we are committed to providing customers with solutions that enable them to create, share and manage all types of content in their organization.
One of the key reasons that the CMS plans are being kept quiet is that CMS is now an important component of Office 12 and so its not appropriate to discuss CMS vNext in isolation. Office 12 is still deep in development but as soon as our intentions are in stone, the IW team will begin communicating publicly the various pieces of what we have in mind for the complete Office12 wave of products - and that will include details about CMS vNext.
Until then customers and partners can be confident that CMS2002 is hugely successful and that there is considerable investment in CMS futures ... for evidence check the following open job positions to join the CMS vNext team as program managers, developers and testers:
8 Comments:
http://www.crn.com/sections/breakingnews/dailyarchives.jhtml?articleId=60403652
parag sinkar
http://www.crn.com/sections/breakingnews/dailyarchives.jhtml?articleId=60403652
parag sinkar
Can you comment on the plans MS will make to ensure future CMS development will fully support browsers other than Internet Explorer? We increasingly have users in our team on varied platforms - but more to the point, migrating to Firefox and other browsers (on the Applemac it seems to be Sarfri). They want to author - and many areconcerned about the limitations in 2002. So - full clients in MSCMS?
With CMS2002 - you should use the free Telerik control to work on alternative browsers.
If you want to extend what Telerik have done you should contact them - im sure they would be interested and helpful.
On the otherhand, Microsoft has done an excellent job on API for MCMS. We need that type of thought put into the authoring controls.
Post a comment