From Sense/Net 6.0 Wiki

Contents 1 Sense/Net 6.0 Beta 5 Release Notes 1.1 System requirements (important!) 1.2 Main feature changes 1.3 What to expect in the next release 1.4 Known issues 1.5 Installation issues 1.6 Upgrading from Sense/Net 6.0 Beta 4.3 1.6.1 Breaking changes since Sense/Net 6.0 Beta 4.3

[edit] Sense/Net 6.0 Beta 5 Release Notes

We are proud to finally present you Sense/Net 6.0 beta5, a major feature overhaul over beta43, and hopefully the penultimate beta before the final, stable product. As the focus of this release, we have added a complete ECMS user interface, enabling you to easily create and use workspaces and content lists out-of-the-box to boost your organizational productivity.

[edit] System requirements (important!)

• IIS 7 or 7.5 (Windows Vista / Server 2008 or later)
• Microsoft SQL Server 2005 or later (SQL Express recommended for the source edition)
• Client browser: Internet Explorer 8 or Firefox 3.5

[edit] Main feature changes

• Content Lists (previously Listers) have been improved internally, and augmented with an intuitive user interface.
• Workspaces are now ready for real-life deployment and everyday work.
• We finally implemented indexing and search via Lucene.NET, boosting overall speed by several magnitudes.
• A new permission management system has been added, boosting overall speed and providing full support for ACLs.
• We have re-thinked the Content Type hierarchy, and in the process, removed several long-running bugs from the system.
• We put much work into making Windows authentication function properly out-of-the-box.
• We have integrated Microsoft ASP.NET MVC support into the product.
• New, declarative UI hints have been added to CTDs, helping eschew cumbersome custom Content Views.
• The newsletter module has been factored out of the main product, and will be released as an add-on in improved form in the near future.
• Uncountable bugs have been fixed since the last release.

[edit] What to expect in the next release

• Our context menus, while good enough for everyday use cases, still get most of their content from hardcoded, imperative sources. Expect a fully featured declarative system for controlling Content actions and behavior.
• A comprehensive MIMEtype system is something we have been lacking for too long. It is coming.
• We have finally agreed on a scheme to solve most concerns around content naming, including international characters, spaces, long and short names, etc. It will be implemented in beta6.
• The times of Portlet chaos will soon be over. Pre-configured Portlets and easy Portlet administration are on their way.
• Beauty IS productivity. The all-new user interface eye candy you will find is only the beginning: expect a major design makeover!
• Our goal: Stability. We intend beta6 to be stable enough to become the first Release Candidate.

[edit] Known issues

• The commands "Open in Windows Explorer" and "Edit in Microsoft Office" currently work only in Microsoft Internet Explorer.
• The design has been tested with Internet Explorer 8. Visual glitches may appear under different browsers.
• When using the Portal Remote Control buttons on a node displayed with a SmartPage, you may be erroneously redirected to the SmartPage itself.
• Renaming custom Fields on a Content List may produce unwanted results, and is advised against. As a workaround, delete the Field and create a new one instead.
• List views do not honor the UI hint settings of Fields (eg. currency and percentage symbols aren't displayed).
• Uploading a file with international characters in its name might make the file inaccessible through the portal UI. (This issue is present only when uploading content, not in creation or renaming.)
• When creating a Subpage to a Portlet page under a Workspace, be aware that the Workspace menu is only 1 deep, thus your new page will not be shown. Add a new menu to the parent page, bound to the "Current content", or a static link to the child page.

[edit] Installation issues

• When installing via the Web Deployment Tool under IIS 7.5, set the Identity of the Application Pool from "AppPoolIdentity" to "Network Service", and be sure to give creation rights to the "Network Service" principal in SQl Server.
• When using the source package, please delete the file named "bin" from Source/SenseNet/ContentExplorer. This is an unwanted artifact from our experimental automatic build process, and will be removed in the next service release.
• When using the source package, you will be prompted by Visual Studio about broken source control bindings. Select the answer "Remove source control bindings" to get rid of the problem permanently.
• The source package is ready for immediate running using User Instances with SQL Express. To use it with another SQL Server edition, the connection strings must be changed in the following locations: (Do not forget to manually mount the database, and provide for sufficient rights.)
  • Tools\Install\app.config
  • Tools\Import\app.config
  • ContentExplorer\bin\IndexPopulator.exe.config
  • ContentExplorer\Web.config

[edit] Upgrading from Sense/Net 6.0 Beta 4.3

Looking at the sheer amount of added features since the last major release, we hope it is excusable that upgrade is unfortunately non-trivial. Since our base Content Types, our database schema and our indexing system have changed significantly, Sense/Net 6.0 beta5 binaries will NOT work with a beta4.3 database.

We are hoping to provide a tool for migrating beta4.3-based applications and sites into a beta5 system, in the meantimewe advise the owners of production-level Sense/Net beta4.3 (or earlier) installations to leave their current systems intact, and start experimenting with beta5 features and migration in a safe, sandbox environment.

[edit] Breaking changes since Sense/Net 6.0 Beta 4.3

• Several database schema changes
• Indexing is now done with Lucene.NET. This affects the entire Storage tier of the system.
• The security subsystem has been replaced. The new system is fundamentally incompatible with the old one.
• The Content Type inheritance tree has been fundamentally rebuilt.
• Several interface changes to the class SenseNet.Storage.Node
• The period (.) sign is now forbidden in ContentType names and Field names
• The Lister Content type and Class are renamed to ContentList. All names systemwide, containing the name "Lister" were changed to contain "ContentList" instead.
• All Beta 4 demo collection listing and manipulation functionality (icon views, list views, etc.) have been removed. This code was not production quality, and was never meant for real-life use.
• Changed the SenseNet.Portal.UI.PortletFramework.RenderMode enum type: the value "Default" has been renamed to "Native"
• The property SenseNet.Portal.UI.PortletFramework.ContextboundPortlet.RenderMode has been removed
• The method PortalActionLinkManager.GetAvailableActions now returns an IEnumerable<PortalActionLink>
• The CTD xml schema has changed: "Action" elements now use an Add/Remove/Clear format similar to that used in web.config. (Remove and Clear are for future support, and are not implemented in beta5)
• JavaScript is now loaded in SenseNet PortletPages before the DOM. This will cause problems with third-party JS files that contain imperative commands to run at load time.
• The class SenseNet.Services.Content has been moved to SenseNet.Services.ContentStore.Content
• The Content Type "GenericRSSApplication" has been renamed to "RSSApplication"
• The "Motto" field removed from the Workspace Content Type
• Removed the "RSSFeed" Content Type
• Removed all MIMEtype-specific document types (eg. WordDocument, ExcelDocument, etc.)
• Removed all beta4 Workspace-specific collection types (eg. MemoCollection, etc.)
• Removed the "WorkspaceSmartFolder" Content Type
• Removed the "CountdownContent" Content Type
• Removed the "CrawlSet" Content Type
• The way how Browse SmartApplications are resolved has been changed: the Browse application is no longer the node under the Apps folder named after the type, but a child of that Node explicitly named "Browse"
• All "WhoAndWhen" Fields and Field Controls have been removed from the system.
• Removed several unused or rarely used Fields from the File, Site and User Content Types
• The DisplayName (GenericContent) and PageNameInMenu (Page) Fields have been permanently removed
• The NewsLetter functionality has been removed from the product in its entirety
• The old, ExtJS-based DocumentLibrary portlet has been removed