WinXP SP3, Framework 1.1 through 4 installed (and VS2010 Pro). Saw the post about %windir% and %systemroot%, and made sure both pointed to windows directory (not system or system32). Filterpro crashes at startup, no further diagnostic messages?
Any thoughts?
Hmmm...
Nothing comes to mind right away. Perhaps your downloaded file was somehow corrupted? Best suggestion is to uninstall, re-download, and install again. Let us know if that doesn't work.
Wish I could be more definite...
Well, I removed and installed a fresh copy, without joy. I let VS2010 start as a debugger, and it reported the following error:
When I've encountered this in the past it was usually because I changed a serializable class that I was using to create an INI file. So, when I tried to directcast the INI file with a new class definition, of course, the cast failed.
However, I don't see any INI files, just some XML and config files. The config files I assume are resource files, so they now seem to be outstanding candidates for sources of the problem. However, deleting them just results in a message about the autoupdater not being able to run?
I'd like to have one of our developers contact you and work through this. We tried your my.TI registered e-mail address but it bounced.
Can you please send me your contact information so we can email or call you? Write to me at downs underscore rick at ti.com (I wrote it out to prevent being spammed).
Thanks -
Rick:
My contact information is below, but I have resolved the issue.
I removed and reinstalled Framework 1.1 ~ 4.0. It said is was properly installed, but apparently not. When reinstalling I found that updates had to be installed in a certain order with reboots in between. I ended up rebooting ~ 8 times (thanks MS, I had plans for that afternoon), perhaps originally I put off one of the reboots, and then forgot? Or did the installs in the wrong order?
In any event, removal and reinstallation fixed the problem. On the positive side I also write code in VS2010, so this would probably have bitten me elsewhere. Thanks for you support, and I would only suggest that a bit more error logging might reduce all of our aggravation (although this was obviously my fault).
George Barbehenn
Bijoux Design
Embedded hardware, firmware and Applications Software
ghbarbehenn@earthlink.net
480-246-4314