The evaluation version is designed to stop working the first monday of every month. What was fixed in 2.0.0.6 is that the error message shoud be friendly, instead of receiving the weird error you are seeing. And I also fixed the fact that the crash should not be showing through OleView, only when using the library to do stuff.
If you still see this error, that means that the system is still trying to load the old binary. You should ALWAYS unregister the old binaries before registering the new ones, otherwise you will run into the commonly known as "registry hell".
A quick workaround for this is to change your system date and time to a day different than today, so that the evaluation protection does not trigger. You will then be able to use OleView and see what libraries and versions you have effectively registered. Sorry for this annoying behaviour, a few users complained today already and this has been fixed in 2.0.0.6.
The evaluation version is designed to stop working the first monday of every month. What was fixed in 2.0.0.6 is that the error message shoud be friendly, instead of receiving the weird error you are seeing. And I also fixed the fact that the crash should not be showing through OleView, only when using the library to do stuff.
If you still see this error, that means that the system is still trying to load the old binary. You should ALWAYS unregister the old binaries before registering the new ones, otherwise you will run into the commonly known as "registry hell".
A quick workaround for this is to change your system date and time to a day different than today, so that the evaluation protection does not trigger. You will then be able to use OleView and see what libraries and versions you have effectively registered. Sorry for this annoying behaviour, a few users complained today already and this has been fixed in 2.0.0.6.