Releases: SenseNet/sensenet
ContentRepository 7.7.9 and Services.Core 0.0.7
This release is mostly a technical update that takes us closer to a full .Net Core solution. It also contains several bug fixes.
If you have the .Net Framework version of sensenet installed, this release does not require an upgrade patch: it is enough to update the packages in Visual Studio.
Features
- Added a new action and infrastructure for registering users using external providers.
- Our authentication middleware accepts identifiers in the client_sub claim as well along with the original
sub
claim. - Secure file download feature has been implemented in the .Net Core Services layer.
- The in-memory blob provider (for testing purpuses) is able to handle chunk file upload requests.
OData improvements
- The OData middleware understands form-encoded request parameters.
- We ported the following actions to the new .Net Core Services layer:
Bug fixes
- Typescript metadata response contained a duplicate Type property.
- Typescript metadata
HandlerName
was missing from the schema. - OData operations
HasPermission
andGetPermission
became ODataFunctions (so that they can be called using aGET
request).
Installation
To get started please follow the instructions in the Install sensenet from NuGet article.
sensenet Services 7.7.8
This release is mostly a technical update that takes us closer to a full .Net Core solution. It also contains several bug fixes.
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.
Features
- CORS: the allowed origin feature is available in sensenet .net core apps (#834).
- Repository file download is available in .net core (#789).
- In-memory repository: it is possible to import content while the repository is running (#881).
- We published the
Storage
project as a standalone nuget package (#883).
Bug fixes
- We return the default value if a setting could not be loaded (#877).
- The new .net core user discovery algorithm became more sophisticated (commit 21d4c7e)
Installation
To get started please follow the instructions in the Install sensenet from NuGet article.
sensenet Services 7.7.7
This release is mostly a technical update that takes us closer to a full .Net Core solution. It also contains several bug fixes.
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.
Features
- The new .Net Core OData layer is able to handle querystring parameters
Bug fixes
- Use async stream operations in OData middleware because that is the default in .net core to prevent a runtime exception.
- Fix empty query execution.
- Allowed child types field is indexed correctly and became searchable.
- Previous GetSchema changes (added content handler info) were ported to the old Services project.
- OData middleware is registered correctly and developers may add custom middleware after it correctly in a .net core web project.
- Users without admin permissions are able to create other users correctly.
Installation
To get started please follow the instructions in the Install sensenet from NuGet article.
sensenet Services 7.7.5
This release is mostly a technical update that takes us closer to a full .Net Core solution.
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.
Features
- OData actions in .Net Core
- Handler name was added to the schema information.
Bug fixes
- Uppercase site url: it was not possible to register a url that contained uppercase letters.
- Settings type was set as the only allowed child type of the global Settings container.
Installation
To get started please follow the instructions in the Install sensenet from NuGet article.
sensenet Services 7.7.4
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.
sensenet Services 7.7.2
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.
sensenet Services 7.7.1
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.
sensenet Services 7.6.4
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.
sensenet Services 7.6.3
There are mostly bug fixes in this release, please take a look at the following list of changes.
Client changes
- As part of a cleanup we refactored the generated TypeScript schema.
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.
sensenet Services 7.6.2
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.