While my main job is MeshCentral, on the side I am still taking care of updating the Developer Tools for UPnP Technologies. One of the areas that gets the most updates is Device Builder, the tool that generates custom UPnP stacks. It just happens that Device Builder's C stack uses the same code base as my peer-to-peer mesh project.
I just updated the Developer Tools for UPnP Technologies. It's now at version v0.0.38, as always it's open source at http://opentools.homeip.net. For people that already have a previous version of the tools installed, the update should be coming using the auto-update system.
I am generally a C# developer, but these days, I own, maintain and write a lot of C code. My two main projects with C are the Mesh Agent and the UPnP Microstack, both share a lot of code and in the case of the UPnP stack, it's quite widely used.
I just released a new bug fixed version of the Developer Tools for UPnP Technologies. Someone pointed out that on IPv6 you have to use a different multicast address for link local and normal IPv6 interfaces. In other words, if you have an IPv6 address that starts with FE80, you have to use a different SSDP multicast address.
After many requests, I again attempted to get the Developer Tools for UPnP Technologies working on Linux. Some have noted that it already almost worked, the user interface would show up but no device would get discovered.
People who have downloaded the Developer Tools for UPnP Technologies in the last month have noticed many new updates are being released. The self-updating system build into the tools allows anyone to keep up with the changes as they come. In recent days I have been getting help from the community and fixed may more bugs.
I just updated the Developer Tools for UPnP Technologies in an attempt to bring the tools up to date. First, the source code was updated to Visual Studio 2010. Second, when running Device Spy, the UI was sluggish and the tools would not be consistent in detecting all devices on the network.