search

usmanatron / amBXPeripheralController

Server application (with a number of assisting clients) to control amBX gaming peripherals
Other
1 stars 4 forks source link

Rename aPC.Common.Communication #4

Closed usmanatron closed 10 years ago

usmanatron commented 10 years ago

The aforementioned project does more than communication these days. It also defines Client specific things like UsageExceptions along with Ninject helper stuff.

Ideally, this should be appropriately renamed to clean this up. An alternative is to merge it into aPC.Common, however I like the idea of having a very lightweight library that can be used in third party applications...

usmanatron commented 10 years ago

Another idea is to move UsageException and the Ninject stuff into aPC.Common and not rename it. Then the Communication library is just communication. The disadvantage is a new dependency on aPC.Common for aPC.Client, but that isn't actually /that/ bad?

usmanatron commented 10 years ago

Now sorted. Kept the name as-is and moved all the non-communication stuff into a new assembly called aPC.common.Client (as it was all things specific to my clients i.e. not needed in third party integrations)