After over one month there’s finally the 1.1 release which is still a beta just to make that clear. VisualBug 1.1 features the newly introduced Tokenization which allows you to track multiple instances of the same type inside of VisualBug. Moreover it allows you to easily implement for example the Singleton-pattern. Sadly we had to cut the injection-feature because there where a bug that causes any assembly to break when using satellite-injection. At this point: Yes, 1.1 theoretically already supports multiple assemblies for injection.
For this reason we have revamped BugSpy’s usage. Now manual usage of BugSpy’s tracking methods is incredibly easy. Method names have been kept short, you only need to specify the most important parameters and most stuff will be done by BugSpy if you provide the necessary information. This means that if you specify the Monitor– and Tokenized-attributes, BugSpy will use the provided information and makes it even easier for you. See the tutorials for how to use BugSpy manually. It couldn’t be easier.
And thereby we have the next headword. We created 3 tutorials which show all possible features and how to use them. Moreover we created a documentation with library reference which is contained in the download and update packages from now on.
Last but not least: VisualBug now does support both WPF and WinForm applications.
In 1.2 we will bring back Injection with support for all current features. Moreover there will finally be build-automation support in form of commandline arguments. This will allow you to easily set up a process chain that will inject BugSpy into your application during post-build. We’ll announce other major features for 1.2 once it’s time to do so.