Skip to content
This repository has been archived by the owner on Jan 16, 2022. It is now read-only.

Get rid of TDV-Specific dxInput and move it to BPCSharedComponent.dll, upgrade NuGet packages #70

Closed
munawarb opened this issue Nov 17, 2018 · 0 comments
Assignees

Comments

@munawarb
Copy link
Owner

TDV implements a class called dxInput. As part of work in Treasure Hunt and wanting to use DirectInput there, I moved the dxInput class into BPCSharedComponent.dll and the new DLL is packaged with Treasure Hunt. The next step is to have the TDV project point to BPCSharedComponent.Input.DXInput instead of its dxInput.cs class.

While we're at it, I need to see if we can get away with using the same versions of all the SharpDX libraries, instead of weak-naming different assemblies because there are two NuGet packages for SharpDX in TDV, due to a bug in SharpDX that could very well be fixed now, according to the SharpDX GitHub. So let's point TDV to BPCSharedComponent and upgrade the NuGet packages if we can.

@munawarb munawarb self-assigned this Nov 17, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant