<commit_before>---
title: "Install sensenet 7.0 from NuGet"
source_url: 'https://github.com/SenseNet/sensenet/blob/master/docs/install-sn-from-nuget.md'
category: Guides
version: v7.0
tags: [install, nuget, packages, services, sn7]
description: This article is for developers about installing the core layer, sensenet Services, but before getting into that, please take a look at the concept of our install method.
---

# Install sensenet 7.0 from NuGet
This article is **for developers** about installing the core layer, [sensenet Services](https://github.com/SenseNet/sensenet), but before getting into that, please take a look at the concept of our install method.

> **TLDR**: jump to the [Install packages](#InstallPackage) section to get started right away!

## Why NuGet?
In the last couple of years [NuGet](https://nuget.org) became the industry standard for delivering (mostly open source) libraries and projects. In our case, we take this even further by letting you install a full CMS right from *Visual Studio*. This is not a common scenario, so we have to approach it carefully (the upgrade process is still under development).

## Why so many packages?
sensenet is a huge product consisting of many smaller components (take a look at this curated collection of built-in and 3rd party [components and plugins](https://github.com/SenseNet/awesome-sensenet)) that are not needed by everybody. It is best if you install only the parts you need, so that you can keep maintenance and upgrade costs at minimum. This is why we publish many small packages containing only the minimal set of libraries and content.

About choosing the components you need, take look at [this article](/docs/sensenet-components) that describes the main components briefly.

#### Two packages per component
Some of our components need multiple things to work, for example:
- server-side code (libraries)
- content items that should be imported at install time
- configuration changes

If you have a single project in *Visual Studio* (a web application), this is not a problem. But if you have *multiple projects* (e.g. a business or data layer beside your web app) that also need the sensenet libraries (to access our c# api), you would end up installing content items that are needed only for installation and/or webapp-specific multiple times, in projects that do not need these items.

This is why we decided to publish two types of packages for our components:

1. **SenseNet.Whatever**: contains only libraries. Should be added to *library projects* that need only the references.
2. **SenseNet.Whatever.Install**: has a NuGet dependency on the library package above, and contains installation artifacts: an [SnAdmin](/docs/sn-admin) package, config file or c# code changes/additions, anything that should go only to your web folder, nowhere else.

> **Long story short**: install the *SenseNet.Whatever.Install* package into your *web application* and the basic library package to your other projects.

<a name="InstallPackage"></a>

## Installing sensenet Services

![sensenet Services](https://github.com/SenseNet/sn-resources/raw/master/images/sn-components/sn-components_services.png "sensenet Services")

Watch our video tutorial where one of our developers guide you through the whole process.
<iframe style="margin:auto;width:100%" width="560" height="315" src="https://youtu.be/ZrtiJRg5fSk?rel=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen=""></iframe>

### Create a web project and pull in the package(s)

1. Create a new **ASP.NET web application** (using the MVC template, optionally adding *Web api* or *Web Forms*), or use an existing one.<commit_msg>pasted the correct embed link<commit_after>---
title: "Install sensenet 7.0 from NuGet"
source_url: 'https://github.com/SenseNet/sensenet/blob/master/docs/install-sn-from-nuget.md'
category: Guides
version: v7.0
tags: [install, nuget, packages, services, sn7]
description: This article is for developers about installing the core layer, sensenet Services, but before getting into that, please take a look at the concept of our install method.
---

# Install sensenet 7.0 from NuGet
This article is **for developers** about installing the core layer, [sensenet Services](https://github.com/SenseNet/sensenet), but before getting into that, please take a look at the concept of our install method.

> **TLDR**: jump to the [Install packages](#InstallPackage) section to get started right away!

## Why NuGet?
In the last couple of years [NuGet](https://nuget.org) became the industry standard for delivering (mostly open source) libraries and projects. In our case, we take this even further by letting you install a full CMS right from *Visual Studio*. This is not a common scenario, so we have to approach it carefully (the upgrade process is still under development).

## Why so many packages?
sensenet is a huge product consisting of many smaller components (take a look at this curated collection of built-in and 3rd party [components and plugins](https://github.com/SenseNet/awesome-sensenet)) that are not needed by everybody. It is best if you install only the parts you need, so that you can keep maintenance and upgrade costs at minimum. This is why we publish many small packages containing only the minimal set of libraries and content.

About choosing the components you need, take look at [this article](/docs/sensenet-components) that describes the main components briefly.

#### Two packages per component
Some of our components need multiple things to work, for example:
- server-side code (libraries)
- content items that should be imported at install time
- configuration changes

If you have a single project in *Visual Studio* (a web application), this is not a problem. But if you have *multiple projects* (e.g. a business or data layer beside your web app) that also need the sensenet libraries (to access our c# api), you would end up installing content items that are needed only for installation and/or webapp-specific multiple times, in projects that do not need these items.

This is why we decided to publish two types of packages for our components:

1. **SenseNet.Whatever**: contains only libraries. Should be added to *library projects* that need only the references.
2. **SenseNet.Whatever.Install**: has a NuGet dependency on the library package above, and contains installation artifacts: an [SnAdmin](/docs/sn-admin) package, config file or c# code changes/additions, anything that should go only to your web folder, nowhere else.

> **Long story short**: install the *SenseNet.Whatever.Install* package into your *web application* and the basic library package to your other projects.

<a name="InstallPackage"></a>

## Installing sensenet Services

![sensenet Services](https://github.com/SenseNet/sn-resources/raw/master/images/sn-components/sn-components_services.png "sensenet Services")

Watch our video tutorial where one of our developers guide you through the whole process.
<iframe style="margin:auto;width:100%" width="560" height="315" src="https://www.youtube.com/embed/ZrtiJRg5fSk?rel=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen=""></iframe>

### Create a web project and pull in the package(s)

1. Create a new **ASP.NET web application** (using the MVC template, optionally adding *Web api* or *Web Forms*), or use an existing one.
{'fraction_non_alphanumeric': 0.08178740690589031, 'fraction_numerical': 0.006228842247799593, 'mean_word_length': 4.942075623491553, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 15, 'https://': 12, 'lorem ipsum': 0, 'www.': 1, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3196474', 'n_tokens_mistral': 1930, 'n_tokens_neox': 1872, 'n_words': 987}