Assets 2

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.

@tusmester tusmester released this Oct 8, 2018 · 2 commits to master since this release

Assets 2

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

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

  • The infinite Children expand issue has been fixed.
  • ReindexBinaries task (used during upgrading from sensenet 6) threw an exception in tests.
  • Content property changed notification: when a contenthandler property is changed, we need to reset the content field value to let indexing use the most recent value. Because of this bug developers needed to reload content objects in some cases after a save operation.

New features

  • we extended the built-in OAuth identity with an avatar image so that external providers may import a profile image for the user.

Package changes to support .Net Standard

  • removed Entity Framework 6 hard reference: this will let us convert our libraries to .Net Standard later. In the default package there is still an EF6 soft dependency (because of the security component) but that will be also replaced later with the already published EF Core data provider for the security component.
  • removed Ionic.Zip dependency from sensenet to rely on the built-in .Net compression API.
  • removed System.Web.Caching dependency. This may cause a breaking change in your project if you used the cache dependency API in sensenet. Do not worry, the upgrade is straightforward and very few projects are actually affected.

Installation

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

@tusmester tusmester released this Sep 5, 2018 · 17 commits to master since this release

Assets 3

There are mainly internal changes in this release, take a look at the following links to know more about what has changed since the last release.

This release requires an upgrade patch to be executed if you already have a database.

New features

  • add additional no cache headers to the response to make the client clean up the cache (thanks @VargaJoe for the contribution).
  • Patching:
    • we added a new indexing step (BinaryReindex) for rebuilding index documents in the database without indexing binaries. This will make the upgrade from sensenet version 6 to 7 much faster.
    • new control flow step: WhileDatabaseValue will let developers execute long-running db patch operations in blocks without experiencing SQL timeout.
    • DeleteContentType step is able to work with multiple content types to run faster.
  • Version poperties are available on the OData API. This will let you access the correct creators and creation dates for individual content versions.

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.

@tusmester tusmester released this Aug 13, 2018 · 25 commits to master since this release

Assets 3

There are both new features and bug fixes in this release, take a look at the following links to know more what has changed since the last relase.

This release requires an upgrade patch to be executed if you already have a database.

New features

  • there are new OData functions for getting children or ancestors of a content item
  • we simplified the logging infrastructure (under the hood) and removed the Enterprise Library dependency from the system

Bug fixes

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.

@tusmester tusmester released this Jul 24, 2018 · 31 commits to master since this release

Assets 2

In this release we converted one of the internal standalone libraries in sensenet (TokenAuthentication) to .Net Standard 2.0 as part of our goal to modernize our libraries. This is something that happens under the hood, just upgrade the NuGet packages and compile your application.

Bug fixes

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:

  • versions before 7.2: upgrade your database using the upgrade patch (you'll find it on the page of the 7.2 release) in your dev, test and live environments to be up to date.
  • versions 7.2 or later: do not require a patch in the dev environment, just update the NuGet package and compile your application.

@tusmester tusmester released this Jul 20, 2018 · 35 commits to master since this release

Assets 2

Features

  • The new Repository builder API lets developers configure the repository from code during application start instead of having to edit configuration files.

Bug fixes

  • The site start process froze in some environments when trying to access the performance counter API.

Breaking changes

  • The Blob storage library has been converted to .Net Standard 2.0. During this process we had to move a legacy feature, MS Sql FILESTREAM column support to a separate package. If you are using the FileStream feature to store binaries in sensenet, you will have to install that new package and configure it as an external blob provider. Please visit the main page of the MS Sql FileStream provider repository to know more.

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:

  • versions before 7.2: upgrade your database using the upgrade patch (you'll find it on the page of the 7.2 release) in your dev, test and live environments to be up to date.
  • versions 7.2 or later: do not require a patch in the dev environment, just update the NuGet package and compile your application.

@tusmester tusmester released this Jul 4, 2018 · 40 commits to master since this release

Assets 3

This is an important milestone toward cloud compatibility: we started to convert our projects to support .Net Standard 2.0. This means that we had to upgrade all our projects to at least .Net Framework 4.6.1 (which is the earliest version of the framework that supports netstandard 2.0).

In this release cycle we converted the following related packages to .Net Standard:

  • SenseNet.Common
  • SenseNet.Search

Features

  • Easy release: from the next release it will be possible to update only the NuGet package of a component (without executing an upgrade patch) if there were no database or configuration changes (this is not the case for this particular release however, because there are config changes).
  • We removed Unity containers from the product in preparation for removing EntLib as a dependency. Please check remaining Unity containers and type definitions in your configuration after upgrading.
  • Our provider loading mechanism got smarter: if there is no provider configured in code for a certain name, it will look into the configuration file for that provider automatically.

Bug fixes

  • There was a stackoverflow exception in certain cases when a custom Membership extender tried to access the security subsystem.
  • There was a serialization error during patch execution (when upgrading from a previous version), caused by an incorrect indexing algorithm.
  • Incorrectly formatted xml files were not indexed at all. From now on we index them as regular text files.

Breaking changes

  • Please make sure that all your projects are built using .Net Framework 4.6.1 (or a later version) before upgrading.
  • Please check remaining Unity containers and type definitions in your configuration after upgrading.

Installation

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

Upgrade from previous version

If you already have sensenet installed and want an in-place upgrade instead of re-creating the database, please run the upgrade patch (you'll find it above in the Assets list) in your dev, test and live environments to be up to date. The patch is an SnAdmin package.

The patch above is a cumulative package that you may execute on any previous version. This means you do not have to upgrade to previous interim versions before executing this one.

Note that after executing the patch, you will have to update your sensenet Services NuGet packages to the same version. Please check your connection strings (web.config and Tools\SnAdminRuntime.exe.config) after updating the packages, because NuGet may change those values based on the package contents.

Known issues

It is possible that when you upgrade your NuGet packages, an extra line appear in the loggingConfiguration/formatters section: a duplicated line with the name 'Text Formatter'. If that happens, please remove one of those lines.

@tusmester tusmester released this Jun 26, 2018 · 55 commits to master since this release

Assets 3

This is mainly a bugfix release before starting to refactor our project files to a more modern format.

Bug fixes

  • We update the Owner of a new content only if it is the Visitor. This fixes an issue when a newly created user profile workspace contain inaccessible content.
  • TreeCache fix: in case of heavy load TreeCache threw a null reference exception during reload.
  • We always load TreeCache items in elevated mode to not miss some of the items during reload.
  • Security component is shut down properly to avoid logging many thread abort exceptions during system shutdown.

Installation

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

Upgrade from previous version

If you already have sensenet installed and want an in-place upgrade instead of re-creating the database, please run the upgrade patch (you'll find it above in the Assets list) in your dev, test and live environments to be up to date. The patch is an SnAdmin package.

The patch above is a cumulative package that you may execute on any previous version. This means you do not have to upgrade to previous interim versions before executing this one.

Note that after executing the patch, you will have to update your sensenet Services NuGet packages to the same version. Please check your connection strings (web.config and Tools\SnAdminRuntime.exe.config) after updating the packages, because NuGet may change those values based on the package contents.

@tusmester tusmester released this May 24, 2018 · 60 commits to master since this release

Assets 3

New features

  • New actions
    • To let client-side devs build dynamic forms, we added the GetSchema custom action that will serve the available content types (including field metadata) to the client.
  • New SnAdmin steps
    • To aid the migration process from sensenet 6 to sensenet 7, we created a Move config SnAdmin step that will be able to update configuration files. This is a generic step so you'll be able to use it in similar scenarios.
    • We extended the ForEach SnAdmin step to work with an explicit file list (e.g. well-known config files) in a loop.

Installation

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

Upgrade from previous version

If you already have sensenet installed and want an in-place upgrade instead of re-creating the database, please run the upgrade patch (you'll find it above in the Assets list) in your dev, test and live environments to be up to date. The patch is an SnAdmin package.

The patch above is a cumulative package that you may execute on any previous version. This means you do not have to upgrade to previous interim versions before executing this one.

Note that after executing the patch, you will have to update your sensenet Services NuGet packages to the same version. Please check your connection strings (web.config and Tools\SnAdminRuntime.exe.config) after updating the packages, because NuGet may change those values based on the package contents.

@tusmester tusmester released this May 9, 2018 · 66 commits to master since this release

Assets 3

New features

  • Component version compatibility is not checked when using debug dlls to speed up the development process.
  • Delete content type step is added to serve cleanup scenarios in the future.
  • Improved in-memory db installation in tests.
  • We opened a virtual method in the ClusterChannel base class so that 3rd party developers can create their own messaging providers. We use this API to create the initial implementation of the RabbitMQ messaging provider.

Bug fixes

  • An unknown field in a query caused a null reference exception.
  • LINQ to SN First, FirstOrDefault and a couple of similar methods work correctly. If a LINQ method is not supported, we throw a meaningful exception to inform the developer what to do.
  • Fixed a wildcard query bug in LINQ to SN that broke StartsWith expressions.
  • When the user Profiles container is created, we set container permissions correctly so that new users can access their profiles.

Installation

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

Upgrade from previous version

If you already have sensenet installed and want an in-place upgrade instead of re-creating the database, please run the upgrade patch (you'll find it above in the Assets list) in your dev, test and live environments to be up to date. The patch is an SnAdmin package.

The patch above is a cumulative package that you may execute on any previous version. This means you do not have to upgrade to previous interim versions before executing this one.

Note that after executing the patch, you will have to update your sensenet Services NuGet packages to the same version. Please check your connection strings (web.config and Tools\SnAdminRuntime.exe.config) after updating the packages, because NuGet may change those values based on the package contents.