intercom-dotnet icon indicating copy to clipboard operation
intercom-dotnet copied to clipboard

Published 20 hours ago • verified publisher icon intercom

Latest version 2.1.1 does not target .NET Standard

Open martinmasse opened this issue 5 years ago • 10 comments

Hi,

It seems that we have lost the .NET Standard target in the latest release making it not compatible with .NET Core

martinmasse avatar Aug 19 '19 11:08 martinmasse

yeah, this seems like a pretty bad regression.

mscrivo avatar Sep 05 '19 14:09 mscrivo

Any ETA for a fixed package?

hognevevle avatar Dec 19 '19 22:12 hognevevle

This is keeping me from updating as well.

ThomasArdal avatar Jan 21 '20 06:01 ThomasArdal

Same here, would be great to get a "fix" for this 👍

gonace avatar Feb 07 '20 13:02 gonace

Is this still an actively supported SDK?

johnnyoshika avatar Apr 01 '20 21:04 johnnyoshika

Hello we are also stuck in our migration for .net core. NETStandard is vital to move towards .net core.

AndiRudi avatar Apr 02 '20 15:04 AndiRudi

Someone made https://github.com/intercom/intercom-dotnet/pull/157 which should solve the issue

AndiRudi avatar Apr 02 '20 15:04 AndiRudi

Maybe https://github.com/intercom/intercom-dotnet/pull/166 could help with this? Fixes that CircleCI build error too....

mngobbi avatar Jan 23 '21 04:01 mngobbi

It looks like Intercom have completely dropped support for this library which is a real shame considering the cost of their product, and considering that the community have attempted to provide PRs to fix these issues but which are seemingly ignored. This project should be marked as deprecated.

A few options - fork it, and issue nugets from the patched PRs, or alternatively you can use 2.1.0 (https://github.com/intercom/intercom-dotnet/releases/tag/2.1.0) which does support netcore, but you will still be on the old v1.2 API (and who knows how long that will be supported for!) - https://github.com/intercom/intercom-dotnet/issues/163

Internally we have just setup a refit (https://github.com/reactiveui/refit) interface around some of their endpoints as needed, and define our own data models. Saves being bound to an unsupported and out of date library.

mgoodfellow avatar Jan 25 '21 09:01 mgoodfellow

For future visitors and in addition to @mgoodfellow's comments, I'm using the 2.1.0 package with version 1.4 of Intercom's API. I haven't experienced anything that isn't working yet, but there could be something unsupported with that combination. Any newer versions of the API won't work with 2.1.0.

I can only agree with everything here. It's a shame that Intercom offers this package and then don't maintain it. Deprecate it or fix it.

ThomasArdal avatar Jan 25 '21 09:01 ThomasArdal