This project has moved and is read-only. For the latest updates, please go here.

SenseNet 6.3.1 Community Edition

Rating: No reviews yet
Downloads: 2329
Released: Aug 11, 2014
Updated: Aug 12, 2014 by tusmester
Dev status: Stable Help Icon

Recommended Download

Application sensenet631-community-webpi
application, 74379K, uploaded Aug 11, 2014 - 1367 downloads

Other Available Downloads

Source Code sensenet631-community-source
source code, 98925K, uploaded Aug 11, 2014 - 716 downloads
Source Code EnableFilestream.sql
source code, 16K, uploaded Aug 11, 2014 - 246 downloads

Release Notes

Sense/Net 6.3.1 Community Edition

Sense/Net 6.3.1 is an important step toward a more modular infrastructure, robustness and maintainability. With this release we finally introduce a packaging and a task management framework, and the Image Editor that will surely make the job of content editors more fun.

Please review the changes and new features since Sense/Net 6.3 and give a feedback on our forum!

Main new features

  • SnAdmin (packaging framework)
  • Task Management
  • Image Editor
  • OData REST API improvements


We created a packaging framework that will handle core product and 3rd party application updates as well in the future. For our Enterprise customers we will provide update packages so they do not have to perform manual upgrades. Developers can also make their own upgrade packages for their 3rd party solutions.

Task Management

This is a new framework that supports delegating background tasks to external executor agents. Operators can manage resources in a more flexible way and the tasks are separated from the web process to aid robustness. Enterprise customers have the possibility to build an external agent grid from virtual machines, even in the cloud.

Image Editor

This new feature makes it easy to edit images (rotate, crop, resize or modify them with many filters) before uploading them to the Content Repository.

OData REST API improvements

The OData REST API lets you talk to the Sense/Net Content Repository using standard tools like jqGrid or a custom AJAX solution. In previous releases you had to address individual content by their path. This could cause a problem if your solution involves changing the path during the process - e.g. moving or renaming the content. From now on you can use the content id for all types of OData requests that address individual content.
How to install
How to install Sense/Net

Detailed changelog
Change log 6.3 - 6.3.1

Reviews for this release

No reviews yet for this release.