Hi,
Yes, you can use that license also for AntView 1.1
Note however that AntView 1.x is a different control and it uses its own set of GUID's and its own namespace.
See: Important changes in AntView 2.0
We're not really recommending AntView 1.1 at this stage, but if it was for a specific use case then trying AntView 1.x could be a workaround on trying to get the control to work on your Windows 7 machine.
If OTOH it is for development only and then deploy on modern supported Windows operating systems then we recommend on staying with AntView 2.0 as that is our current development branch that gets new features and you'll also stay within a supported environment.
It is best to update your development platform. VB6 does work fine on Windows 11.
We don't test against Windows 7 anymore as Microsoft no longer supports WebView2 on that platform, so I'm not sure what to try beyond AntView 1.1 when it comes to using Windows 7.
edit: To clarify, we still support AntView 1.1, but not on Windows 7.
--
Wil
Yes, you can use that license also for AntView 1.1
Note however that AntView 1.x is a different control and it uses its own set of GUID's and its own namespace.
See: Important changes in AntView 2.0
We're not really recommending AntView 1.1 at this stage, but if it was for a specific use case then trying AntView 1.x could be a workaround on trying to get the control to work on your Windows 7 machine.
If OTOH it is for development only and then deploy on modern supported Windows operating systems then we recommend on staying with AntView 2.0 as that is our current development branch that gets new features and you'll also stay within a supported environment.
It is best to update your development platform. VB6 does work fine on Windows 11.
We don't test against Windows 7 anymore as Microsoft no longer supports WebView2 on that platform, so I'm not sure what to try beyond AntView 1.1 when it comes to using Windows 7.
edit: To clarify, we still support AntView 1.1, but not on Windows 7.
--
Wil