Skip to content

This release is mostly a technical update. We started working on package install with .Net Core version of sensenet and set current sensenet user based on the .net identity. - this will come in a future release.

Feature

Installation

To get started please follow the instructions in the Install sensenet from NuGet article.

Assets 2

@VargaJoe VargaJoe released this Nov 6, 2019 · 31 commits to master since this release

This release is mostly a technical update. We started working on converting the OData layer from .Net Framework to a modern .Net Standard solution. These are only the first steps, the changes can be observed only in source code. The goal is to let new .Net Core projects use our NuGet packages and install sensenet seamlessly - this will come in a future release.

To get this update on an existing repository, you need to execute a patch. Please download it from the assets list and execute it using SnAdmin on your machine first. It will take some time because we will rearrange metadata in the database during the patch.

Bug fixes

Installation

To get started please follow the instructions in the Install sensenet from NuGet article.

Assets 3

@VargaJoe VargaJoe released this Oct 10, 2019 · 158 commits to master since this release

This release marks a major milestone for the sensenet Content Repository. We refactored our data storage layer to meet the requirements of other (non-relational) data storage platforms and modern programming patterns (e.g. async data access).

To get this update on an existing repository, you need to execute a patch. Please download it from the assets list and execute it using SnAdmin on your machine first. It will take some time because we will rearrange metadata in the database during the patch.

Features

Bug fixes

Installation

To get started please follow the instructions in the Install sensenet from NuGet article.

Assets 3

@tusmester tusmester released this Sep 11, 2019 · 184 commits to master since this release

This is a minor release containing the following feature.

Features

  • CORS port setting with wildcards: from now on you can define CORS domains with wildcard as the port to let a wide range of origin domains access the repository.

Installation

To get started please follow the instructions in the Install sensenet from NuGet article.

Assets 2

@tusmester tusmester released this Aug 6, 2019 · 188 commits to master since this release

There are mostly bug fixes in this release, please take a look at the following list of changes.

Client changes

Bug fixes

  • Office Online actions take action type (e.g. edit or view) into account when serving WOPI actions to the client. This is important in cases when a file (e.g. a doc file) can be viewed but not edited.
  • From now on it is possible to define allowed origin domains with a port number.

Package changes to support .Net Standard

  • We removed ConfigurationManager usages from the ContentRepository and Storage projects to support .Net Core applications.

Installation

To get started please follow the instructions in the Install sensenet from NuGet article.

Assets 2

@tusmester tusmester released this Jul 17, 2019 · 193 commits to master since this release

This is a minor release to support the new version of the Tools library.

Package changes to support .Net Standard

  • the Services install package got a new switch to let developers install repository-only content items, without Services-related types (e.g. OData applications that are not yet converted to .Net Standard).

Installation

To get started please follow the instructions in the Install sensenet from NuGet article.

Assets 2

@tusmester tusmester released this Jun 24, 2019 · 197 commits to master since this release

There are bug fixes and new features as well in this release, please take a look at the following list of changes.

This release requires an upgrade patch to be executed if you already have a database. Download the patch from the assets list below.

Features

  • Shared lock: for multiple users to be able to edit the same document in the browser.
  • CORS wildcard support: you can define a subdomain with a wildcard for CORS.
  • Comment OData API: a simple API for managing comments next to preview images.
  • AccessToken cleanup: periodically remove old tokens.
  • add a built-in method for configuring the external blob provider.
  • in preparation for cloud patching, we made the ContentType system more robust by allowing it to start even if a content handler is missing.
  • from now on it is possible to edit the allowed child types on a content from the client easily using PATCH or PUT OData requests.

Bug fixes

  • the Open in editor action takes file extension and permissions into account when deciding whether the action is available to the client or not.
  • a null reference error has been fixed in the desktop access provider for console environments.

Package changes to support .Net Standard

Installation

To get started please follow the instructions in the Install sensenet from NuGet article.

Assets 3

@tusmester tusmester released this Feb 22, 2019 · 218 commits to master since this release

This release contains new features and major architectural changes. Please take a look at the change log below.

New features

  • AccessToken: a new C# API for generating security tokens for users. The feature is integrated into our authentication pipeline so it is possible to use it for authentication by 3rd party players.
  • WOPI: we started working on a feature that will let users open and edit Office documents in the browser. In this release we added the API for viewing documents. Editing and the full UI solution will come later.

Architectural changes

Introducing data provider extensions

Previously any feature that required unique storage and data operations needed to be integrated to the core data provider of sensenet. Starting with this release it is possible to add a new feature involving storage and db operations outside of the main db provider. This architecture will let us provide a lot more simple and clean data provider layer in the future.

The changes above are mainly under the hood, but developers who created a custom data provider may encounter build errors, because the surface of the db provider interface has changed a little. The required changes are really minor things, please contact us if you do not know how to upgrade your code.

Package changes to support .Net Standard

Converted projects

In this release we finally converted two of our main projects to .Net Standard: the Storage and ContentRepository projects are now compatible with modern .Net environments. We are working on a fully deployable solution that will let developers access the repository in a .Net Core environment.

Legacy packages

During the .Net Standard conversion we had to move a couple of legacy features to separate packages. This is because they use old APIs that are not available in a modern environment. If your project uses these features, please install the corresponding NuGet packages:

Installation

To get started please follow the instructions in the Install sensenet from NuGet article.

Upgrade from previous versions

If you already have sensenet installed and want an in-place upgrade instead of re-creating the database, you have to do the following:

  • upgrade your database using the upgrade patch (see the attachment above in the Assets section) in your dev, test and live environments to be up to date.

Before executing the patch please make sure you have the latest version of the System.Data.SqlClient NuGet package installed in your application and there is no assembly binding in your config files pointing to a previous version of this library.

Assets 3

@tusmester tusmester released this Jan 22, 2019 · 237 commits to master since this release

There are bug fixes and new features as well in this release, please take a look at the following list of changes.

This release requires an upgrade patch to be executed if you already have a database. Download the patch from the assets list above.

Features

  • The backend part of the Sharing feature provides the API for managing private and public content sharing.

Bug fixes

  • Add allowed child types API works correctly.
  • Querying on a content's reference field (inner or nested query) works correctly through the OData API.
  • User Avatar property always contains the image url and it can be modified correctly.
  • Notify property changed event is fired correctly to avoid deviations between the node and content layers.
  • Indexing activity deserialization errors are written to the log only once, not every time the same error occurs.

Package changes to support .Net Standard

  • The legacy Performance counters api has been removed from the core product in preparation for moving our packages to .Net Standard. The feature has been moved to the Performance counters repo and package.
  • We moved the MSMQ Channel Provider to a separate package because the MSMQ technology is not available in .Net Standard.
  • We rearranged default permissions for the Identified and Everyone groups. This will make adding new users simpler because they will receive the necessary basic permissions automatically through the Everyone group. These changes will affect new projects only, they are not included in the upgrade patch to avoid unwanted permission changes.
  • We removed the System.Web reference from the Storage library to be able to convert it to .Net Standard later.
  • We also removed the IHttpHandler interface from the repository project: Images are served through the regular binary provider from now on.
  • We removed the separate Configuration dll from the main package and moved all its classes to the Services library to make our library set more streamlined.

Installation

To get started please follow the instructions in the Install sensenet from NuGet article.

Assets 3

@tusmester tusmester released this Nov 7, 2018 · 260 commits to master since this release

This is a small bugfix release, please take a look at the details of the fix below.

This release does not require an upgrade patch if you already have the previous version installed: it is enough to update the packages in Visual Studio.

Bug fixes

  • Cache insert failed in cases when the maximum date value could not be converted to the UTC time on the local server.

Installation

To get started please follow the instructions in the Install sensenet from NuGet article.

Assets 2
You can’t perform that action at this time.