Monogame: SharpDX Retired

[tdeeb]

The official SharpDX repository states that the project is no longer active or maintained as of March 29, 2019. Since WindowsDX (and Xbox One?) projects use it to render via the DirectX API, any bugs tracing down to SharpDX won't be addressed by the maintainers. What should we do about this going forwards?
@tomspilman @cra0zy @Jjagg

[amerkoleci]

https://github.com/sharpdx/SharpDX/issues/1138

[tomspilman]

any bugs tracing down to SharpDX won't be addressed by the maintainers.

The good news is very very few of those exist.

And if we run into issues we can choose to go fix it ourselves.

So at this point it isn't a huge concern.

What will be interesting is what happens post DX12.

[nathan-alden-sr]

I'm concerned about this, as well. I just started work on a game engine and I'm already knee-deep in SharpDX. This is making me question whether I should throw away the SharpDX code and port the whole client to Visual C++.

Someone--or some org--needs to take ownership of the project, or at least fork it and become the "new" owner. SharpDX is an _excellent_ library and it would be a shame if the project just died.

Does Microsoft have a process where people can request they take ownership of projects such as this?

[tomspilman]

Someone--or some org--needs to take ownership of the project,

Agreed... but I highly doubt Microsoft will do it.

It will be up to the community that already uses the project to maintain it.

I expect with the MG team needs a fix one of us will fix it and submit the PR and it will get merged.

[amerkoleci]

As I said on SharpDX issue and else where, I'm working on new DirectX bindings (https://github.com/amerkoleci/SharpWindows)

[tomspilman]

I'm working on new DirectX bindings

That is great. If we ever decided SharpDX isn't working for us we would consider it.

[slmyyy]

This is really unfortunate. I've invested heavily in SharpDX. Wouldn't it make more sense to fork SharpdDX and redirect efforts there?

[tomspilman]

Going to close this issue for now as it isn't really serving any purpose.

There is nothing to worry about here.

SharpDX works just fine today and is 100% open source so we can create fixes when we need to.