News in Content Studio version 5.7 Sp 1

Release date: January 2016

  • New functionality
    Support for TinyMCE Html WYSIWYG-Editor in the The New Editorial Interface aka. CSEdit
    We have added support for the popular TinyMCE Html WYSIWYG-Editor, effectively replacing the old Telerik editor. You can add User-controls and set properties directly in the editor and browse for files and documents using the built in browse dialog.
    Improvements to asynchronous Event Actions
    We have improved the asynchronous Event Actions system by adding support for re-scheduling of failed jobs. It is also possible to add asynchronous event actions jobs programatically.
    A plug in-based system for collecting information from Content Studio and other sources and forward it to sources of your own choice, is available. It is very suitable when there is a need to build an external search index based on data from Content Studio.
  • Improvements and fixes
    Improvements to Ept schemas
    We have improved the Xsd-schema so it can be used for validation. Developers now can save modified versions of an Ept schema. in earlier versions of Content Studio Ept schemes could only be saved automatically.
    Fixed: Cannot restore some documents from the recycling bin.
    Some type of documents cannot be restored from the new Recycling Bin. This problem does not affect uploaded files and Ept documents.
    Fixed: Cannot rename some root categories.
    If a root category has a child category with the same name, it cannot be renamed.
    Fixed: Cannot have duplicate name on a list even though the group names are different.
    The first version of the new Editor interface supported a plain structure of lists where the names must be unique. Later when lists could be grouped it would have been natural for list names to be unique within a group. This is now true in this release.
    Fixed: Cannot rename of move folders on the ReFS file system.
    Windows has introduced the new file system 'Resilient file system' or ReFS with server 2012 and this file system will be default in Server 2016. One of the differences between NTFs (the current file system) and ReFS is that transactions are no longer supported. The causes problems for the Content Studio API:s that rename or move Categories and Units. These API:s have been rewritten so that ReFS can be used as well.
    A number of minor bugs and issues have been fixed

News in Content Studio version 5.7

Release date: April 2015

  • New functionality
    New design on the New Editorial interface
    We have updated the design of the New Editorial interface to give it a new fresh look and to make it more intuitive to use for editors.
    A new image scaling and cropping functionality
    Content Studio version 5.7 takes image handling like cropping and scaling to a new level. It makes it simple to adjust an image just by query string parameters in the image link. Use this functionality to adjust the image size depending on the device used. You can even crop the image using a set of query string parameters and optionally activate the face detection functionality to have the image cropper to focus on faces in the image.
    Upload images directly from the browse dialog in the New Editorial interface
    When selecting an image via the browse dialog in the New Editorial interface you can now upload a new image, depending on the device, take a new picture with the camera, upload, and eventually select it. That is perfect for editors that like to publish news directly on site.
    Versioning support in the New Editorial interface
    You can now preview and optionally restore older document versions directly in the New Editorial interface.
  • Improvements
    Improved recycle bin
    In the old recycle bin for documents deleted documents were still connected to their category. This made it impossible to delete an empty category when deleted documents connected that category still existed in the recycle bin. Now deleted documents are moved out of the original category but still "remember" their original category so that they can be restored. If the category has been deleted a document can still be restored if a new category with the same name and type is created.
    You can now preview images in the recycle bin just like in the Windows Explorer. This is true both in the old admin interface and in the New Editorial interface.
    Improved full-text search
    For historical reasons the document full-text index search did not include the document title. This has now been fixed and the document title has been more important for the search result.
    Improvements to the Site copy utility
    The site copy utility has been adjusted for the new Recycling bin and document search improvements. It now also handles document version numbers correctly. After installation the new copied site document has their version numbers reset to the initial values. As before only the latest version is copied into the dump. Documents in the recycle bin are no longer copied into the dump.
    Improvements to VSI (Visual Studio integration)
    You now find VSI in the Visual Studio Gallery . You can develop directly in Visual Studio 2010, 2012 or 2013. Save your changes directly to web site or the staging server remotely or in your local network. You can now change properties for Units, Categories and Documents. Support for Rename, Delete and Move operation on Categories and Units has been added and the performance has been improved by loading objects in the background. Login for remote sites has been improved and Visual Studio now asks for credentials for the remote site when needed.
    A number of minor bugs and issues have been fixed

News in Content Studio version 5.6 Update 1

Release date: September 2014

  • New functionality
    Associated lists in the New Editorial interface
    One or more lists can be associated with a menu item to define if and how documents can be created or connected to that menu item. This is a developer functionality and can be reached in the document hierarcy dialog in the Content Studio administrative interface.
    Associated lists adds more strict rules how document can be created, removed and moved in the site tree.
    Create new documents from the site tree in the new edtiorial interface.
    Create a copy of a document in the new editorial interface
    Fixed problems in the ImageDialog and LinkDialog components
    Improved search functionality in the new editorial interface
    Event action improvements
    OnDocumentRestore sync event handlers can now be used to turn on the <Published> flag in the same way as OnDocumentApprove have been able to do since version 5.2
    Other bug fixes and minor improvements

News in Content Studio version 5.6

Release date: May 2014

  • New functionality and improvements
    New Editorial interface (aka CSEdit)
    The new Editorial interface was built from the ground and up to support a variety of modern browser on desktop computers, smartphones and tablets. Besides a good Web browser support the goal has been to focus on site content maintenance rather than administrative, development and design tasks. During the development process the Content Studio team has tested the interface and its functionality on Internet Explorer 10+, Chrome, Firefox and Safari Web browsers on Windows 7+, Mac and Linux Ubuntu desktop operating systems. In parallel tests have been made on Windows RT, Android and IPad tablets as well as IPhone, Windows Phone 8 / 8.1 and Android smartphones.
    After upgrade the new Editorial interface is not enabled on existing sites and is an option when adding new sites. For more information on how to activate the new editorial interface on an existing site see How to enable the new editorial interface.html
    Expose categories as lists
    Content Studio categories are not exposed directly in the new editorial interface. Instead lists are used. A list represents a category and several lists (filtered or not) can represent a single category. Typically a developer only exposes EPT and File categories as lists in order to hide non-content related parts of the Web site for editors.
    A new browse dialog
    The legacy browse dialog in Content Studio only worked in Internet Explorer. To overcome this problem the modern editorial interface now has a completely new dialog that is based on the new list functionality. This dialog is designed to work with all modern browsers on computers, tablets and smartphones.
    Multiple asynchronous file upload
    The new editorial interface supports multiple file upload with Html5 technique for browsers that support it. I addition to this Content Studio checks if the files are allowed to upload before any bytes have been transferred to the server. Very useful when uploading large and/or many files.
    Server controls are updated to support the new editorial interface
    In earlier version of Content Studio some of the included server controls only worked with Internet Explorer. These controls interacted with the user in some way - through a browse dialog or a WYSIWYG editor. The controls ImageDialog and LinkDialog have now been updated to use new dialogs in the new interface. They still works as before in the legacy Content Studio interface.
    New or updated server controls
    Image dialog
    Link dialog
    Load user info cookies
    Twitter timeline - replaces the outdate Twitter Profile Widget component.
  • Improvements
    Improved support for Internet Explorer 11
    Internet Explorer 11 that is included with Windows 8.1 and offered as an upgrade option to Windows 7 is a major browser upgrade to meet the latest web standards. This has led to a number of incompatibilities with older web sites and application. Version 5.6 fixes many of the issues of this kind present in Content Studio.
    Improved version of VSI (Visual Studio Integration)
    Better integration and now capable to debug remote sites
    Improved version of Site Copy utility
    Site Copy utility now supports the new list functionality.
    Fixed errors in the Site Copy utility
    The new Site Copy utility included in Content Studio 5.5 had som bugs that could cause it to fail. These have been fixed.
    Fixed errors and added improvements in the Image dialog and Link dialog components.

News in Content Studio version 5.5

Release date: Q1 2013

  • New functionality
    Support for relocating documents
    It is now possible to move documents from one category to another category if the categories are compatible with each other. The document's source category and the destination category must either be of the same type (e.g. xml documents or files) of compatible with each other (e.g. Text with Meta data and Html with Meta data). This new functionality should be used wisely since it can easily cause problems on an active web site - e.g. broken links and not found user controls that can cause compile errors.
    Support for relocating categories
    It is now possible to move categories from one unit or category to another unit or category. Just like the document relocation functionality this can easily cause problems on an active web site and should be used with care by knowledgeable developers.
    A new and improved Site Copy Utility
    The site copy utility has been rewritten from the ground up. It now supports an option to copy well-known and/or domain level security entries and now has an easy-to-use wizard interface.
  • Improvements
    Improved support for Internet Explorer
    Internet Explorer 10 that is included with Windows 8 and offered as an upgrade option to Windows 7 is a major browser upgrade to meet the latest web standards. This has led to a number of incompatibilities with older web sites and application. Version 5.5 fixes many of the issues of this kind present in Content Studio.
    Improved integration with Telerik rich-text editor
    Content Studio 5.4 and later uses Telerik rich-text editor to provide a browser independent rich text editor component that can be used in Edit Templates. The integration of this third party product enables an editor to include standard user control components into the document data (e.g. a list of news or the latest blog items) and set properties in a simple and intuitive way. This integration is now improved and extended.
    Many minor bugfixes and improvements.
    A number of issues that was not included in version 5.4 have been added to further improve the user experience and add stability to the product.

News in Content Studio version 5.4

Release date: September 2012

  • New functionality
    Cross browser support

    Integration of the Telerik Rad Editor
    Content Studio can now integrate with the Telerik Rad Editor for ASP.Net. This popular rich-text editor for Web-forms supports all major modern web browsers. This means that you can add this editor as a replacement for the Content Studio webitor, which only supports Internet Explorer, in an edit form to let site editors create and update documents with rich text content. It fully integrates itself with EPT and even lets the user include any user-control in their documents. The Telerik Rad Editor is a part of the Rad Controls for ASP.NET Ajax. License to use Telerik Rad Editor must be purchased directly from Telerik. This new functionality has been tested on Internet Explorer 8 and later, Firefox 14, Safari 5.1 or a recent version of Chrome.

    Extended versioning

    Some document properties have not followed the document version in earlier versions of Content Studio. A number of them have now been integrated into the versioning system:

    • Document DOC-type
    • Directives
    • Title
    • Publish date
    • Archive date
    • Virtual path
    • Body properties
    • Published
    • Description

    Renaming of units and categories

    It is now possible to rename categories and units via a new menu option in the folder tree. This functionality requires that Content Studio runs on Server 2008 / Vista or later.

    Support for Swedish e-legitimation

    New control: EIdentityLogin
    This control makes it possible for web site users to logon to a website that uses Svensk e-identitet as identity service provider. The control displays a login form and integrates with .NET forms authentication. To use this control one need a contract with Svensk e-identitet that must be acquired separately.

    Integration with social medias

    New control: TwitterProfileWidget
    This control makes it easy to display tweets from a specific account on a website.

  • Improvements and fixes
    Improved validation for XHTML 1.1.
    Support for Windows Server 2012 and Windows 8.
    Fixed problems when using Internet Explorer 10.
    Fixed problems in the subscription service.
    Fixed problems in the administrative interface.
    Fixed many errors in the technical documentation.
    Added missing texts and labels in the administative interface for Norwegian and Finnish.
    Added some missing properties for Event Actions and the built in handlers
    Improvements in the installation program
    Support for installing and upgrading CS using an SQL logins.
    Support for SQL logins for the runtime.

News in Content Studio version 5.3 Sp 1

Released December 2011

  • New functionality
    Integration with social medias

    New control: FaceLikeButton
    Make it easy to share content with friends on Facebook.
    The Like button lets a user share your content with friends on Facebook. When the user clicks the Like button on your site, a story appears in the user's friends' News Feed with a link back to your website. When your Web page represents a real-world entity, things like movies, sports teams, celebrities, and restaurants, use the Open Graph protocol to specify information about the entity. If you include Open Graph tags on your Web page, your page becomes equivalent to a Facebook page. This means when a user clicks a Like button on your page, a connection is made between your page and the user. Your page will appear in the "Likes and Interests" section of the user's profile, and you have the ability to publish updates to the user. Your page will show up in same places that Facebook pages show up around the site (e.g. search), and you can target ads to people who like your content.

    New control: FacebookOpenGraphTags
    Describe your web page to Facebook.
    Open Graph tags are <meta> tags that you add to the <head> of your website to describe the entity your page represents, whether it is a band, restaurant, blog, or something else.

    Integration with Google analytics

    New control: GoogleAnalytics
    Google Analytics Tracking Code.
    Stay in the Loop!
    Subscribe to our changelog.
    Asynchronous Tracking Forum.
    Collect visitor data for your website using the Google Analytics tracking code. The tracking code works by the inclusion of a block of JavaScript code on your website pages. When visitors to your website view a page, this JavaScript code executes the tracking operation for Analytics. Data about the page visit is collected and sent to the Analytics server through a list of parameters attached to a single-pixel image request. Without any customization, the tracking code snippet supplies your Analytics reports with a wide variety of data about your website pages, your visitors' loyalty, AdWords traffic sources, and more. If you want to use Analytics for other types of web analytics—such as e-commerce tracking or tracking visitors across domains—you will need to customize the tracking code.

    Support for Norwegian
    Improved support for making own Content Studio API extensions
    Programmers can now extend the Content Studio API to i.e. query the site database for data, thus exposing new site functionality.
  • Fixed problems
    Fixed sorting problems
    A few minor problems fixed
    Webitor control
    Fixed problems with Internet Explorer 9
    Other minor problems fixed
    Improved designer support
    A number of issues fixed in design mode
    Improved synchronization of EPT-documents
    Fixed problems locking our users

News in Content Studio version 5.3

Released October 2010

  • New functionality

    Event added: OnDocumentPreview.
    This event fires when a document is previewed in Content Studio and can be used to fetch content to be previewed from an other source than Content Studio. this type of event handler can return a custom identifier that Content Studio passes on the presentation template used. The presentation template can then fetch the content from an external content store and display it.
    Using this event and other synchronous events, Content Studio can be used as CMS for CMS independent web sites.

    Event added: OnDocumentPreviewDispose.
    Fires when Content Studio closes the preview dialog and cleans up used resources on the server. Used in conjunction with the OnDocumentPreview event to clean up resources in an external content store.

    Event added: OnDocumentRevisionRestore.
    Fires when an older revision is restored. This event is useful in a scenario when Content Studio synchronizes document content to an external storage. When a revision is restored the draft content of the document is overwritten with the older revision. This causes that the draft version of the document is out of synch in the external storage. Use this event to correct this problem.

    Multiple synchronous handlers for the same event and category.
    You can now have more that one event handler that fires on the same event and category. Even though it was possible to assign multiple event in earlier versions of the product only one of them fired. When using multiple event handlers you cannot control the order in which they are fired meaning that these handlers must be independent of each other.

    It is now possible change document meta data and content in OnBeforeDocumentSave handlers.
    This is a very powerful new feature; it allows you to change the properties and event the content of a document before Content Studio saves it.

    More document properties are available in handlers.

    Easier development and testing of synchronous event handlers.
    Developing and testing synchronous event handlers has been difficult because the complex data they receives from Content Studio. Often developers found themselves debugging their components remotely against the web server - an tedious and time consuming task. By using the new Spotlijster library it is now possible to "mock" event actions data and this have the test project calling the event handler in a controlled way. The EventHandlers.Spotlijster.dll assembly will be included as a part of the Content Studio SDK.

    Support for custom configuration files in synchronous event actions handlers.
    When a Content Studio synchronous event handler needed access to a configuration file, the most obvious place was the CSServer5.config. However placing custom configuration data in this file affects the entire Content Studio server and this file is overwritten each time Content Studio is upgraded. A new API on the base class that synchronous event handler inherit from can return this custom configuration file.

    New view: My Recycling Bin

    In earlier versions the recycling bin was shared between all users. The default view now lists the files that are delete by the caller only. This improves performances in scenarios where a large number of documents is in the recycling bin. The old "global" view is accessible for backwards compatibility.

    Support for virtual file systems

    The new virtual file provider makes it possible to save documents directly in the file system rather that in Content Studio. The documents stored will still be available in Content Studio and can be saved and deleted as usual. The main purpose with this provider is to help those customers that have a huge amount of data in uploaded files and images. This will eventually result in very large database files and problems with backups. By using the virtual path provider, those files now can be stored directly in the file system thus reducing the size of the database files.

    Support for custom control editors
    Support for cached server data
    Some often read server data very seldom changes is now cached for better performance
    • Site list - an expensive method called whenever a user enters Content Studio
    • Connection string information
    Improved Ept datasource control
    A number of new properties have been added:
    • CheckForPublishStatus - turning off publish date checking can improve performance.
    • PermissionToCheck (BROWSE or READ)
    • RandomSortOrder
    • Aggregation
    The control has been better documented for improved usability.
    Improved installation program
    New versions of Sql Server cannot be guaranteed to be 100% compatible with a certain version of Content Studio. For this reason earlier versions of the installation program did not accept newer version of Sql Server than the newest version available when the Content Studio distribution was compiled. This behavior has now changed; instead of just refuse the newer, unverified version of Sql Server, the installation program now displays a warning allowing the caller to decide whether to install on the unverified Sql Server version or not.
    A new and improved version of the Visual Studio integration plug-in (VSI)
    The VSI - plug in now supports Visual Studio 2010 and is completely redesigned. This gives a much better performance.
    New improved webitor server control replaces the older AS-component.
    The most significant improvement is that the new Webitor supports a new setting, UseSoftLineBreakInDiv, that determines whether a carriage return command within a <div> section should render a soft line break <br /> or a new paragraph <p>.
    Improved performance for custom views.
    A custom view makes it possible, when a category is clicked in the Content Studio administrative interface, to show custom document rather than the regular list of categories and files. In older versions of Content Studio the regular content of the category was loaded silently in the background even if not used for anything. This has now changed in order to improve performance for custom view categories.
    Improved spell checking.
    In earlier versions of Content Studio the list of available dictionaries was determined from a list stored in the database. In version 5.3 the list is determined by the actual dictionaries found in the Spellcheck/Dictionaries subfolder on the Content Studio administrative site. The spellchecker is delivered with dictionaries in
    • Danish
    • English - GB
    • English - US
    • Norwegian
    • Russian
    • Swedish
    more dictionaries are available for download at
  • Fixed problems
    Link dialog - difficult to understand terms for targets
    The list of targets has been completed with more easy to understand names, e.g. _blank now is New window
    The Recycling Bin view can be slow
    When the recycling bin has many documents, it can be very slow. The listing algorithm has now been improved and the default view is now My Recycling bin which often contains much less documents than the full view.
    The menu API does not return custom data
    This API has been completed with this data field.
    Problem with encoding of server block tag attributes in the Webitor.
    New improved algorithm for server block encoding
    Improved support for Ept document caching
    An ept document can now be whole-side cached.
    Site copy utility cannot correctly handle virtual url:s
    Fixed in CS 5.3
    API MenuCreator.ListDocuments does not ignore the presentationTemplateId
    According to the CS 5.2 documentation the presentationTemplateId parameter should be ignored, but in CS 5.2 an CSDocumentNotFoundException is thrown when an nonexisting indentifier is supplied. This has now been fixed and the argument is truly ignored.
    Site Content manager cannot handle session time outs
    If, during a file synchronization operation, an error or warning dialog is displayed waiting for the caller's response, and the session eventually times out, the entire operation fails with Session is invalid exception. This problem now has been fixed.
    VSI-safe Guid-based file names was not always safe
    Visual Studio does not accept file names that begins with a number. In CS 5.2 a change was made that should guarantee that a Guid-based file name always begins with a letter [A - F]. However, this did not work correctly but has now been fixed.
    Content Studio sometimes asks the user to remove a user control in use
    This problem has now been fixed.
    Wrong pipe-line mode when upgrade or new web site.
    Sometimes classic pipeline mode is forced when during upgrade or when a new CS web site is installed even though Content Studio uses integrated mode. This causes the web site to stop working.
    This problem occurs if the namespace declaration has been removed from the Web.config file and has been fixed in CS 5.3.
    EptHyperLink control
    Fixed problem with the alternate text property.
    API: SessionId.Ensure method
    This call did not work according to the documentation in CS 5.2
    Documentation fixes
    Completions and corrections:
    • Several spelling errors corrected.
    • Some api:s has insufficient or none return value documentation.
    • Some method had no documentation of possible exceptions.

News in Content Studio version 5.2 SP1

  • New functionality
    Event Actions
    A new set of base classes added that makes it possible to create synchronous handlers that performs custom, policy based validation.
    For more information see the Creating a synchronous event handler article.
    A new library of base classes to use as base for custom Asynchronous event handlers.
    For more information see the Creating an asynchronous event handler
    Improved base classes for handling the OnDocumentMoveInHierarchy synchronous event
    A new flag is available in the OnDocumentApprove synchronous event that makes it possible to specify that restored documents will be published when re-approved. By default all deleted documents are marked as being "WithDrawn" but this flag overrides this behavior This functionality is only available on a synchronous event handler object.
    Support for custom property editors in the properties interface for user/server controls
    This is done by setting the EditorAttribute to class that inherits the WebUITypeEditor class.
  • Fixed problems
    Some asynchronous events do not fire
    For more information on this problem see our knowledgebase article Some Asynchronous Event Actions do work in version 5.2
    Performance problems with menus
    Bad performance when XML based menus are rendered, the optimization settings CurrentDocument, PerformAccessCheck, UsePublishStatus had no effect.
    Impossible to set an empty description on uploaded files
    In earlier versions there was no possibility to set an empty description on an uploaded file. If an empty description was provided the document title was used instead.
    Url rewriter
    Fixed: When using a custom Url-rewriter that rewrites query strings, the properties RootDocumentId, RefId and EditId could not be read.
    Internet Explorer 8: Alert message boxes do not work
    Fixed: On Windows Vista with protected mode deactivated, the javascript function alert() that displays a message box, does not work in popup windows.
    Read more
    Fixed: A number of JavaScript errors in Internet Explorer 8.
    Installation program fixes
    Fixed: Cannot set LogonAsService user right for runtime account on 64-bit systems.
    Fixed: Content Studio server event log is not removed during uninstall.
    Fixed: During upgrade, the installation program does not check for databases in old compatibility mode.
    Fixed: During upgrade, database upgrade fails for databases that was upgraded from SQL Server 2000.

News in Content Studio version 5.2

  • Breaking changes
    SQL Server 2000
    Starting with Content Studio version 5.2; Sql Server 2000 is no longer supported. Today almost every customer uses SQL Server 2005 or later and in order for Content Studio to benefit from the many improvements in SQL Server 2005 support for the older SQL Server versions has been dropped.
    For developers
    Most API that used integers as identifiers for ConnectionId, SessionId, UnitId, CategoryId and DocumentId have been changed. Each one of these identifiers have now their own data types. Existing code might need to be changed or recompiled in order to work with Content Studio 5.2. This change has vastly improved the possibility of importing documents and folders from another site.
    The Event Actions event handler interfaces have been changed and all existing event handlers must be changed and recompiled. This breaking change was done in order to make custom event handlers continue to work between different versions of Content Studio.
  • New functionality
    A new, integrated, subscription engine that makes easy to create and administer newsletter subscriptions on documents.
    Virtual Url support
    Full support for virtual url:s on all levels. This makes it possible to give any document a unique address. Instead of you now can give a virtual url such as Products and be able to use the url In IIS7, Integrated mode, the address can even be without file extension These documents do not need to exist physically.
    Extended security support
    In earlier versions, under some conditions, you could bypass the Content Studio permissions on a document if you knew the physical file name ex. and the document was only protected by a Publish Date in the future or if it was archived. In CS 5.2 and in IIS 7 Integrated mode (Server 2008 / Vista) all requests are directed through ASP.NET and controlled by Content Studio API.
    Changes in Default.aspx
    The Default.aspx file now used only to provide the default document functionality and all logic in this file has been moved to an ASP.NET HttpHandler to improve performance and security. In older version both default.aspx and the actual document had to be executed.
    Improved support for accessing documents based on their file names
    Full support for accessing documents by their file names instead of by their numeric identifier. It is now possible to change the file name of an individual document or set a rule that specifies that a document's file name should be the same as its name (title).
    Content Studio has been heavily dependent on the numeric identifier of the document (DocumentID) but since you now can control the file name of the document and access it using the file name instead of the identifier. This will eventually vastly improve the possibilities to reuse documents and application between Web sites.
    A new EPT data source with filtering capabilities, is included, thus making it possible to bind any data-aware standard ASP.NET control to EPT data.
    Express edition
    The new, free Content Studio Express edition for small web sites, is finally here!
    Fulltext search
    Support for change tracking with the full text indexing and newly approved or changed documents are searchable within a few seconds. In earlier version of the product an incremental re-indexing was needed in order to index new and changed documents.
    Event Actions
    Four new server side events added:
    OnDocumentPublish, OnDocumentArchive, OnDocumentUnPublish and OnBeforeDocumentSave
    Two new server side events related to Subscription added:
    OnDocumentSubscription and OnDocumentTestSubscription
    Support for viewing the job queue on a category.
    Support for stopping an queued event from executing.
    PDF Server
    The support for PDF Server integration is back in Content Studio 5.2.
    A standalone PDF Server that can integrate with Content Studio will be released later.
    New Server Control library
    A new Server Control library has been added that contains a number of important controls. .NET Server Controls will eventually replace the older AS Component and Live Object technology developed for the 3.x and 4.x Content Studio platforms.
  • General improvements
    Improved user interface
    Syntax highlighting in the Webitor code editor.
    Support for minimized and maximized windows in the administrative interface.
    Support for editable regions in Server Controls.
    ASP.NET integration
    Improved support for using Server Controls and User Controls in Content Studio.
    EPT fields presentation in presentation template is now based on native ASP.NET technology instead of the older Active Scripting technology. This makes it much easier to work with User Controls and Server Controls within EPT.
    Service Manager
    The Service Manager has been improved. It is now uses an internal queue system that reduce the waiting time for events to be carried out on server with may Web sites.
    Event Actions
    The Event actions programming interfaces have been moved to a separate assembly. Custom Event Actions event handlers no longer need to be recompiled between different versions of Content Studio.
    Synchronous event handlers now can obtain information on the document that triggered the event. In earlier versions this would lead to a dead-lock situation.
    Installers can now choose between the TCP and IPC protocol.
    Bugs and other issues connected with IIS7 have been fixed.
    Support for IIS integrated mode in IIS7 on Vista and Server 2008.
    Changing between IPC and TCP communication is now a simple setting in Web.config.
    For developers
    The new data types DocumentId, CategoryId and UnitId makes it possible to refer to documents, categories and units based on their file names, virtual paths or identifiers. This makes it far more easy to move documents or solutions between sites since the numeric identifier dependency can be eliminated.
    GetHashCode and GetHashCodeForField methods on EPTXmlParser and its inheriting classes now generates a value based on the content of the document. This makes it much easier to compare the content of two EPT documents with each other.
    SyncronizedEPTDocument only saves changed fields in order to work better with server side validation.
    A new friendly programming library SyncEvtHand makes the task of writing synchronous server side event handlers far easier.
    A separate library that acts as a base class for the new Subscription event handlers makes it easy to write your own subscription service logic.

Changes between Content Studio version 5.2 Beta 3 and 5.2 RC 1

  • Improvements
    • Support for IIS Integrated mode in Windows Vista/Server 2008
    • Improved installation program.
  • Bug fixes
    • Installation problems on Server 2008 fixed.
    • General bug fixes.

News in CS version 5.1

  • New functionality
    • All the code in the core are now using .NET. This will make the core more robust, reliable and less dependent on older system components. Also, it fully support the 64 bit operating systems.
    • All of the remaining AS components that did not make it to version 5.0 are now included. [Documentation]. However, the few components that work in conjunction with the PDF Server are scheduled to version 5.2. 
    • The Spellchecking module and its corresponding component are available. This functionality checks the spelling of published texts using dictionaries in simple text formats. [Documentation]
    • The Track changes module and its component are available. Track changes makes it easy to detect and trace changes between different revisions of a document. [Documentation]
    • The Workflow Server engine is available together with its accompanying AS components. The Workflow Server is a powerful mechanism to set up workflow definitions for document management. Compared with the workflow engine of version 4, the capabilities have improved. [Documentation]
    • New managed engine for image processing. [Documentation]
  • Search engine improvements
    • New managed engine for extended search result.
    • Full-text searching has been radically improved for customers running SQL Server 2005
    • For customers running SQL Server 2005, the Full-text search now supports the FREETEXT clause, for simple searching sensitive to forms of words and synonyms. Earlier only CONTAINS was supported (advanced, precise searching). Also, support for language sensitive searches (language must be specified for word forms and synonyms). [Documentation ]
  • General improvements
    • Optimized XML filter queries [Documentation]
    • Radically improved performance for large menu structures. This requires SQL Server 2005.
    • User controls now can act as presentation templates. It is now possibly to use User Controls in EPT, thus making them available to editors on the Web site just like the old Live Object technology.
    • User Controls can be used for including documents, instead of using the Insert document component. This improves performance.
    • Improved support for User Controls and Server controls. Installed server controls now turns up in the tool box, making them easy to use.
    • The administrative interface, including edit templates, is now supported by the caching engine within .NET. Caching is not enabled by the installation program, but can manually be activated using the IIS Management console.
  • Security enhancements
    • Security: Support for restriction of file types per category.
      Restrict what type of file (based on its extension) that can be stored in a category. For example, you now can set that a category only can contain PDF-documents and Word-documents or that a category only can contain user controls (.ascx - files). As in earlier versions, the global right to write code is required to write any server side code or upload any file that can be executed on the server side such as ASP or ASPX files. [Documentation]
    • Security: EPT document file extension now defaults to .ept.
      In Windows Server 2003, By changing the file extension for EPT documents to .ept you can prevent the EPT document content to be displayed in clear text even if there is no presentation template connected to it or if the underlying file name should be known. The Web server in Windows Server 2003 and later will by default ignore this file extension. It is possible to use the old .xml extension but we recommend this to be avoided. [Documentation]
    • Security: Built-in support for cookie encryption, thus making sensitive data unreadable off site. [Documentation]
  • Improved SDK and documentation
    • The CS5 Technical Overview has been completed.
    • The Knowledgebase is now included
    • All AS components are documented

News in version CS 5.0 (from beta version 1)

  • Support for non Windows authentication. It is possible to support catalogs such as NDS and ADAM, as well as custom database and catalogs. Integration with ASP.NET Forms login. Requires writing your own custom membership provider and authentication module. [Documentation]
  • Support for ASP.NET Themes and skins for user controls [Documentation]
  • Support for 32-bit IIS 7 (Vista / Server 2008)
  • Content Studio API is available via Web Services. The classic Web API is still available for backwards compatibility [Documentation]
  • Support for Web Parts Create WebParts or consume WebParts directly for ex. Microsoft Sharepoint Portal Server. Visual support using drag & drop technology. Built-in web part provider. New user controls for web parts makes it simple to create portals pages. [Documentation]
  • Visual support for Master pages and Content pages. Master pages can be combined with the presentation template technology. [Documentation]
  • Graphical support for server and user controls All controls can use drag & drop technology. New toolbar for server controls with a possibility to add your own controls. Full support for editing control properties.
  • Support for application cache in ”Insert Document” components. High performance thanks to the in-memory-cache technique.
  • Support for IDN (International Domain Names)
  • Optimized performance with a new cache mechanism. Document retrieval cache (DRC) lessens the load on SQL Server in all page requests.
  • New improved installation program
  • Improvements in the user interface. Browse functionality on all properties and directives that handle URL:s and document/category identifiers. Address field in both the web view and the preview.