Keeping a console application alive in Service Fabric

Question

Are there any established patterns for keeping console applications alive when hosted as guest executables in Service Fabric?

Adding a Thread.Sleep(Timeout.Infinite) after I've subscribed to Service Bus or similar feels like a bit of a hack to me. Other approaches I've seen use Console.ReadKey(), but, again, this feels like a hack.

`Thread.Sleep(Timeout.Infinite)` is what all service/actor hosts do to prevents process from terminating. Look at _Program.Main_ — Aleksey L., May 15 '17 at 07:19

score 2 · Accepted Answer · answered May 15 '17 at 09:32

Thread.Sleep(Timeout.Infinite) appears to be what's recommended by Microsoft according to their Azure Service Fabric samples in GitHub:

https://github.com/Azure-Samples/service-fabric-dotnet-getting-started/blob/master/src/GettingStartedApplication/ActorBackendService/Program.cs

score 1 · Answer 2 · answered May 12 '17 at 21:15

1

Console.ReadKey() is perfectly fine. You can Write a message before like

Console.WriteLine("Press any key to end...");
Console.ReadKey();

so the user knows how to end the application.

answered May 12 '17 at 21:15

johannespartin

501
3
15

Keeping a console application alive in Service Fabric

2 Answers2