ActiveX problems in .net
Few active X that used to work properly, means we can easily add them to our forms , throws error when we try them to place on our forms. Even few makes the visual studio crash. I was really shocked to see even the MS studio crashing. Is there any specific reason for the same, even some errors show that since they are working with unmanaged code for controlling ActiveX addition to forms , they are crashing.
One example of such a active X control is MSVSA Button Class.
Please provide some input on the way to get out of the problem. Even do we have some way by which we can check if the current activeX control is licensed or not.
[653 byte] By [
Chips_in] at [2007-12-25]
HI,
I suggest on contacting the activeX manufacturer on licensing issues. Also, your problem greatly lies on the activeX component that you are using, so its best to contact the support for the activeX control. And also try re-registering your activeX control using the regsvr32 command. Also look for new updates for the control for .Net support coz its more likely that the manufacturer would release a .Net capable version of the control.
cheers,
Paul June A. Domag
Hi,
I think I was unable to specify my problem at first time. My problem is that I wnat to check that from some code sniffet that whether the active x is authentiacted licenced or not.
SO is there some help on that.
Another thing is that even microsoft IDE crashes with the some active x , this means the code of the viual studio is even lacking some exception handling, I just wana get into that, is there some way to igonre this exception, since even i place a try catch over the main program, then even the application crashes as the Visual studio.
So is there some way to avoid that. I hope in none of these cases particular active X manufactureres can help.
Please provide ur inputs
Regards
Chips,....
Hi,
ActiveX Licensing solely depends on the author of the ActiveX control. Every 3rd party control has a different licensing technique. Coz if they were all the same then a single crack could probably crack all of the available ActiveX control in the market. So its on the Manufacturers side to give you their licensing technique and thus you can manually check if the installed activex control is licensed.
Hmmm... Your activeX is clearly invoking something that causes visual studio to crash. In both cases its the activex that caused the crash and I doubt microsoft would have a proper solution for that. But if you still want to report it as a Visual Studio bug you can file it here.
Microsoft Product Feedback Center
cheers,
Paul June A. Domag
