We've finally found this bug, and the reason we could not reproduce it on our side. It seems the presence of a drive-letter in two of the settings in the config file was causing the problem. Weird I know, nevertheless it's fixed and will be out with 2.0.3. In the meantime, here's the quick-fix:
- Edit your CodeBreeze.exe.config file (located in the CodeBreeze application install folder).
- The two keys in the <appSettings> called "InstallFolder" and "PersonalFolder" probably have "C:" in front of the path.
- Eliminate the "C:" from both values. NOT "C:\", JUST "C:". Make sure the path still starts with "\".
This should get you going fine, and our sincere appologies for this hard-to-find issue, and thanks to Joseph Bagget for working with us on this.