1

Topic: Who the thread saws ServiceBase for Nano Server 2016

I will copy an essence from a subject: Who the thread saws System. ServiceProcess. ServiceBase for Nano Server 2016 Like.net core 1.1 made with net standard 1.6, and things are right where they started. Microsoft - a fable  any. A swan a cancer and a pike . Are puffed up and make an effort and a simple and necessary feature which itself  advance to make and could not. Here  in  told that  the server for services and asp.net applications. And how on.net core 1.1 service to write? And as well as on 1.0 - in any way. And all should be made that   which to lift the console application on.net core and on namedpipe  OnStart, OnPause and OnStop.  the difficult. Or it is difficult? P.S. Read and understood - it was necessary in a forum.NET

2

Re: Who the thread saws ServiceBase for Nano Server 2016

Hello, VladCore, you wrote: VC> I Will copy an essence from a subject: Who the thread saws System. ServiceProcess. ServiceBase for Nano Server 2016 VC> Like.net core 1.1 made with net standard 1.6, and things are right where they started. VC> Microsoft - a fable  any. A swan a cancer and a pike . Are puffed up and make an effort and a simple and necessary feature which itself  advance to make and could not. VC> here  in  told that  the server for services and asp.net applications. VC> and how on.net core 1.1 service to write? VC> and as well as on 1.0 - in any way. Write the console application and launch it in the container constructed on basis nanoserver VC> And all should be made that   which to lift the console application on.net core and on namedpipe  OnStart, OnPause and OnStop.  the difficult. VC> or it is difficult? And what for? docker start / docker stop - anything difficult Because Nano Server is optimized as a lightweight operating system for running "cloud-native" applications based on containers and micro-services or as an agile and cost-effective datacenter host with a dramatically smaller footprint, there are important differences in Nano Server versus Server Core or Server with Desktop Experience installations: If service is necessary - use Server Core.

3

Re: Who the thread saws ServiceBase for Nano Server 2016

Hello, VladCore, you wrote: VC> And that should be made all   which to lift the console application on.net core and on namedpipe  OnStart, OnPause and OnStop.  the difficult. nssm does not go? For some reason there is no such software,  to a normal state, but this suits simple cases.

4

Re: Who the thread saws ServiceBase for Nano Server 2016

Hello, TK, you wrote: TK> And what for? docker start / docker stop - anything difficult And how in console application to make that that vital in stop? And where to write docker start/stop if powershell-access it is closed ? TK> TK> Because Nano Server is optimized as a lightweight operating system for running "cloud-native" applications based on containers and micro-services or as an agile and cost-effective datacenter host with a dramatically smaller footprint, there are important differences in Nano Server versus Server Core or Server with Desktop Experience installations: Also what such these micro-servajses? Than them ? The Control bar-> Administration-> Microservices? Or the Control bar-> Administration-> Containers? TK> If service is necessary - use Server Core. You are assured?

5

Re: Who the thread saws ServiceBase for Nano Server 2016

Hello, VladCore, you wrote: TK>> And what for? docker start / docker stop - anything difficult VC> And how in console application to make that that vital in stop? As usual - the method stop anything basic does not differ from start. Simply cause it When to cause - system gives for this purpose the events. VC> and where to write docker start/stop if powershell-access is closed ? I.e. powershell access closed, and services on a network still  it is possible? NanoServer you as  gathered? Because Nano Server does not have interactive log on capabilities, all management will be completed from a remote system using PowerShell. TK>> TK>> Because Nano Server is optimized as a lightweight operating system for running "cloud-native" applications based on containers and micro-services or as an agile and cost-effective datacenter host with a dramatically smaller footprint, there are important differences in Nano Server versus Server Core or Server with Desktop Experience installations: VC> Also what such these micro-servajses? Than them ? The Control bar-> Administration-> Microservices? Or the Control bar-> Administration-> Containers? And what you there want to administer? start/stop? Somehow it is completely not dense... TK>> If service is necessary - use Server Core. VC> you are assured? If it is necessary high-grade.net - server core it is your choice. https://windowsserver.uservoice.com/for … rk-on-nano