Please help us by completing this survey

Go to survey

Releases

  • sensenet
  • sn-client-js
  • sn-client-dotnet
  • sn-webpages
  • sn-client-cli
    • 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 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.

    • 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.
    • 3.0.3 December 15, 2017

      Changes

      • Optimized tsconfig settings
    • 3.0.2 December 12, 2017

      Changes

      • Added noImplicitAny Typescript compiler options
      • Reviewed type castingss
    • 3.0.1 December 05, 2017

      Fixes

      • Fixed a reference lazy loading issue when no _deferred object has been provided (reference not selected)
      • Fixed minor typo in content.tryGetAsSaved()’s errormessage
      • Renamed content.Actions() to content.GetActions(). content.Actions() marked as deprecated
    • 3.0.0 November 24, 2017

      New features

      • Batch actions has been improved and are now triggering meaningful success / failure repository events on every operation inside the batch
      • OAuth Providers can be added to Authentication services - see sn-client-auth-google
      • Upload now supports additional OData parameters for reloading Content after upload

      Breaking changes

      • Authentication.LoginState - enum has been changed from a number-based enum to a string-based one
      • tslint
      • Schemas has been scoped into Repositories from the global level
      • ControlMapper requires a Repository reference ()
      • ContentTypes has been decoupled from the Content level and all logics has been removed. Custom content types will work with Content generics, the only restriction is it have to implement the IContent interface

      Fixes

      • Repository
        • fixed error message on error loading the current user
        • fixed content reload on chunked upload
      • Query
        • fixed result type assertion
    • 2.5.0 October 20, 2017

      New features

      Upload functionality has been improved, now chunked upload is supported from the library. The new upload endpoints on Content level:

      • content.UploadTextAsFile(options) - Create a text file from a string variable
      • content.UploadFile(options) - Upload a file from a File instance (e.g. from form data)
      • content.UploadFromDropEvent(options) - Upload a file structure from a single Drop event

      Binary field support has been added, now you can overwrite binaries on content field level. The new endpoints per binary fields (e.g. file.Binary) are:

      • fileContent.SaveBinaryFile(file: File)
      • fileContent.SaveBinaryText(text: string)
      • fileContent.GetDownloadUrl(): string

      New Repository setting - If you’ve modified the default BinaryChunkSize, you can adjust it with the Repository’s ChunkSize setting

      Changes

      MockHttpProvider has been refactored in order to handle a request/response queue instead of defining single results. The provider will The following methods has been removed / replaced

      • setResponse(response) -> AddResponse(response)
      • setError(error) -> AddError(error)
      • lastOptions -> RequestLog

      RxAjaxHttpProvider - The unused ForceCheckCrossDomain property has been removed.

    • 2.4.1 September 26, 2017

      Changes

      • Improved repository.GetCurrentUser() realibility, the observable will be throtteled on Authentication.State change until the current user will be loaded
      • jwtService.Logout() will trigger an additional request to flush http-only cookies
    • 2.4.0 September 19, 2017

      New features

      • Improved OData ‘orderby’ options, now ordering direction can be specified for fields
    • 2.3.0 August 22, 2017

      New features

      • Extended Repository configuration with default OData parameters for default select, required select, default metadata, default inlinecount, expand and top
      • Added repository.GetCurrentUser() observable for tracking user identity changes
      • Created SavedContent< T > type where the content Id and Path is required
      • Added batch operations to Repository: CopyBatch, MoveBatch and DeleteBatch

      Changes

      • Type checking for OData select, expand and orderby options
      • repository.handleLoadContent() will accept a SavedContent for parameter (Id and Path will be required)
    • 2.2.0 August 08, 2017

      New features

      • New Query API for building strongly typed Content Queries
      • Public Query endpoints:
        • repository.CreateQuery(…) for querying the whole repository
        • content.CreateQuery(…) for querying on a subtree of a Content
        • ContentReferenceField.Search(…) and ContentListReferenceField.Search(…) for querying available content for a specific reference field (e.g. autocomplete or picker controls)

      Changes

      • Reviewed and cleaned up NPM dependencies

      Fixes

      • Type casting and content construction on Collection responses
      • Fixed ContentReference and ContentListReference dirty checking
    • 2.1.0 July 27, 2017

      New features

      • New hierarchical content comparison methods on Content instance level
        • IsParentOf()
        • IsChildOf()
        • IsAncestorOf()
        • IsDescendantOf()
      • repository.Events Observables - RxJS Observables to track repository events
        • OnContentCreated
        • OnContentCreateFailed
        • OnContentModified
        • OnContentModificationFailed
        • OnContentLoaded
        • OnContentDeleted
        • OnContentDeleteFailed
        • OnContentMoved
        • OnContentMoveFailed
        • OnCustomActionExecuted
        • OnCustomActionFailed
      • ContentSerializer feature - can be used to stringify and parse content maintaining all of its data and its origin.
        • Added content.Stringify(): string
        • Added *repository.ParseContent(): T*
      • ContentReferenceField and ContentListReferenceField handling improved
        • Allow to get the reference w/o additional request when expanded
        • Allow to lazy-load reference when not expanded
        • Automatically serialize and deserialize reference values for requests
      • Content.Reload(viewName)
        • Reload a Content instance, $expand and $select fields automatically based on the desired view
      • Content.ReloadFields(…fields)
        • Reload the specified fields / references on a Content instance

          Changes

      • repository.Load() parameter ordering has been changed to: *idOrPath:string int, odataOptions?: IODataParams, returnsType?, version?*
      • Content.Create() parameter ordering has been changed to: contentOptions: IContentOptions, newContentType, repository: BaseRepository
      • repository.HandleLoadedContent() will try to get the content type from the constructor options ‘Type’ field, if provided, and the optional contentType parameter is not provided
      • Content.GetSchema() will fall back to GenericContent’s schema instead of throwing an error when there is no available Schema for the type
      • Updated sensenet specific enums to be string-based ones. Their values will be provided by sensenet ECM and they can be used on API calls without casting or converting

        Fixes

      • Fixed content.Delete() fired a duplicated request
      • Fixed content.HasPermission() method
      • Fixed typo on ControlMapper.GetFullSchemaForContentType()

        Deprecations

      • repository.Content - Please use repository.GetODataApi() instead
      • Content.HandleLoadedContent() - Please use repository.HandleLoadedContent() instead
    • 2.0.1 July 12, 2017

      Fixes

      • RxAjaxHttpProvider - Fixed observable error for successful requests with no response body (e.g. OData DELETE)
      • Content.Children() will respect the optional OData options parameter
    • 2.0.0 July 05, 2017

      New features

      • Content lifecycle tracking with the Content API
        • Added IsDirty, IsSaved, IsValid and SavedFields properties
        • Added GetChanges() method for change detection
        • Updated Save() method to work without parameters based on the change detection and the Content state
      • Optimized the generated Schemas structure
      • Typescript 2.4.1 Support

      Breaking changes

      • All content fields will be optional during the component creation. You can use the IsValid property to check required fields.
      • DateTime field types has changed from Date to string due timezone conversion issues.
    • 2.0.0-RC.4 June 13, 2017

      Changes

      • Added ControlMapper feature
      • Implemented Retrier
    • 2.0.0-RC.2 May 16, 2017

      Breaking changes

      • Fixed typo, renamed Repository.Contents references to Repository.Content
    • 2.0.0-RC.1 May 15, 2017

      Breaking changes

      • SetSiteUrl and SetServiceToken won’t be available any longer. These settings can be specified during Repository instance instantiation
      • OData Api methods won’t be available at the Global scope, you can use them through Repository.Contents

      New Fetatures

      • Introduced Repository class as the main, configurable entry point to the sense NET API
      • JWT Token Authentication implementation
      • Improved type safety for OData Operations
    • 1.1.0-beta.1 February 15, 2017

      1.1.0-beta.1 (2017-02-15)

      Bug Fixes

      • Change the portal url setting process and the related actions (d0a4675d)
      • Siteurl related fixes (3bb9327f)
      • common: Login and logout methods are binded to the new actions in the odataapi module (c259371b)

      Features

      • Add sn generated default ts files and their tests (80e04abc)
      • Add odata service token setting and login/logout actions (b87e1f23)
    • 1.0.2 December 01, 2016

      1.0.2-beta.5 (2016-12-05)

      Bug Fixes

      • ODataAPIActionObservables’ name is changed to ODataApiActionObservables (6b2a4cdc)
      • actionobservables: Change jquery ajax calls to fetch (b7a2e490)
      • import: Add missing index.js file (762dd7d1)

      Features

      • app: Adding the sn-client-js library (98a74a23)
      • location: Related sn portal can be configured in a config file (dc91f6cd)
    • 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.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 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.

    • 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:

    • 2.0.0-RC.3 May 22, 2017

      Fix

      • NPM Dependency to ‘fs-extra’ package
    • 1.0.0-RC.2 May 16, 2017

      Changes

      • NPM dependency ‘Path’ moved from devDependencies to dependencies
      • Updated the default sn.config.js template with the latest available parameters with a short description
    • 1.0.0-RC.1 May 15, 2017

      Initial release

      Features

      • init - Initializes an sn.config.js file into your NPM package, whitch you can use to configure your sn-client-js repository later
      • fetch-types - Allows you to download custom type definitions for sense NET ECM 7 repository.