sensenet ECM Services 7.0.0 beta4

New features

TypeScript 2.4 updates

• generated TypeScript classes take advantage of string-based enums

New packaging steps for SnAdmin

• SetField, AddReference, RemoveReference: new steps for setting or modifying field values during a patch or installation, without importing.

New SnAdmin tool

• delete: it is possible to delete a content from the repository by its path from the command line, you do not have to use the REST or C# api for that.

Bug fixes

• added a missing package reference for the OpenPop library
• added a few missing string resources

Installation

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

Upgrade from previous versions

Please export your custom content and perform a clean install, there is no upgrade patch for previous versions for this release.

sensenet ECM Services 7.0.0 beta3

New features

• Add CORS header and preflight response in case of a JWT token auth request, so that JWT authentication works with CORS.

Packaging

• Allow SnAdmin install packages to be executed multiple times (depends on the decision of the package creator).
• It is possible to create and execute packages that contain the hyphen (-) character in their name.

Bug fixes

• The Open in Office feature works regardless of the file extension casing (e.g. .xlsx/.XLSX).
• Content type header is added correctly to the response, even if the content path casing is incorrect in the request.
• OData parameter inlinecount=allpages results in executing a Lucene query (compile to SQL is not allowed in this case so that a correct full count is served to the client).
• Add missing fieldsetting content types to aid list field management on content lists.
• Allowed child type logic works even if there is a missing content type in the list.

Installation

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

Upgrade from previous versions

If you installed a previous version, please export your custom content before you get the new version:

1. export your custom content from the Content Repository (using the export SnAdmin tool)
2. upgrade the NuGet package in Visual Studio (from v7.0.0 beta2 to beta3). Make sure you let nuget overwrite your local files with the new ones from the package.
3. please remove/cleanup generated package folder(s) from your web\Admin\tools folder: most importantly install-services, so that the new package zip is extracted when you install the component again.
4. reinstall the whole Services component. This is a clean install that creates a new db. If you want to use the same db name, use the ForcedReinstall:true switch when installing.
5. import your custom data

There is no in-place upgrade for this version, the new dlls would not work with the old database.

sensenet ECM Services 7.0.0 beta2

New features

JWT authentication

JSON Web Token authentication will help client developers connect to sensenet ECM and work with the content repository in a more secure and flexible way.

Packaging improvements

• SQL authentication is supported during installation
• SnAdmin packages support phase-level custom assemblies that are loaded only for the phase that they are defined for.
• New steps:
  • Edit allowed child types (on a content or content type)
  • IfComponentExists for checking component existence (soft dependency check)

NuGet install improvements

We modularized our NuGet packages to be more flexible: now we have two packages for our components:

• one for web applications, containing content files and web folder material
• a simple, dll-only package for other project types

Bug fixes

• Variable resolution fix in various steps (Export, Index).
• Warning is logged on unknown action instead of throwing an error. This makes OData responses more robust.
• Eliminated several null reference errors when there was no Site content in the system.
• Install logic can deal with existing databases.
• Service action generates a correct url even if the service name starts with a slash.
• Saving the Root content is possible.
• Removed unnecessary custom workspace type references from the User ctd that prevented saving users.

Breaking changes

Packaging

Package manifest structure had to be changed to support the new component model of sensenet ECM.

• Every manifest should contain a component Id and optionally a list of dependent components.
• Package type definition has been simplified.
• Old package structure is not supported anymore, manifest files have to be upgraded.
  See the new manifest structure in this article: SnAdmin

Known issues

• Open in Office feature is currently not available (issue #10).
• Windows authentication is currently not available (issue #69).

Installation

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

Upgrade from previous versions

If you installed a previous version, please export your custom content before you get the new version:

1. export your custom content from the Content Repository (using the export SnAdmin tool)
2. uninstall the previous NuGet package (v7.0.0 beta)
3. install the new package (v7.0.0 beta2)
4. reinstall the whole Services component. This is a clean install that creates a new db. If you want to use the same db name, use the ForcedReinstall:true switch when installing.
5. import your custom data

There is no in-place upgrade for these versions, the new dlls would not work with the old database.

Initial release

Introducing Sense/Net Services 7.0.0 beta

Sense/Net Services is the base component of the Sense/Net ECM platform that all other components will build on.

Installation

To get started, install the following NuGet package. Please follow the instructions in the Getting started section of the main readme.

Known issues

There are a couple of known issues with the beta release. We plan to solve these before releasing the stable version:

• Open in Office feature is currently not available in the beta release.
• There is a single Services NuGet package that contains both dlls and install content files. If you install the package into multiple projects, all the install files (e.g. web.config additions) will be added to all those projects. In the future we will publish two different NuGet packages: one containing only dlls and one for install files.