J
Jerry Spence1
I noticed when adding Toolbox Items in the IDE that, under the COM tab I
have some Microsoft. Forms 2.0 Controls. I'm not sure where they came from
(VB2005, .Net 3.0??), but they have some really nice features. I used the
Image control and using the various properties made a nice button which gave
the impression that it stays down when pressed, and pops up when pressed
again. I haven't been able to achieve this with other controls.
Anyway, I deployed my application to another PC and took with it the
FM20.DLL file. As soon as I start up the application, it crashes with one of
those "Do you want to send this to Microsoft" boxes.
I find very little reference to these controls on the web which puzzles me.
It comes out as AxImage when inserted on a form.
Has anyone got an answer to this? Do I need any other file (Deployment
dependancy says not), does anything need to be installed on the target PC?
It has the same .Net framework (3.0). One clue is that if I deploy it on
another PC with VB2005 installed, it works OK which tends to suggest a
registration issue.
-Jerry
have some Microsoft. Forms 2.0 Controls. I'm not sure where they came from
(VB2005, .Net 3.0??), but they have some really nice features. I used the
Image control and using the various properties made a nice button which gave
the impression that it stays down when pressed, and pops up when pressed
again. I haven't been able to achieve this with other controls.
Anyway, I deployed my application to another PC and took with it the
FM20.DLL file. As soon as I start up the application, it crashes with one of
those "Do you want to send this to Microsoft" boxes.
I find very little reference to these controls on the web which puzzles me.
It comes out as AxImage when inserted on a form.
Has anyone got an answer to this? Do I need any other file (Deployment
dependancy says not), does anything need to be installed on the target PC?
It has the same .Net framework (3.0). One clue is that if I deploy it on
another PC with VB2005 installed, it works OK which tends to suggest a
registration issue.
-Jerry