I do not know whether my post went through but I a mtrying again.
I am developing an active x control for an intranet web site that I am designing. While testing the control, I am obviously making changes. When I change and "remake" the control (using VB6), and call up the web page on the local machine, the new control comes up as it should. However, when I test the page on another system (not the IIS machine), the version of the control still comes into the page.
I assume that this is because the browser does not know to look for a new control. I am using Project Compatibility for the AX control project in VB which means, I believe that it uses the same class ID for newer versions of the control. I do not want to use versioning until the control is deployed.
How can I get the non-IIS machines to download the new control instead of using the one on their system???
Thanks in advance for any help,
Chris
I am developing an active x control for an intranet web site that I am designing. While testing the control, I am obviously making changes. When I change and "remake" the control (using VB6), and call up the web page on the local machine, the new control comes up as it should. However, when I test the page on another system (not the IIS machine), the version of the control still comes into the page.
I assume that this is because the browser does not know to look for a new control. I am using Project Compatibility for the AX control project in VB which means, I believe that it uses the same class ID for newer versions of the control. I do not want to use versioning until the control is deployed.
How can I get the non-IIS machines to download the new control instead of using the one on their system???
Thanks in advance for any help,
Chris