Visual C# Beta 2 doesn't work with Visio 2003 Drawing Control
When I drag the Visio drawing control to a form, build and run the project, it throws an Class not registered COM exception at axDrawingControl1.EndInit() line.
Commenting this line out crashes the application. Please help
As for my disappearing control, I had a listview in the same form. Certain actions on the listview were causing the height of the Visio control to become 0 !
Found this while researching the problem. For me, I still don't see the control in the form but at least the program launches. [ of course not very useful since my form's main control is Visio ] Larry
If you put you a Visio Drawing Control on a form and press F5 to debug, you'll get a COM error on the EndInit line.
But that doesn't mean you can't use the control. What I did was first fire up the application without debugging. (Via executing the app in the bin directory or via the Start without debugging menu item)
Then when the control is loaded, attach the Visual Studio debugger to the process via "Attach To Process" menu item.
Offcourse this still means that while debugging you open a form with the Visio Drawing Control on it, you'll still get the error. You just can't be in debug mode while the control is loading.
Visual C# Beta 2 doesn't work with Visio 2003 Drawing Control
Visual C# Beta 2 doesn't work with Visio 2003 Drawing Control
ongsw
http://blogs.msdn.com/mailant/archive/2005/04/22/411042.aspx
As for my disappearing control, I had a listview in the same form. Certain actions on the listview were causing the height of the Visio control to become 0 !
markm2005
Larry
How to get around the Class Not Registered COM Exception of the Visio Drawing Control in Visual Studio 2005 Beta 2
The bad news is you can't!
If you put you a Visio Drawing Control on a form and press F5 to debug, you'll get a COM error on the EndInit line.
But that doesn't mean you can't use the control. What I did was first fire up the application without debugging. (Via executing the app in the bin directory or via the Start without debugging menu item)
Then when the control is loaded, attach the Visual Studio debugger to the process via "Attach To Process" menu item.
Offcourse this still means that while debugging you open a form with the Visio Drawing Control on it, you'll still get the error. You just can't be in debug mode while the control is loading.