A
Austin Myers
As some of you know, I was having a real issue with my COM add-ins not
loading properly. PowerPoint would try to load them, have an issue and then
change load behavior to two (don't load) in the registry.
The real headache in all of that was that there was no way to determine what
failed or why and that made troubleshooting a real bear.
Sooo, I've managed to work out a bit of code that will track any errors
during load (VSTO and .NET only) and write them to a *.log file.
If anyone wants to peek at it just let me know.
FYI: This will catch errors from any VSTO / .NET add-in so it might be
handy for users or dev types having issues.
Austin
loading properly. PowerPoint would try to load them, have an issue and then
change load behavior to two (don't load) in the registry.
The real headache in all of that was that there was no way to determine what
failed or why and that made troubleshooting a real bear.
Sooo, I've managed to work out a bit of code that will track any errors
during load (VSTO and .NET only) and write them to a *.log file.
If anyone wants to peek at it just let me know.
FYI: This will catch errors from any VSTO / .NET add-in so it might be
handy for users or dev types having issues.
Austin