Please help us by completing this survey

Go to survey

Releases

  • sensenet
  • sn-client-dotnet
  • sn-webpages
  • sn-security
  • sn-preview
    • 7.5.1 January 21, 2019

      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.

    • 7.4.1 November 06, 2018

      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.

    • 7.4 October 04, 2018

      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.

    • 7.3.3 September 04, 2018

      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.
    • 7.3.2 August 10, 2018

      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.
    • 7.3.1 July 24, 2018

      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.
    • 7.3 July 19, 2018

      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.
    • 7.2 July 04, 2018

      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.

    • 7.1.4 May 30, 2018

      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.

    • 7.1.3 May 22, 2018

      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.

    • 7.1.2 May 08, 2018

      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.

    • 7.1.1 April 03, 2018

      New features

      • Some classes in the Search component became serializable to aid the upcoming Search Service feature.
      • Open the PermissionFilter API to let other apis call its methods.
      • Test projects were updated to the latest test project type.

      Bug fixes

      • Query count fix: in some cases the count of a query result was 0 even if the query returned the actual content items. This bug broke the Windows authentication feature.
      • Duplicated documents
      • Webdav fix for paths starting with /Root and for Versioning GUI in Word.
      • Open permission added for logged in user on the DWS (Edit in Office) web root folder to let them edit Office files.
      • The central activity queue became more robust and thread safe.

      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 versions from 7.0.0 to 7.1. 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.

    • 7.1.0 March 02, 2018

      New features

      Search module

      This is a major update of the platform: we generalized indexing and querying so that the Lucene search engine can be refactored later to work as a service instead of as a local index. In this first phase nothing will actually change architecturally: the index folders will remain in the local web directory as before. But under the hood we decoupled the search module from the repository, which means we will be able to create and deploy a separate search service in the future, without changing the code in the main application.

      Breaking changes

      This version contains API changes that may break low-level search-related calls. We had to move a few classes to a different namespace (e.g. the base TextExecutor class) and a few enumerations too. If you encounter build or type load errors during or after the upgrade, please follow the suggestions in Visual Studio to update those calls or base classes. We do not expect to have many of these, but if you stuck with the upgrade please contact us for help.

      Bug fixes

      • SmtpClient instances are created in a using block so that they got desposed properly to prevent connection leak.
      • Logout action can be called without providing the ultimateLogout optional parameter.
      • Add initial See permission for the Identified Users group to the Folder content type so that users see the folder creator action on the UI.

      Installation

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

      Upgrade from previous version

      If you already have sensenet ECM 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.

      This is a major upgrade, please check out this article for details about performing a complex upgrade.

      The patch above is a cumulative package that you may execute on versions from 7.0.0 to 7.0.2. This means you do not have to upgrade to 7.0.1 or 7.0.2 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.

    • 7.0.2 February 07, 2018

      New features

      • Ultimate logout: we improved the logout feature by letting operators and client developers decide what should happen when the user logs out of the system: from now on it is possible to log out from all clients (meaning all devices and browsers). This will make the system even more secure as it will invalidate security tokens on all clients. This is related only to the JWT authentication mechanism, it does not affect the old webforms authentication chain.

      Installation

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

      Upgrade from previous version

      If you already have sensenet ECM 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 either on version 7.0.0 or 7.0.1. This means you do not have to upgrade to 7.0.1 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.

    • 7.0.1 February 02, 2018

      The new version of sensenet ECM Services’ main component has arrived!

      New features

      • ISnComponent interface for defining components. Currently this contains an API for checking component versions to make sure that the dlls and the database remain consistent across NuGet packages (see previous link).

      Bug fixes

      Installation

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

      Upgrade from previous versions

      If you already have sensenet ECM 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.

      Note that after executing the patch, you will have to update your sensenet Services NuGet packages to the same version.

    • 7.0.0-beta4 July 21, 2017

      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.

    • 7.0.0-beta3 July 10, 2017

      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.

    • 7.0.0-beta2 May 17, 2017

      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.

    • 7.0.0-beta March 28, 2017

      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.

      NuGet

      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.
    • 7.0.0 December 02, 2017

      The stable version of the sensenet ECM Services main component has finally arrived!

      New features

      • OAuth providers let developers integrate 3rd party services (e.g. Google) for authenticatig users (aka Google sign-in).

      Type handling

      • Provider store gives developers a simple API for managing replaceable runtime instances for providers (e.g. using a memory db provider instead of a real one).

      Packaging

      • SetUrl step lets you add a new url to a site declaratively (useful in case of automatic builds)
      • MoveXmlElement snadmin step for moving xml elements inside a file or content binary.
      • SnAdmin runtime displays a human readable info when a type load exception occurs.

      OData

      • Extend batch copy, delete and move OData action responses with information about the changed content and the errors that occured during the operation.

      Bug fixes

      • load types at startup and during runtime without throwing an error if there are ones that are not installed
      • Notification class name fixed in source code and config
      • Suppress field errors when serving a content through OData.
      • close output file stream after editing it in xml editor snadmin step
      • binary download is supported with JWT authentication
      • sorting has been fixed for batch node load
      • we allowed the Everyone group to access several applications by default so that administrators do not have to give permission one by one
      • OData REST api returns all the actions in a scenario, not just html ones
      • a token authentication control flow bug has been fixed
      • give startup user a real id that will let us save content during request startup
      • added the necessary http headers for chunked upload

      Known issues

      In the current release the following features may not work, depending on your environment:

      • Windows authentication
      • WebDAV
      • Open in Office

      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.

    • 2.0 July 13, 2018

      The main theme of this release is to upgrade the .Net Client project to .Net Standard 2.0 so that it can be referenced from either .Net Framework or .Net Core.

      Binaries

      If you want to reference this library in your project, please do it by installing the NuGet package.

      NuGet

    • 1.1.1 May 29, 2018

      Bug fixes

      Binaries

      If you want to reference this library in your project, please do it by installing the NuGet package.

      NuGet

    • 1.1 November 23, 2016

      Introducing Sense/Net Client for .Net

      A .Net client for Sense/Net ECM that makes it easy to use the REST API of the Content Repository.

      Binaries

      If you want to reference this library in your project, please do it by installing the NuGet package.

      NuGet

    • 7.2.3 January 21, 2019

      This minor release focuses on supporting the latest version of sensenet: v7.5.1.

      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.

      Installation

      Prerequisites: you have to install sensenet Services before you can install WebPages.

      You can install the sensenet WebPages component in Visual Studio as a NuGet package. Please follow the steps in the the following article:

    • 7.2.2 September 10, 2018

      This minor release focuses on supporting the refactored cache API in sensenet.

      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.

      Installation

      Prerequisites: you have to install sensenet Services before you can install WebPages.

      You can install the sensenet WebPages component in Visual Studio as a NuGet package. Please follow the steps in the the following article:

    • 7.2.1 September 10, 2018

      This is a small bugfix release, but it requires a patch to be executed if you want to keep your database.

      Bug fixes

      • As the BlobStorageConfiguration class has been removed from the main Services component, views in this package needed to be upgraded to use the new config class as a replacement.
      • Use a safe query in PageTemplateManager to load pages.

      Installation

      Prerequisites: you have to install sensenet Services before you can install WebPages.

      You can install the sensenet WebPages component in Visual Studio as a NuGet package. Please follow the steps in the the following article:

      Upgrade from previous versions

      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.

    • 7.2.0 July 04, 2018

      New features

      The main theme of this release is to upgrade the WebPages project to be compatible with .Net Framework 4.6.1 and the base component sensenet Services 7.2.

      To learn more about this framework update, please check the corresponding Services release.

      Breaking changes

      • Please make sure that all your projects are built using .Net Framework 4.6.1 (or a later version) before upgrading.

      Installation

      Prerequisites: you have to install sensenet Services before you can install WebPages.

      You can install the sensenet WebPages component in Visual Studio as a NuGet package. Please follow the steps in the the following article:

      Upgrade from previous versions

      If you already have sensenet installed and want an in-place upgrade instead of re-creating the database, please check the release v7.1 for the patch that upgrades the database to at least version 7.1 of WebPages.

      Later versions do not need an upgrade patch, only the updated NuGet package.

    • 7.1.0 March 05, 2018

      New features

      The main theme of this release is to update the package to support the Search module changes in sensenet Services 7.1. We updated the code and the content items to be compatible with the new search API.

      Bug fixes

      • Add missing content
        • spinner image
        • global Search page
      • removed unnecessary doc viewer JavaScript files as they are available in the Preview component.

      Installation

      Prerequisites: you have to install sensenet ECM Services before you can install WebPages.

      You can install the sensenet ECM WebPages component in Visual Studio as a NuGet package. Please follow the steps in the the following article:

      Upgrade from previous versions

      If you already have sensenet ECM 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.

      This is a complex patch, please check out this article for details about performing a complex upgrade.

    • 7.0.0-beta2 July 10, 2017

      New features

      • Add more content types, views and controls: Article, ArticleSection, HTMLContent, WebContent CTDs and TagList control.

      Bug fixes

      • EditField and MoveField apps added to make contentlist field editing possible on the UI.
      • ContextBound portlet logs the path information when a binding error occurs.
      • Add missing string resources.

      Installation

      Prerequisites: you have to install sensenet ECM Services before you can install WebPages (Services 7.0.0 beta is not enough, WebPages needs at least Services 7.0.0 beta3).

      You can install the sensenet ECM WebPages component in Visual Studio as a NuGet package. Please follow the steps in the the following article:

      Upgrade from previous versions

      There is no in-place upgrade for this version, the new dlls would not work with the old database. In the future there will be official upgrade patches for subsequent releases. Please reinstall the underlying Services component before installing this new version.

    • 7.0.0-beta1 May 18, 2017

      Introducing sensenet ECM WebPages 7.0.0 beta1

      This component is a UI layer for the sensenet ECM platform built using ASP.NET WebForms pages, portlets (webparts) and controls.

      It does not contain predefined user interfaces for end users, but there is an admin UI (the Content Explorer) that you can use to build your portal from our building blocks.

      Installation

      Prerequisites: you have to install sensenet ECM Services 7.0.0 beta2 before you can install WebPages (Services 7.0.0 beta is not enough, WebPages needs at least beta2).

      You can install the sensenet ECM WebPages component in Visual Studio as a NuGet package. Please follow the steps in the the following article:

    • 7.0.0 December 14, 2017

      New features

      • TaskMonitor UI for monitoring executing tasks in the Task Management component.
      • New packaging steps
        • RenameContentListViewColumn step

      Bug fixes

      • Add missing controls, pages, classes and settings
        • global Error control in the global content views folder
        • Password change app
        • Page type is allowed on the Site type by default
        • Purge from proxy, SetAsDefaultView, ImportFromCsv actions
        • Explore pages in the IMS folder (displaying users, orgunits and domains)
      • Fix versioninfo gui

      Installation

      Prerequisites: you have to install sensenet ECM Services before you can install WebPages.

      You can install the sensenet ECM WebPages component in Visual Studio as a NuGet package. Please follow the steps in the the following article:

      Upgrade from previous versions

      There is no in-place upgrade for this version, the new dlls would not work with the old database. Starting from this release there will be official upgrade patches for subsequent releases. Please reinstall the underlying Services component before installing this new version.

    • 4.0 November 20, 2018

      In this release we are introducing the concept of Entry types. This was necessary to implement the first special entry type (Sharing) that will aid the Sharing feature in sensenet.

      Entry types can be used to store feature-specific security entries along with other, normal entries so that they can be used in the same permission evaluation process while managed separately.

      Breaking change

      Because this new feature requires a new column in the database, this is a breaking change. If you are using the security component inside sensenet, you do not have to worry about it: the upgrade script is included in the sensenet patch.

      If you are using this package as a standalone component, please use the attached patch script that will take care of migrating your data to the new schema (in-place upgrade, just execute the script).

    • 3.0 June 25, 2018

      New features

      In this release we upgraded most of the projects to .Net Framework 4.6.1 and the main library to .Net Standard so that newer architectures may use it.

      • a new data provider was added for Entity Framework Core that is compatible with the previous database structure, you may use it without changes in the database

      Binaries

      If you want to reference the libraries in your project manually, please do it by installing these NuGet packages.

      Security core: NuGet Entity Framework Core data provider (optional): EFCore data provider Entity Framework 6 data provider (optional): EF6 data provider MSMQ message provider (optional): MSMQ message provider RabbitMQ message provider (optional): RabbitMQ message provider

    • 2.4 May 29, 2018

      New features

      • we added a new message provider for RabbitMQ
      • a new API for shutting down the security system has been added

      Binaries

      If you want to reference the libraries in your project manually, please do it by installing these NuGet packages.

      Security core: NuGet Entity Framework data provider: EF/ data provider MSMQ message provider (optional): MSMQ message provider RabbitMQ message provider (optional): RabbitMQ message provider

    • 2.3 November 24, 2016

      Introducing Sense/Net Security

      A powerful .Net component for managing permission entries in content repositories.

      Binaries

      If you want to reference the libraries in your project, please do it by installing these NuGet packages.

      Security core: NuGet Entity Framework data provider: EF/ data provider MSMQ message provider (optional): MSMQ message provider

    • 7.1.1 September 03, 2018

      This release contains the preview image cleanup feature that lets operators clean up unnecessary preview images from the repository to save storage space.

      This release does not require an upgrade patch, just update the package from NuGet and compile your application.

      Installation

      To get started please follow the install guide.

    • 7.1 July 13, 2018

      This release focuses on updating preview projects to .Net Standard and .Net Framework 4.6.1 to be compatible with the latest release of sensenet.

      Installation

      To get started please follow the install guide.

    • 7.0.0 February 02, 2018

      Introducing sensenet ECM Preview and Document Viewer

      A preview generator and viewer for the sensenet ECM platform.

      Installation

      To get started please follow the install guide.