WIP: Restore WCF ServiceModel (maybe)

[lukebakken]

Hi @bording -

There have been a couple users (like this one) who continue to use the .NET library with WCF. I took a half-hour to see if I could restore the files deleted in commit ee92035 and, with some small hacks and TODOs left, the old files compile fine against version 6.0.0.

I don't know why RabbitMQ.ServiceModel was deleted (I assume it meant less to maintain). I have the following questions -

• Why was the project removed? Lack of interest in it or WCF in general? Bad fit for WCF?
• Should the project be restored and kept up-to-date? There have been a handful of inquires about it since it was removed.
• If restored, should RabbitMQ.ServiceModel be its own project with its own GitHub repo?
• I'm assuming some sort of tests should be added

Thanks!

[bording]

While I did remove that project all the way back in #248, it was at the direction of @michaelklishin in #243.

I've never really looked at what the RabbitMQ.ServiceModel code enabled, so I don't have really have any insights into whether it's worth bothering to bring back. My gut reaction is no.

FYI there are some packages to enable .NET Core WCF support, but it's only the client-side aspect of it, not the parts that enable you to write a WCF service.

As far as one repo or two, I see that you had to add access to the internals of the main project? If so, then I'd keep them in the same repo and version / release them together. I would consider creating a separate test project though, instead of sharing one project.

However, if you had to ask me, I'd say just keep this in the past. WCF is basically done/dead at this point and will never be something you'll really be able to use .NET Core, which is the future of all .NET development. Microsoft has already said that .NET Framework is done, and there won't be any new versions coming.

[lukebakken]

@bording thanks for the input!

[michaelklishin]

It did not see enough use and we have enough things to maintain already.