Rework of the getting started guide (#270)

* Rework of the getting started guid

* Small improvements

* update the docs on tools and source deployment

* Add reference to source deployment

Author: helto4real

docs/user/started/assets/add_on_configuration.png

@@ -0,0 +1,41 @@
+---
+id: development_source_deploy
+title: Get started with NetDaemon app development
+---
+
+### Deploy source files and configurations
+
+With this option you can deploy the actual source code and NetDaemon will
+compile them and use it dynamically.
+
+This option offers:
+
+- Easy access and editing your apps with integrated editor like VS Code server.
+- Limited DI support.
+- Does **not** support custom nuget packages.
+
+Deployment is done by copying source code and config files under your apps folder
+(.cs and .yaml ) to the destination.
+The provided debug project should never be copied.
+
+**We always recommend to deploy your binaries as described in the main getting started guide**
+
+#### Use the source code deployment template
+
+```bash
+dotnet new --install NetDaemon.Templates.Project
+mkdir NetDaemonApps
+cd NetDaemonApps
+dotnet new nd-src-project
+```
+
+### Source files and configurations
+
+**Do not copy project files. Only copy the contents under the `apps` folder!**
+Copy the content from the `apps` folder to to `/config/netdaemon5` if you are using
+add-on (note that you might have changed the destination in add-on config),
+or the destination folder you chose in the other hosting options.
+**Do not copy project files. Only copy the contents under the `apps` folder!**
+
+See [installation docs](user\started\installation.md) for how to configure
+different hosting options.

docs/user/started/assets/netdaemon_add_on.png

@@ -0,0 +1,90 @@
+
+# Configure your development tool
+
+We support most popular options. We strongly recommend using containers to run
+and debug your apps but local compilation and debugging is also supported.
+We provide a Docker file in the project template to use as a start and a
+dev container for VSCode.
+
+## Visual Studio
+
+You should be all set, so skip to step 3.
+:::note
+
+To use Visual Studio's publish feature first install & configure the [Samba share Home Assistant addon](https://github.com/home-assistant/addons/blob/52bafd68185080e9b1a1d6b6c501ab96705d73f9/samba/DOCS.md), then configure your VS publish options:
+
+![Visual studio profile settings](/img/docs/started/vs_publish_config.jpg)
+
+Now you can publish to quickly deploy files, and restart NetDaemon to run them.
+:::
+
+## Visual Studio Code
+
+Dev Containers are the preferred way to develop your apps.
+This also requires Docker to be installed. You can also
+develop and debug directly on your dev machine without Docker.
+
+1. Install [Remote Development extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack)
+in VS Code if you have not already.
+2. Open folder, the newly cloned template
+3. Run task: `Dev Containers: Open Folder in Container...`. Wait until it fully opened
+
+## JetBrains Rider
+
+Just as with Visual Studio it is ready to go for local compile
+and debugging of your apps.
+
+Rider supports debugging of containerized ASP.Net Core apps from version 2018.2.
+
+Open the netdaemon_app folder in Rider and it should be able to build
+the projects immediately. A default execute and debug profile will be
+created however these will be executed as local processes. The preferred
+way to develop your app is to use a container, which requires Docker to be installed.
+To configure a container, perform the following steps:
+
+1. Locate `Dockerfile` in the Solution Explorer window
+2. Right click and select `Debug Dockerfile`
+3. This will create a new profile called "DOCKERFILE"
+4. To view progress, located "Docker" in the "Services" tab and double-click it
+5. Like all container apps, the first build may take a few minutes - watch the progress in the "Services / Docker" tab
+
+Ensure that the "DOCKERFILE" profile is selected in the toolbar and then `Run` and `Debug` will execute within the container.
+
+## Studio Code Server Addon
+
+### Setup
+
+1. In Home Assistant go to Configurations -> Add-ons, Backups &
+Supervisor -> Add-on Store -> Menu -> Repositories
+2. Add the repository: [https://github.com/hassio-addons/repository](https://github.com/hassio-addons/repository)
+3. Install the `Studio Code Server Addon` (a0d7b954_vscode)
+4. In the add-on configuration Tab add the following config:
+
+   ```yaml
+   init_commands:
+     - >-
+       wget
+       https://packages.microsoft.com/config/debian/12/packages-microsoft-prod.deb
+       -O packages-microsoft-prod.deb
+     - dpkg -i packages-microsoft-prod.deb
+     - rm packages-microsoft-prod.deb
+     - apt-get update
+     - apt-get install -y apt-transport-https
+     - apt-get update
+     - apt-get install -y dotnet-sdk-9.0
+     - dotnet tool install -g NetDaemon.HassModel.CodeGen
+   packages: []
+   log_level: info
+   config_path: /
+   ```
+   --> The part in the `init_commands` will install .NET SDK 9.0 only in the
+   Studio Code Server add-on (Docker Container)
+5. Now you can start the Studio Code Server add-on by going the
+add-on information tab and pressing `OPEN WEB UI`.
+
+HINTS:
+
+- It is recommended to install the C# Extensions (ms-dotnettools.csharp) in Studio Code
+Server to get Semantic Highlighting and IntelliSense.
+- Open only the folder where the solution/project is located to ensure that the C#
+Extension works properly.