Support .NET Core

[WilliamBZA]

ServicePulse can be deployed separately to ServiceControl and thus has a different set of blockers preventing the adoption of .NET Core.

Since Nancy is also close to supporting Core, we are well placed to support it with relatively low friction.

Since Pulse will be the only product of ours that supports .NET Core, the benefit provided is low so this should be low priority too.

• Investigate blockers

[johnsimons]

@WilliamBZA ServicePulse can be easily deployed on any non Windows system, all you need is a webserver to host for the files.
Not sure I see the value here.

[WojcikMike]

I agree with @johnsimons as ServicePulse is a SPA application without any backend we can host it on any webserver that supports html+js

[WilliamBZA]

Of course, that's exactly why I say this will be low friction! But there's more to it than just hosting the files on a webserver. The design of including transformation of config files as part of the setup project makes this hard for users. There's manual work involved and there will be bugs with "why is my version incorrect".

My suggestion is to spend some time making the deployment process cross-platform too, so that we have a complete solution - not just a workaround. Like I said, low priority, but brushing it off as "it's just html and js" is not good enough unfortunately.

[levimatheri]

Any progress on this? @kbaley @WilliamBZA

[HEskandari]

@levimatheri ServicePulse can run on Linux as a SPA application. In fact, we have docker images for it for both linux and windows on Docker Hub. Would that work for you?

[levimatheri]

Nice 👍🏽 yes that works. Thank you @HEskandari

[WojcikMike]

Should we then close this issue?

[WilliamBZA]

Yes, closing.