Good questions. The short answer is that I've reorganized the code to take advantage of new platforms. For old platforms, use the old builds.
I used to release Update Controls as an MSI because it targeted Windows Forms. The MSI installed the controls into the toolbox, and created a Visual Studio command for creating independent properties.
It still works with Windows Forms, but without an MSI you have to manage the toolbox yourself.
Then I started focusing on XAML. And we added features like Independent<T> (that was yours, right?) and ViewModelBase that took away the need for a command. So the MSI became less important. Add to that the rise of NuGet as a distribution mechanism, and
I stopped building MSIs altogether.
It was a good thing, too, since Visual Studio 2012 stopped supporting Setup and Deployment projects.
Now Portable Class Libraries have come along. With them, I can target WPF, Silverlight, Windows 8, Windows Phone, Android, and iOS (using Xamarin). And, I can hit all those platforms with one project, rather than linked source files. So I reorganized the solution
to clean it up and put it on the path to continue forward.
The down side is that Update Controls Portable Class Library only targets .NET 4.5 and above. So if you want to target 3.5 or 4, you'll need to grab an earlier version.
Download the MSI. I won't be building any new MSIs, so this is the pre-PCL version.
Install an earlier version with NuGet:
Install-Package updatecontrols -Version 184.108.40.206
If you want to build the code in VS2010, just pull down an earlier changeset. I even moved the history over to GitHub so you can easily fork it and create a branch at any point you like.
Hope this helps.