<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Miklós Tóth on Medium]]></title>
        <description><![CDATA[Stories by Miklós Tóth on Medium]]></description>
        <link>https://medium.com/@tusmester?source=rss-307e79fab514------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*u9m8Y3sNUEyW59I3.</url>
            <title>Stories by Miklós Tóth on Medium</title>
            <link>https://medium.com/@tusmester?source=rss-307e79fab514------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:19:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tusmester/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Webhooks in sensenet]]></title>
            <link>https://medium.com/sensenet/webhooks-in-sensenet-9f124cf0fb69?source=rss-307e79fab514------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f124cf0fb69</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[webhooks]]></category>
            <dc:creator><![CDATA[Miklós Tóth]]></dc:creator>
            <pubDate>Wed, 10 Feb 2021 11:35:57 GMT</pubDate>
            <atom:updated>2021-02-10T11:35:57.940Z</atom:updated>
            <content:encoded><![CDATA[<p>In modern service platforms like sensenet, developers need the possibility to do something when something happens in the service. In more technical terms: handling <strong>events</strong> is one of the most important things we need when building an enterprise application.</p><p>In the old days backend developers would handle this issue by developing a module that runs inside the application when a user uploads a file — but since everything has moved to the cloud, this is not an option anymore.</p><p>Fortunately in a service-oriented environment we can do the same with <a href="https://en.wikipedia.org/wiki/Webhook">webhooks</a>. They are basically <strong>HTTP requests</strong> made by the service and a corresponding handler method on the other side. Developers can then do what their project requires in case of these events — for example archiving a document, starting a build in the cloud or sending a notification email.</p><p>Many popular services offer webhooks. You can react for example to <a href="https://docs.github.com/en/github/extending-github/about-webhooks">code commits</a> on <a href="https://github.com/">GitHub</a> or <a href="https://sendgrid.api-docs.io/v3.0/webhooks/retrieve-event-webhook-settings">email events</a> in <a href="https://sendgrid.com/">SendGrid</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ca2oN43MBF6yzhk4.png" /></figure><p>In sensenet, webhooks are an easy way to <strong>integrate our service with another</strong>. They are usually triggered by content changes. You can register a webhook for the usual content operations — for example when somebody uploads a file or changes an article.</p><p>When such an event occurs, we call the URL you provided. It can be a custom application in your datacenter, a serverless function in the cloud or a 3rd party service like <a href="https://slack.com/intl/en-hu">Slack</a> or <a href="https://www.netlify.com/">Netlify</a>. We make these HTTP requests based on the <strong>filter</strong> you define: for example you are interested only in new file uploads in a certain library but not article changes. You also have some control over the request itself — for example you can add custom headers or url parameters required by your webhook handler.</p><p>In the future we plan to extend the list of events with other options like permission changes, login events, and so on. Please let us know which events would you like to have a webhook for!</p><p>Photo by jesse ramirez and Duy Pham on Unsplash</p><p><em>Originally published at </em><a href="https://www.sensenet.com/blog/2021-02-10-webhooks"><em>https://www.sensenet.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f124cf0fb69" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sensenet/webhooks-in-sensenet-9f124cf0fb69">Webhooks in sensenet</a> was originally published in <a href="https://medium.com/sensenet">sensenet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A road to .Net Standard]]></title>
            <link>https://medium.com/sensenet/a-road-to-net-standard-d0c144638cdd?source=rss-307e79fab514------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0c144638cdd</guid>
            <category><![CDATA[platform]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[netstandard]]></category>
            <dc:creator><![CDATA[Miklós Tóth]]></dc:creator>
            <pubDate>Mon, 09 Jul 2018 00:00:00 GMT</pubDate>
            <atom:updated>2018-07-09T17:31:41.517Z</atom:updated>
            <content:encoded><![CDATA[<p>There is a lot going on with .Net these days. First came the new era of .Net Core, then a new standard emerged that serves as a bridge between the old and the new platforms. We have to make sensenet available to as many customers as possible. This is why we started to unify our projects to support <a href="https://docs.microsoft.com/en-us/dotnet/standard/net-standard">.Net Standard 2.0</a> that contains a lot more APIs than its predecessors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CiXCGBOxhkqWP1X5.jpg" /></figure><h3>A unified .Net platform</h3><p>To offer at least parts of sensenet in .Net Standard format, we have to upgrade all our libraries to <strong>at least .Net Framework 4.6.1</strong>, because that is the oldest version on the framework line that supports .Net Standard 2.0. This already happened in the last few days: we released a new version of our components containing the new libraries.</p><p>This means that starting with <strong>sensenet Services 7.2</strong> the application project that uses sensenet packages has to be at least on .Net Framework 4.6.1 or later. This should not be a big deal as that version is relatively old.</p><blockquote><strong><em>Important</em></strong><em>: please note that there was a </em><a href="https://github.com/dotnet/standard/issues/300"><em>type forwarding issue</em></a><em> in .Net Framework 4.6.1 that breaks interop with a netstandard assembly if it contains certain methods in a class marked as Serialized. This means that although your projects may be on 4.6.1, on the target (executing) machine at least </em><strong><em>.Net Framework 4.7.2</em></strong><em> has to be installed.</em></blockquote><h3>I’m confused, .Net Framework, Core or Standard?</h3><p>sensenet consists of many libraries. The goal is to offer these libraries to the broadest customer audience possible. The .Net Standard format lets both <strong>.Net Framework</strong> (4.6.1+) and <strong>.Net Core</strong> (2.0+) applications use our packages. This lets older projects get the new features while modern environments (for example a full cloud-ready build and deployment system) can also use the same code base.</p><blockquote><em>But we are not there yet.</em></blockquote><h3>Converting sensenet libraries</h3><p>There are some features or APIs in sensenet that are <strong>not available in .Net Standard</strong> (of course in a future version of the standard there may be more APIs available but we can only work with what we have now): <em>EventLog</em> access, <em>MSMQ messaging</em> and <em>Workflow Foundation</em> among them. Our approach is to replace these features with more modern solutions or separate them into their own components and make them available as a legacy option.</p><p>There are other reasons for decomposing some features: as MSMQ is <strong>not available in the cloud</strong>, we will offer a different solution (based on <em>RabbitMQ</em> or <em>Azure Service Bus</em>) for messaging in cloud deployments.</p><p>This means we will convert our projects one-by-one, starting from the bottom. <em>SenseNet.Tools</em>, <em>Common</em>, <em>Search</em> and a few other libraries are already converted to netstandard, as you can see in the following diagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FHFBpmu5RDeYtwHd.png" /></figure><p>As we move forward with this project, we will post updates on how many and what kind of issues we have left and which packages are converted to netstandard.</p><h3>How does this affect my project?</h3><p>You should not notice much — at least at the beginning. When we release a new version, NuGet will take care of updating your dll references.</p><p>We try to convert or move features in the background, without changing the API if possible. When we remove and replace a dependency (e.g. <em>Enterprise Library</em> soon) you’ll have the option to use either the old or the new technology (in this case a more modern, service-oriented logging module).</p><h3>Easier upgrades</h3><p>Ok, but does not this mean that I’ll have to update sensenet packages too frequently and execute patches all day?</p><blockquote><em>Fortunately not.</em></blockquote><p>Our components (e.g. Services, WebPages) have two parts: libraries and a database part (e.g. content type definitions, views, etc.). If <em>only the dll part changes</em> (as is the case when we refactor the code base in the background), you <em>do not have to execute an SnAdmin patch</em>, because the dll is still compatible with the content items in the database.</p><p>Starting with sensenet 7.2, our components know the last supported version for their database part, so if there were no changes in the content repository, you can just <strong>update the NuGet package in Visual Studio</strong> and compile your application!</p><p>Photo by <a href="https://unsplash.com/photos/FWOGqSKq_Cs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">rawpixel</a> on <a href="https://unsplash.com/search/photos/standard?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p>Have feedback on this post? Let <a href="https://twitter.com/sensenet">@sensenet</a> know on Twitter.</p><p>Need help or found a bug? <a href="https://community.sensenet.com/contact">Contact us</a>.</p><p><em>Originally published at </em><a href="https://community.sensenet.com/blog/2018/07/09/netstandard-first"><em>community.sensenet.com</em></a><em> on July 9, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0c144638cdd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sensenet/a-road-to-net-standard-d0c144638cdd">A road to .Net Standard</a> was originally published in <a href="https://medium.com/sensenet">sensenet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A complex patch]]></title>
            <link>https://medium.com/sensenet/a-complex-patch-bcc86d279382?source=rss-307e79fab514------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcc86d279382</guid>
            <category><![CDATA[ecm]]></category>
            <dc:creator><![CDATA[Miklós Tóth]]></dc:creator>
            <pubDate>Mon, 05 Mar 2018 00:00:00 GMT</pubDate>
            <atom:updated>2018-03-05T14:02:40.570Z</atom:updated>
            <content:encoded><![CDATA[<p>In most cases executing a <a href="https://community.sensenet.com/blog/2018/02/14/install-patch">sensenet ECM patch</a> is easy: download-execute-forget. There are cases however when because of API or content changes this requires a bit more attention. In this post we will go through a process like this.</p><p>From time-to-time we have to change some parts of the API. Usually this happens because we need to clean up or clarify those parts or to make way for a new feature. If your custom solution used the previous API, this may require some manual work during patching.</p><blockquote><em>Of course we always try to minimize the impact of these changes, extend our APIs silently. But in cases like the </em><a href="https://github.com/SenseNet/sensenet/issues/125"><em>information retrieval refactor</em></a><em> we could not avoid a few breaking changes. Sometimes the change does effect only a subset of our users, depending on whether you’ve used a certain API or not.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YocBonLQxwUgX2vaGODO4g.jpeg" /></figure><h3>Optimistic approach</h3><p>The process always starts as usual, by downloading and trying to <a href="https://community.sensenet.com/blog/2018/02/14/install-patch">execute the latest patch</a>. If it fails with a <strong>type load error</strong>, that is usually a sign that you are using an old API either directly in your code or through a 3rd party component. In that case you’ll have to <strong>rebuild or update</strong> those libraries before executing the patch.</p><p>If there are type mismatch errors between the old and the new API and the package contains steps that need to be executed using the <em>new dll set</em> (for example updating pages or importing), there is no way to avoid adding your updated libraries to the package — see the details below.</p><h3>Rebuilding your libraries</h3><p>If you have to rebuild your libraries, please do the following:</p><ul><li>backup your web folder containing the old environment</li><li>get the latest NuGet packages of the component you are trying to patch</li><li>rebuild your solution and resolve build errors.</li></ul><h3>Extend the package</h3><p>There is a way for developers to <strong>add custom libraries</strong> to sensenet packages so that they are copied to the target directory <strong>during patching</strong>. The necessary steps are already there inside the patch in the appropriate place, so you <strong>do not have modify the manifest</strong> — only <strong>put the libraries into the zip file</strong>.</p><p>The reason behind this magic is that in complex patch cases we need to copy the new libraries in the middle of package execution — not earlier and not later. Steps before need to use the old libraries and steps after need the new ones.</p><p>Please copy your libraries to the following subfolder inside the package:</p><pre>Customization\bin</pre><p>Everything placed into the subfolder above will be copied to the <em>web\bin</em> folder of the target site.</p><p>You can also put import content files to the package, they will be imported into the repository at the appropate time:</p><pre>Customization\import</pre><p>The content file structure will be imported under the <em>Root</em> content when we import our own content files at the end of a patch.</p><blockquote><em>Not all future patches will contain these copy/import steps — only when there was an API change that makes this necessary. If you think that a certain patch lacks these steps, or you encounter an error that cannot be handled this way, please contact us. </em><strong><em>Modifying the manifest file inside the patch</em></strong><em> is of course also possible, but please do that only if you are absolutely sure what you are doing.</em></blockquote><p>First you have to <strong>restore the original, old environment</strong>. Yes, that is correct — please restore old libraries and web folder. This is necessary because a complex package needs to start with the old environment — for example because it needs those old libraries to perform an operation before overwriting them with the new ones. It also expects that the web folder (for example configuration) is in the old state.</p><p>After that you should be able to execute the patch (containing your updated libraries) without errors. At the end you also have to <strong>update NuGet packages again</strong>, so that you use the latest libraries in your development environment.</p><h3>Dependent packages</h3><p>Sometimes there are <strong>other sensenet components</strong> (for example <em>WebPages</em> or <em>Workspaces</em>) that depend on the new API. If you installed them in your environment, you will also have to update those components too, because NuGet will get the latest libraries automatically, but your repository would contain the old component version. You’ll notified about this when you try to start the portal next time and receive an error message stating that there is a component in the database with an old version number that cannot run.</p><p>Please let us know how you manage to work with these patches and how can we improve the process!</p><blockquote><em>Photo by </em><a href="https://unsplash.com/photos/7nrsVjvALnA?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Denys Nevozhai</em></a><em> on </em><a href="https://unsplash.com/collections/1577014/car?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Unsplash</em></a></blockquote><p>Have feedback on this post? Let <a href="https://twitter.com/sensenet">@sensenet</a> know on Twitter.</p><p>Need help or found a bug? <a href="https://community.sensenet.com/contact">Contact us</a>.</p><p><em>Originally published at </em><a href="https://community.sensenet.com/blog/2018/03/05/complex-patch"><em>community.sensenet.com</em></a><em> on March 5, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcc86d279382" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sensenet/a-complex-patch-bcc86d279382">A complex patch</a> was originally published in <a href="https://medium.com/sensenet">sensenet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installing a patch in sensenet ECM]]></title>
            <link>https://medium.com/sensenet/installing-a-patch-in-sensenet-ecm-a4ba75973ecc?source=rss-307e79fab514------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4ba75973ecc</guid>
            <category><![CDATA[upgrade]]></category>
            <category><![CDATA[ecm]]></category>
            <dc:creator><![CDATA[Miklós Tóth]]></dc:creator>
            <pubDate>Wed, 14 Feb 2018 00:00:00 GMT</pubDate>
            <atom:updated>2018-02-15T08:37:22.675Z</atom:updated>
            <content:encoded><![CDATA[<p>Sensenet ECM moved to GitHub in small parts. These parts are also maintainable, so need patches. Here is the first one, let’s see what this means for developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*OjlWaQOWomgiwnnf.png" /></figure><h3>Patching Services</h3><p>The <strong>Services</strong> component was the first to dwell on GitHub therefore it is quite reasonable to receive the first patch as well. It contains bugfixes and a single new feature.</p><blockquote><em>Although this post was written at the time of the first patch, the process will be very similar in case of subsequent patches in other components as well.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*-5hfWEz2D_zLClgG.gif" /></figure><h3>Find out if you need it</h3><p>The following conditions indicate that your sensenet ECM have to be upgraded with the patch:</p><ul><li>you have an installed sensenet ECM 7.0.0 site</li><li>you want an <strong>in place upgrade</strong>, which means you want to get the latest version <strong>without dropping the database</strong>.</li></ul><blockquote><em>If one of these criterias is not fit for your situation you will not need to install this patch. In a development and test environment where you </em><strong><em>reinstall and reindex the whole database</em></strong><em> every time, you can use the updated NuGet packages and continue working.</em></blockquote><h3>Where can you find it?</h3><p>You can find the patch on the <a href="https://github.com/SenseNet/sensenet/releases">release page</a>’s Assets paragraph, where you can download it from.</p><h3>How do you install it?</h3><p>Download the patch (a zip file indicating the base and the target versions) from the release page. In order to install it, you need to follow the next few steps:</p><ol><li>Stop the site.</li><li>Execute the patch (using <a href="https://community.sensenet.com/docs/snadmin">SnAdmin</a>). This will raise the version number of this component in the database and make the necessary modifications.<br>snadmin [patch.zip]</li><li>Update the <strong>SenseNet.Services</strong> and <strong>SenseNet.Services.Install</strong> packages from NuGet in Visual Studio so that next time you build your solution you get the new libraries.</li></ol><p>After you have finished the process you can start the site again and will find your Services component upgraded to the latest version. To make sure this happened, you may check the <strong>VersionInfo</strong> page on the Root console in Content Explorer.</p><p>Have feedback on this post? Let <a href="https://twitter.com/sensenet">@sensenet</a> know on Twitter.</p><p>Need help or found a bug? <a href="https://community.sensenet.com/contact">Contact us</a>.</p><p><em>Originally published at </em><a href="https://community.sensenet.com/blog/2018/02/14/install-patch"><em>community.sensenet.com</em></a><em> on February 14, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4ba75973ecc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sensenet/installing-a-patch-in-sensenet-ecm-a4ba75973ecc">Installing a patch in sensenet ECM</a> was originally published in <a href="https://medium.com/sensenet">sensenet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting started with sensenet ECM using MVC]]></title>
            <link>https://medium.com/sensenet/getting-started-with-sensenet-ecm-using-mvc-bd9d84b50c8d?source=rss-307e79fab514------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd9d84b50c8d</guid>
            <category><![CDATA[aspnet-mvc]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[mvc]]></category>
            <dc:creator><![CDATA[Miklós Tóth]]></dc:creator>
            <pubDate>Wed, 31 Jan 2018 00:00:00 GMT</pubDate>
            <atom:updated>2018-02-08T13:19:40.128Z</atom:updated>
            <content:encoded><![CDATA[<p>When you build a site with sensenet ECM, you have many options when it comes to choosing a technology. This post walks you through a few easy steps to create your first <strong>Asp.Net MVC</strong> app with sensenet ECM 7.0. It is a part of a series about the different client and server-side technologies and architectures when designing your first app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bpiyN2aoSPCjRtNF-yjL7g.jpeg" /></figure><p>This post will help you create your first <strong>Asp.Net MVC</strong> app with sensenet ECM 7.0. For other possibilities please take a look at the following articles:</p><ul><li><a href="https://community.sensenet.com/docs/tutorials/starting-out-with-reactjs">Starting out with ReactJs and Redux</a></li><li><a href="https://community.sensenet.com/blog/2018/01/10/starting-out-with-aurelia">Starting out with Aurelia</a></li></ul><blockquote><em>This post is based on a tutorial, you can find the latest version in </em><a href="https://community.sensenet.com/_docs/tutorials/starting-out-with-mvc"><em>this article</em></a><em>.</em></blockquote><h3>What will we build?</h3><p>This MVC sample application will be a very simple CRUD app: it will display a dashboard with tasks assigned to the current user and another list for other users’ tasks. It will also let users create and delete tasks.</p><p>This architecture means a web application with custom code added on the <strong>server side in C# and cshtml</strong>. For a Javascript single page application example please visit one of the links above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/0*6roYcxnRq62M6kKg.PNG" /></figure><p>When completing this short excercise, please try to focus on the sensenet-related parts — for example the way we search for content items and load them from the Content Repository, the way we create and modify content. We tried to keep everything else minimal so you can focus on the new stuff and not on the usual MVC-related parts.</p><h4>Security out of the box</h4><p>All the sensenet ECM Content-related operations (like content Save or Load) are performed using the <strong>permissions of the currently logged in user</strong> — except when switching to the administrator for technical purposes, as we explain below. This means that the user will not be able to create or delete anything that he or she does not have permissions for.</p><h3>Prerequisites</h3><p>You will need a basic MVC project to begin with and install one or more sensenet ECM components.</p><blockquote><em>For the purpose of this guide you will need the basic </em><strong><em>sensenet Services</em></strong><em> package and also the </em><a href="https://community.sensenet.com/docs/install-webpages-from-nuget/"><em>WebPages</em></a><em> component, because it will let you sign in easily and monitor the created content items.</em></blockquote><p>There are two options here:</p><ul><li>Install <a href="https://community.sensenet.com/docs/install-sn-from-nuget">sensenet ECM Services from NuGet</a> and also the <a href="https://community.sensenet.com/docs/install-webpages-from-nuget/">WebPages</a> component: this way you will create a brand new MVC application, pull in the necessary packages from NuGet and make a few modifications manually.</li><li>Or you can copy one of the prebuilt <a href="https://github.com/SenseNet/sn-vs-projecttemplates">sensenet ECM project templates</a>. Those templates contain the <strong>same NuGet packages</strong>, they just save you the time of manually installing them. Our suggestion is to start with the one that contains the <a href="https://github.com/SenseNet/sn-vs-projecttemplates/tree/master/src/SnWebApplicationWithWebPages">Services and WebPages</a> packages. The steps in this case:</li></ul><ol><li>copy the template</li><li>build the solution</li><li>execute the <strong>same install commands</strong> as at the end of the install guides above. These commands will create a database for you and import the necessary content items (please take a look at the install guides above for more details). In case you chose the two main packages, this means the following commands:</li></ol><pre>snadmin install-services<br>snadmin install-webpages</pre><p>After the steps above, you will have an MVC application with sensenet ECM 7.0 integrated. The remaining part of this article is about how to add a basic CRUD functionality for content items in Visual Studio.</p><blockquote><em>It is important to make sure when working with a sensenet ECM web application that you shut down the application properly when you update the server code. This means stopping the IIS Express site so that sensenet ECM can release the index write lock correctly — otherwise you would have to delete that file manually when you start the app next time.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/0*_nK0DEQXQuHOVY2J.PNG" /></figure><h3>Authentication</h3><p>To demonstrate a use case for different users, this sample is designed to display Tasks for the current user and (in a different list) tasks for others. Asp.Net MVC authentication however is <em>not the scope of this guide</em>, so we will use the old built-in WebForms-based UI for signing in and possibly create new users for testing purposes.</p><p>We will not make use of the Asp.Net <em>Identity</em> feature, because currently there is no Identity storage implemented for sensenet ECM (yet).</p><p>We need to change the default <strong>Login</strong> link in the header to redirect to the default sensenet ECM main page that contains a login control. To do that, please modify the <em>_LoginPartial</em> view (in the <em>Shared</em> folder in VS): replace the Login action link at the bottom of the view with the following html link:</p><pre>&lt;a id=&quot;loginLink&quot; href=&quot;/Root/Sites/Default_Site&quot;&gt;Login&lt;/a&gt;</pre><p>Start the site and click on the login link to verify that it leads you to the sensenet ECM login page and you can log in with the default admin credentials (<em>admin/admin</em>).</p><p>For the <strong>Logout</strong> link to work and the signed-in user info to be correct, we have to modify the <strong>form submit link</strong> and the user link in the same <em>_LoginPartial</em> view in the case when the user is authenticated.</p><p>The final version of the view is the following:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d08bae5f6e935c01488484ae703e473b/href">https://medium.com/media/d08bae5f6e935c01488484ae703e473b/href</a></iframe><p>Notice the <em>BeginRouteForm</em> method above that we use to generate a correct link that redirects to the Logoff action in the built-in Account controller.</p><h4>Logging off</h4><p>For the logoff mechanism to work correctly, please modify the LogOff method in the <em>AccountController</em> class (<em>Controllers</em> folder in VS) to execute the sensenet logout logic.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e6e65f8148a0b3beb5bb481241bd0b05/href">https://medium.com/media/e6e65f8148a0b3beb5bb481241bd0b05/href</a></iframe><blockquote><em>The </em>AuthenticationHelper<em> class above provides methods for logging in and out, you can use them in your custom code too.</em></blockquote><h3>Task view model</h3><p>Our goal is to display tasks on the UI. For that we need a model for task items. Please create a new class named <em>TaskViewModel</em> in the <em>Models</em> folder in VS and fill it with the following class:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/51a22b65b287171612effba7a61bdeb3/href">https://medium.com/media/51a22b65b287171612effba7a61bdeb3/href</a></iframe><p>The model above takes a sensenet ECM Task instance in the constructor and exposes a few properties. There are several built-in strongly typed properties like DisplayName, and there is an extensive api for accessing dynamic properties — for example the <em>GetReference</em> method lets you load referenced content items, in this case the assignee user.</p><blockquote><em>Note that there are several other ways to create a model on top of sensenet ECM content items — for example you can create a model that wraps a </em>Content<em> object instead of a strongly-typed business object like Task above (that will let you work with the field layer instead of strongly typed properties). Or you can even use these types (Task or Content) </em>as your model<em>, without creating a model class.</em></blockquote><blockquote><em>The </em><strong><em>SystemAccount.Execute</em></strong><em> call above is necessary for cases when the current user does not necessarily have permissions for a </em>referenced content<em> — in this case the assigned user. This is a trick for loading data from the repository as an administrator and displaying only the required info to the user.</em></blockquote><h3>Dashboard view model</h3><p>To serve the task lists to the view, we create a view model for the dashboard. Please create a new class in the <em>Models</em> folder in VS and name it <em>DashboardViewModel</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3b25afe66b25fd2e26ce760cee13e08c/href">https://medium.com/media/3b25afe66b25fd2e26ce760cee13e08c/href</a></iframe><blockquote><em>Note that we expose </em><strong><em>two Task model lists</em></strong><em> here as properties. One of them (My tasks) is implemented using the </em><a href="http://wiki.sensenet.com/LINQ_to_Sense/Net"><em>LINQ to sensenet</em></a><em> technique, the other one executes a simple </em><a href="http://wiki.sensenet.com/Content_Query_syntax"><em>Content Query</em></a><em> for task content items. The result is very similar in the background, you may choose either of them when searching for content items.</em></blockquote><h3>Dashboard controller</h3><p>The next step is to create a controller for serving the UI the necessary views. Create a new empty controller named <em>DashboardController</em> in Visual Studio (<em>Controllers</em> folder) and fill it with the following code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7b89b21c391967bc96eea85b533662ec/href">https://medium.com/media/7b89b21c391967bc96eea85b533662ec/href</a></iframe><p>The initial Index action simply returns a view. We will fill this class with additinal action methods later for POST requests.</p><h3>Dashboard view</h3><p>To create views for the dashboard, please create a new folder named <em>Dashboard</em> in the <em>Views</em> folder in VS.</p><p>Create an empty <em>Index</em> view in the Dashboard folder without a layout page, and fill it with this initial markup:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a4a5d50c0ae81624353ccbe78a355c22/href">https://medium.com/media/a4a5d50c0ae81624353ccbe78a355c22/href</a></iframe><h4>Dashboard link</h4><p>To access the dashboard page, please insert a link to the header in the <em>_Layout.cshtml</em> file (around line 27)</p><pre>&lt;li&gt;@Html.MvcActionLink(&quot;Dashboard&quot;, &quot;Index&quot;, &quot;Dashboard&quot;)&lt;/li&gt;</pre><p>When you start the site, you should be able to log in and visit the dashboard page using the new link in the header. It will contain no tasks yet, so we need to add the possibility for the user to manage tasks.</p><h3>Adding and Deleting a Task</h3><p>Let’s add a few things to the task view model so that it becomes capable of handling task creation. Please modify the <em>TaskViewModel</em> class that we created above to its final form:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/49b81016b5f04f27c681c1be64d84180/href">https://medium.com/media/49b81016b5f04f27c681c1be64d84180/href</a></iframe><p>The new properties make it easier to build a UI for creating new tasks — for example selecting a person that the task is assigned to.</p><h3>Adding the Create and Delete views</h3><p>Add new empty view in the <em>Views/Dashboard</em> folder and name it <em>Create</em>.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/19d7ecb21180b973a94b3369935ba5c2/href">https://medium.com/media/19d7ecb21180b973a94b3369935ba5c2/href</a></iframe><p>This view shows a form with a few task fields to fill. For example there is a <strong>dropdown list</strong> containing the users coming from the task view model property.</p><p>Create another view named <em>Delete</em> in the <em>Views/Dashboard</em> folder with the following contents:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6c2ebff001a2fa06ba1eb5587dca6c6c/href">https://medium.com/media/6c2ebff001a2fa06ba1eb5587dca6c6c/href</a></iframe><p>The <em>Delete</em> view above uses the <em>BeginRouteForm</em> extension method to build a form url that contains the <strong>id of the task</strong> to be deleted.</p><h3>Add new methods to the controller</h3><p>To display the Create and Delete views and to perform the actual operations, you will have to add a few methods to the <em>DashboardController</em> class. The final form of the controller is the following:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1a3c87d9c89722ce798aa4baadf0a168/href">https://medium.com/media/1a3c87d9c89722ce798aa4baadf0a168/href</a></iframe><p>The Create action receives a task view model filled with the data from the client. It makes sure that the <strong>parent container (the Task List) exists</strong> before adding a new task.</p><p>The new task’s fields are filled from the model and the new content is saved into the Content Repository. All <strong>database operations</strong>, <strong>indexing</strong> and <strong>security checks</strong> will happen under the hood, you do not have to do anything else, just fill the fields and call the Save method.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/0*EEZw3WsK9RkIF1YG.PNG" /></figure><p>The <em>DeletePost</em> method (note that we had to name it differently to avoid a name collision) is simple: it deletes the content with the provided id — it does not even have to load it from the db.</p><h3>Extend the Dashboard Index view</h3><p>To display links for the new Create and Delete actions above, please modify the <em>Index.cshtml</em> file in the Views/Dashboard folder to its final form:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f4025b5f6b49709041febb6085d269a2/href">https://medium.com/media/f4025b5f6b49709041febb6085d269a2/href</a></iframe><p>We added a Create link at the top and Delete links to the tables on both sides.</p><p>If you successfully completed the steps above, you will be able to manage Tasks on the Dashboard of your first sensenet ECM MVC site!</p><h3>What’s next?</h3><p>The example above is very simple and limited. In the future we would like to add more helpers to simplify the creation of <strong>route links</strong> in cshtml files and new components for aiding <strong>authentication</strong>.</p><p>Please experiment with the code, try to use your own MVC techniques and <a href="https://community.sensenet.com/contact/">contact us</a> if you stuck at some point or need a new feature!</p><p>Photo by <a href="https://unsplash.com/photos/imBSxksI7DA?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Cam Adams</a> on <a href="https://unsplash.com/search/photos/start?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p><em>Originally published at </em><a href="https://community.sensenet.com/blog/2018/01/31/Getting-started-MVC"><em>community.sensenet.com</em></a><em> on January 31, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd9d84b50c8d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sensenet/getting-started-with-sensenet-ecm-using-mvc-bd9d84b50c8d">Getting started with sensenet ECM using MVC</a> was originally published in <a href="https://medium.com/sensenet">sensenet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First OAuth implementation in sensenet ECM]]></title>
            <link>https://medium.com/sensenet/first-oauth-implementation-in-sensenet-ecm-581bd63809f7?source=rss-307e79fab514------2</link>
            <guid isPermaLink="false">https://medium.com/p/581bd63809f7</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[oauth2]]></category>
            <category><![CDATA[authentication]]></category>
            <dc:creator><![CDATA[Miklós Tóth]]></dc:creator>
            <pubDate>Wed, 20 Dec 2017 00:00:00 GMT</pubDate>
            <atom:updated>2017-12-21T09:10:07.516Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Re4rFAX-S2f0qylpIEtuNA.jpeg" /></figure><p>Identifying users is one of the most important features in an ECM solution. In <a href="https://github.com/SenseNet/sensenet">sensenet ECM</a> we try to support a wide range of possibilities in this field, this is why we made this a lot easier by extending our <a href="https://community.sensenet.com/docs/web-token-authentication">web token authentication</a>: from now on it is possible to integrate a 3rd party authentication service, for example <a href="https://developers.google.com/identity/sign-in/web/sign-in">Google Sign-in</a> into your sensenet ECM solution.</p><p><a href="https://oauth.net/2/">OAuth 2.0</a> is the industry-standard protocol for authorization. In sensenet ECM we use it as an extension to our JWT authentication to let users <strong>authenticate</strong> using well-known services (such as Google or Facebook). The benefit is that users are able to sign in to a sensenet ECM application with a single click, <strong>without manual registration</strong>. This post gives you an insight on how OAuth is implemented on the server side, shows how the sensenet client libraries support it and quickly demonstrates how you can build it into your app.</p><blockquote><em>In the first iteration we only implemented </em>Google Sing-in<em>, but you can add other services (like Facebook) if you follow the steps and links in this post. If you do that, please consider sharing it with the </em><a href="https://community.sensenet.com/"><em>community</em></a><em> so that others can use it too!</em></blockquote><h3>How it works</h3><p>When new users come to the site, they will be able to sign in by clicking the Google button (or a similar custom experience implemented by the developer). The workflow is the following:</p><ol><li>The user signs in to the 3rd party service.</li><li>The user authorizes the application with the service (e.g. lets the application access basic user data like name and email). This is usually a click of a button in the Google or Facebook popup window.</li><li>The client receives a <strong>token</strong> from the service.</li><li>The client sends the token to the sensenet ECM server, where the appropriate OAuth provider <strong>verifies</strong> the token (note that this way it is not possible to send an invalid or expired token, because it is verified with the 3rd party service).</li><li>If the token has been verified, we <strong>load or create</strong> the corresponding User content in the Content Repository. User content items are connected to the 3rd party service by storing the unique user identifier in a provider-specific separate field (e.g. <em>GoogleUserId</em>).</li><li>sensenet ECM asssembles a JWT token for the client and considers the user as correctly signed in.</li></ol><p>From that point on the user will be able to use the application as a regular user and there is no further connection with the 3rd party service or its token. We use our own JWT token to identify the user in subsequent requests.</p><p>A sensenet ECM OAuth provider is a small .Net plugin that is designed to verify a token using a particular service. Out of the box we offer only the <a href="https://github.com/SenseNet/sn-oauth-google">Google OAuth provider</a> which is available as a NuGet package.</p><blockquote><em>In the future we will add more options (like Facebook Login), but you can also </em><a href="https://community.sensenet.com/docs/oauth/"><em>integrate any 3rd party service</em></a><em>.</em></blockquote><p>If you are using <a href="https://github.com/SenseNet/sn-client-js">sn-client-js</a> and/or <a href="https://github.com/SenseNet/sn-redux">sn-redux</a>, you do not have to deal with sending OAuth tokens to the server, they will do it for you.</p><h3>sn-client-js</h3><p>We’ve added OAuth provider support in version 3.0.0. This means that you can implement and add your own client side OAuth provider — just like we did in <a href="https://github.com/SenseNet/sn-client-auth-google">sn-client-auth-google</a>.</p><h3>sn-client-auth-google 1.0.0</h3><p>This is our first official client-side OAuth provider. It requires sensenet ECM ^7.0.0 with configured JWT authentication, an installed SN7 <a href="https://github.com/SenseNet/sn-oauth-google">OAuth provider</a> and a <a href="https://developers.google.com/identity/sign-in/web/devconsole-project">Google API Console project</a>. You can use it with or without the official <a href="https://developers.google.com/identity/sign-in/web/sign-in">Google Platform Library</a> or any third party component that can retrieve an <em>id_token</em>.</p><p>We’ve focused on keeping this library straightforward and easy-to-use, hopefully you can integrate it within a few minutes — after checking an example in the <a href="https://github.com/SenseNet/sn-client-auth-google">readme</a>.</p><h3>sn-redux</h3><p>Since the needed provider was ready both on the backend and in <a href="https://github.com/SenseNet/sn-client-js">sn-client-js</a> it was a must to add an action to handle login (and registration) with Google account in sn-redux too. However the after-login process is the same: a new epic called userLoginGoogleEpic is created. This new epic is subscribed to the new login request action, but regardless of the success of the result, it dispatches the same actions that are used in the simple login process.</p><h3>Example</h3><p>Let us demonstrate how easy you can add the above to your app through the steps that were made adding Google authentication to our DMS Demo.</p><ol><li>Install <a href="https://github.com/SenseNet/sn-client-auth-google">sn-client-auth-google</a> with npm and import AddGoogleAuth</li></ol><pre>npm i --save-dev sn-client-auth-google </pre><pre>import { AddGoogleAuth } from &#39;sn-client-auth-google&#39;;</pre><p>2. Activate Google authentication on your repository object with your app’s/site’s ClientId</p><pre>...<br>AddGoogleAuth(repository, {<br>   ClientId: &#39;yourclientid&#39;<br>})<br>...</pre><p>3. Create your custom button or link component, import Actions from <a href="https://github.com/SenseNet/sn-redux">sn-redux</a> and now you’re able to access the UserLoginGoogle function and you can dispatch it in the event handler where it is neeeded.</p><pre>...<br>import { Actions } from &#39;sn-redux&#39;<br>...<br><br>class myButton extends React.Component&lt;{login: Function},{}&gt;{<br>    ...<br>    handleButtonClick(e){<br>        this.props.login<br>    }<br>    ...<br>    render(){<br>       return &lt;div onClick={e =&gt; this.handleButtonClick(e)}&gt;Sign in with Google&lt;/div&gt;<br>    }<br>}<br>...</pre><pre>export default connect({}, {<br>    login: Actions.UserLoginGoogle<br>})(myButton)</pre><h3>Next steps</h3><p>As this is only the first iteration, we deliberately made this release very small. For example:</p><ul><li>we do not sync custom properties, like user avatar</li><li>the Google provider on the server verifies the token using the public <em>http Google API</em>, which means the server has to have access to that API. In the future this may be changed to local token verification using the Google SDK.</li><li>Facebook, Microsoft and GitHub login options are not available yet</li></ul><p>Do you feel the power to help the <a href="https://community.sensenet.com/">community</a> with extending the platform with your ideas? Please <a href="https://community.sensenet.com/contact/">contact us</a>, participate in the conversation and help us make tools for the benefit of other developers!</p><p>Have feedback on this post? Let <a href="https://twitter.com/sensenet">@sensenet</a> know on Twitter.</p><p>Need help or found a bug? <a href="https://community.sensenet.com/contact">Contact us</a>.</p><p><em>Originally published at </em><a href="https://community.sensenet.com/blog/2017/12/20/first-oauth-implementation"><em>community.sensenet.com</em></a><em> on December 20, 2017.</em></p><p>Photo by <a href="https://unsplash.com/photos/ahi73ZN5P0Y?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Federico Beccari</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=581bd63809f7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sensenet/first-oauth-implementation-in-sensenet-ecm-581bd63809f7">First OAuth implementation in sensenet ECM</a> was originally published in <a href="https://medium.com/sensenet">sensenet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[sensenet ECM 7 stable release is out]]></title>
            <link>https://medium.com/sensenet/sensenet-ecm-7-stable-release-is-out-8de021d02601?source=rss-307e79fab514------2</link>
            <guid isPermaLink="false">https://medium.com/p/8de021d02601</guid>
            <category><![CDATA[ecm]]></category>
            <category><![CDATA[platform]]></category>
            <category><![CDATA[release-notes]]></category>
            <dc:creator><![CDATA[Miklós Tóth]]></dc:creator>
            <pubDate>Wed, 06 Dec 2017 00:00:00 GMT</pubDate>
            <atom:updated>2017-12-07T10:47:56.689Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to the <a href="https://github.com/SenseNet/sensenet/releases">stable release</a> of sensenet ECM 7.0!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MDZESoE3MTULL_l8buvzpw.jpeg" /></figure><p>Actually, this is not a big deal from a technical point of view: there were a few bug fixes, some interesting new features (like supporting <em>Google Sign-in</em>), but there is not much more in there than in previous releases.</p><p>But from the product’s point of view — well, this is a <em>giant leap</em> forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/858/0*neU8Y_4L3CfWzs5o.jpg" /></figure><h3>Ready to go</h3><p>The ones who’ve been following our journey from <em>sensenet 6</em> to <em>sensenet 7</em> know that we did not actually change much in terms of source code. Of course we had to slice the whole thing into <a href="https://community.sensenet.com/docs/sensenet-components/">components</a>, but we tried to keep everything intact. This is why we think that you can safely go into production with this release — because the majority of the code is already in production on many sites with sensenet 6!</p><p>Another reason to let this into production is that from now on we will publish <strong>patches</strong>. That means you will not have to start from scratch in your production environment (which is of course not an option), but execute the patches published by us (or maybe 3rd party vendors who publish sensenet ECM components).</p><blockquote><em>It is still advisable to work with a </em><strong><em>clean database</em></strong><em> workflow in your </em><strong><em>development and test environment</em></strong><em>. The best practice is to create a CI build that is able to re-create your whole site and database from scratch, including installing sensenet ECM.</em></blockquote><h3>Upgrades in the future</h3><p>Until this point we published pre-release versions of the product on <a href="https://www.nuget.org/packages?q=sensenet">nuget</a> and on <a href="https://github.com/SenseNet/sensenet/releases">GitHub</a> as well. We did not publish patches that would work as in-place upgrades on an existing sensenet ECM installation.</p><blockquote><em>That changes now.</em></blockquote><p>From now on we will assemble a proper <a href="https://github.com/SenseNet/sn-admin"><strong>SnAdmin</strong></a><strong> package</strong> for every release we publish. Sometimes it will contain real content repository changes (e.g. a script that changes the db schema or added/modified content items), sometimes it will just bump the component version in the repo.</p><p>When developers get the new version from nuget, they will have to execute an SnAdmin command (in the command line) with the patch. In some cases (very rarely) there may be some additional manual steps, but we will explain those in detail and we plan to avoid that if possible.</p><h3>Beta packages</h3><p>Will we publish beta releases in the future? Of course! It helps our community a lot if we are able to show you what are we working on and try to collect feedback before publishing a stable release. Just do not push these into production, because that would involve manual patching in the future, which can be risky.</p><h3>Components with different versions</h3><p>As sensenet ECM is built from many <a href="https://community.sensenet.com/docs/sensenet-components/">components</a>, these components are released in a different pace (in fact, we released a stable version of the two main components first, <em>Services </em>and <em>WebPages </em>— the others will follow soon). In some cases there will be version dependencies among components (e.g. one component’s latest version cannot work without upgrading a different one), but we will state these prerequisites when releasing a component — and of course nuget packages will force those dependencies too.</p><h3>What’s next?</h3><p>The journey does not stop here of course! We have many features to add and architectural improvements to make (take a look at the post about our <a href="https://community.sensenet.com/blog/2017/11/29/sn-frontend-releases-in-november">frontend release</a> for example).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3BBkf-vNd7IoTsmn.jpg" /></figure><p>The next major release is planned to include the <strong>Search infrastructure improvements</strong> we have been working on in the last several months.</p><p>We also plan to modernize our <strong>messaging backbone</strong> to make it suitable for cloud installations (meaning replace good old <em>MSMQ</em> with a more modern service).</p><p><a href="https://technet.microsoft.com/en-us/library/jj219437.aspx">Office Web Apps Server</a> integration is also something we would very much like to add to our feature stack.</p><p>Stay tuned for releases in the near future and please <a href="https://community.sensenet.com/contact/">contact us</a> if we can help you with anything!</p><p><em>Originally published at </em><a href="https://community.sensenet.com/blog/2017/12/06/release-7.0-stable"><em>community.sensenet.com</em></a><em> on December 6, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8de021d02601" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sensenet/sensenet-ecm-7-stable-release-is-out-8de021d02601">sensenet ECM 7 stable release is out</a> was originally published in <a href="https://medium.com/sensenet">sensenet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everything is a Content]]></title>
            <link>https://medium.com/sensenet/everything-is-a-content-f34514330e3c?source=rss-307e79fab514------2</link>
            <guid isPermaLink="false">https://medium.com/p/f34514330e3c</guid>
            <category><![CDATA[ecm]]></category>
            <category><![CDATA[repositories]]></category>
            <category><![CDATA[content]]></category>
            <dc:creator><![CDATA[Miklós Tóth]]></dc:creator>
            <pubDate>Wed, 12 Jul 2017 00:00:00 GMT</pubDate>
            <atom:updated>2017-07-13T08:32:52.470Z</atom:updated>
            <content:encoded><![CDATA[<p>The foundation of sensenet ECM is the Content Repository, where documents, tasks, users, projects — everything is a Content. It is the fundamental building block of the system that makes content management easy and powerful at the same time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*23BBSBM-IXd5gdjBKB30kA.jpeg" /></figure><p>Using content items everywhere unlocks a great deal of exceptional features that make your experience as a user more seamless, and your job as a developer a lot easier. Focus on the business problem — the platform handles the rest!</p><h3>Why is this a cool thing?</h3><h4>Unified, easy-to-learn techniques for working with content</h4><p>How do you change document metadata? Edit its properties! How do you modify a User, or add details to a Task? Well, Edit its properties, of course! A unified user interface: same menus, same buttons, same operations help feel familiar with every part of the system immediately.</p><h4>Services and actions available for all content</h4><p>If there is a new feature, it can be enabled for all kinds of content immediately — think of the Copy or Delete actions for example. You can copy a file or a whole workspace the same way.</p><p>This goes for your custom actions too! You can define new features and enable them for all kinds of content — or just for the types you need them for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/0*R3F21rGMhquRCSJJ.png" /></figure><h4>Content management in a central place</h4><p>If everything is a content, why not store and manage them in a central place? You’ll find every single item in the Content Repository in our huge content tree! Combined with a powerful search engine this makes content discovery a no-brainer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/173/0*ZixV6-n0-Fp2AzOY.png" /></figure><p>The built-in Content Explorer, our admin UI lets you browse, edit and manage content — the whole tree — in a familiar, rich environment.</p><p>Do you have questions? <a href="http://community.sensenet.com/contact">Contact us</a> and let us help!</p><h3>Got it, give me the features!</h3><p>Although it is virtually impossible to squeeze every important feature of a modern enterprise content management system into a single article, we wanted to give you a glimpse of what sensenet ECM is capable of when it comes to document management.</p><h4>Custom metadata</h4><p>A unified content infrastructure lets you define custom metadata fields on a high level and use them on specific types. The Display name field for example is defined on the base Content Type called GenericContent — and that gives you a display name field for basically every content in the system!</p><h4>Presentation</h4><p>It is just a single step from storing data in a unified way to displaying it using predefined UI building blocks. Create and re-use field controls and content views, and speed up your development process by assembling skins, pages and page templates — which are also content themselves ;-).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/0*EN4cZ8yk0qo5ncrb.png" /></figure><h4>Version history</h4><p>It takes only a few clicks to enable versioning — not just for files, but for any kind of content! Want to keep old versions of a Memo or a Task? Choose from the available versioning modes, and you’re good to go! You can switch this on in a library, a workspace, or any level in the Content Repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/0*HPbM-_Uj3hDCNUrW.png" /></figure><h4>Approval</h4><p>Collaborate with others on documents, specifications, tasks! The built-in simple approval process that can be enabled for any kind of content makes the usually cumbersome and time-consuming process super-easy and fast in sensenet ECM.</p><h4>Permission on content level</h4><p>The security system that is built into the core layer of sensenet ECM lets you manage permissions on the level of your choice: it is easy to define them on a workspace or library, but if you need to, you can even control the accessibility of a single content — be it a document, a group or a JavaScript file.</p><h4>Fast search by metadata</h4><p>A unified Content Repository extended with our Lucene search engine lets you find the content you need quickly. You can also create complex queries in an easy-to-master query language to build the flexible and rich user interface you imagined.</p><p>For more information please check the following pages:</p><ul><li><a href="https://www.sensenet.com/try-it">Try it</a> — without installation</li><li><a href="https://www.sensenet.com/for-customers/use-cases">Top use cases</a> — how others use sensenet ECM</li></ul><p><em>This post was originally published on the </em><a href="http://community.sensenet.com/blog/2017/07/12/everything-is-a-content"><em>official blog of Sense/Net Inc.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f34514330e3c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sensenet/everything-is-a-content-f34514330e3c">Everything is a Content</a> was originally published in <a href="https://medium.com/sensenet">sensenet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why NuGet?]]></title>
            <link>https://medium.com/sensenet/why-nuget-3683013966b6?source=rss-307e79fab514------2</link>
            <guid isPermaLink="false">https://medium.com/p/3683013966b6</guid>
            <dc:creator><![CDATA[Miklós Tóth]]></dc:creator>
            <pubDate>Tue, 20 Jun 2017 00:00:00 GMT</pubDate>
            <atom:updated>2017-06-28T12:54:09.198Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the most important aspects of a modern software is how to get it into the hands of customers. Especially developers, because they are the ones who will spend most of their time working with our libraries and components.</p><p>In the last couple of years we published sensenet ECM as source and binary install packages, and after installing either of them, developers had to copy libraries around and take care of references themselves. We knew that we have to come up with something easier. A more reliable and modern way to distribute our components as fast as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KnxCjeHUdJlNVuMj.jpg" /></figure><p>We chose <a href="https://www.nuget.org/packages?q=sensenet">nuget.org</a> to publish the bits of our ECM platform, because in the .Net world that is the de-facto standard for delivering libraries. We want to be where our developers are, where they are looking for products and plugins (this is why we are moving our source code to <a href="http://community.sensenet.com/blog/2017/05/23/moving-to-github">github</a>).</p><p>If you are not a developer, don’t panic. We are working on another way to distribute sensenet ECM: an <a href="https://github.com/SenseNet/sn-installer">installer</a> with a nice user interface for the ones who prefer that. This post is for developers who feel comfortable in their well-known environment, Visual Studio, and want a familiar way to get started with <strong>sensenet ECM 7.0</strong>.</p><blockquote><em>The previous version, </em><strong><em>sensenet ECM 6.5</em></strong><em> is still distributed the old way, as a source package and a Web Platform Installer package.</em></blockquote><h3>Install only what you need</h3><p>Another reason why we chose NuGet is that it lets us publish our platform in small, separate components and let you install only the ones that you actually need in your project. Search for ‘sensenet’ in NuGet Package Manager in Visual Studio to see all our packages (remember to switch on the ‘Include prerelease’ checkbox to access the latest ones).</p><p>Take a look at <a href="http://community.sensenet.com/docs/sensenet-components">this article</a> for details about the components we offer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*D2vgV6Azijbx7rGQ.png" /></figure><h3>No more moving dlls around</h3><p>We want you to think in packages instead of dlls. We still compile sensenet ECM into multiple dlls, but you do not have to know how many there are and copy or reference those libraries manually. That is one of the coolest advantage of moving to NuGet.</p><p>Even if you want to modify the core source code (we would be glad if you decide to help our community by <a href="https://github.com/SenseNet/sensenet/blob/master/CONTRIBUTING.md">contributing</a> to the project!), you can create your own personal NuGet packages using the scripts we also publish, and distribute those modified packages in a custom (public or private) NuGet feed.</p><h3>Do you deliver a full ECMS through NuGet, seriously?</h3><p>We are aware that NuGet was designed to distribute small components that contain a few libraries — and sensenet ECM is much more than that. We publish configuration files, database scripts and other file system content along with dlls. After importing the necessary packages into your solution, you will still have to make a few steps manually and complete the installation process in the command line, but at least it is a lot easier than before.</p><p>To be able to pull this off, we had to split our packages into two parts: there is a base package that you can import into any kind of project, because it contains only libraries. And there is a corresponding ‘install’ package that you should import only into your web application project. Do not worry, it is easier than it sounds, see the details in the following article:</p><ul><li><a href="http://community.sensenet.com/docs/install-sn-from-nuget">Install sensenet ECM from NuGet</a></li></ul><p><em>This post was originally published on the </em><a href="http://community.sensenet.com/blog/2017/06/20/why-nuget"><em>official blog of Sense/Net Inc</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3683013966b6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sensenet/why-nuget-3683013966b6">Why NuGet?</a> was originally published in <a href="https://medium.com/sensenet">sensenet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>