bacsharp

As much as the project seems like a chassis of an old muscle car that needs lots of time & attention, once fixed-up, the code is full of potential, and as far as BACnet is concerned, is on solid ground overall. (I tip my hat in recognition. ;D)

Some of the most horrible .NET code I've seen in a long time. Socket programming through PInvokes. Timeouts through System.Windows.Forms.Timer + spin loop. App Config through Ini file. Cyclic reference calls. Code is a mess. Lots of unused code. Still, it's fairly simple, it could be worse I guess.