Why OLEAutomation(False)? about windevlib HOT 2 CLOSED

The flag was a temporary workaround so RegisterTypeLib wouldn't register 3rd party interfaces (i.e. all of them in tbShellLib), as that call would fail, causing ActiveX control builds to fail.

It's no longer neccessary since tB now has a custom replacement for that function controlled by the [ ComImport ] attribute, but the default value is not registering so that didn't need to be added.

So [ OleAutomation(False) ] tags can be removed, but the vast majority of interfaces shouldn't be, as they're not part of the official definitions. Specifically, ITypeInfo is not marked oleautomation in the SDK headers, so the attribute is correct. oleautomation=true would only be found on things like the shell automation objects like IWebBrowser, but it shouldn't be necessary to use them.

from windevlib.

Thanks, I didn't realise there was an SDK standard you were working to and that of course makes sense. For some reason it's still showing up in my ActiveX Dll and I can make an ITypeLib variable in VBA no issue, so maybe I'm misunderstanding what it does anyway.

e.g.

[ AppObject ]
Public Class TypeLibEntryPoints
    Public Function GetExtendedModuleAccessor(ByVal moduleName As String, ByVal proj As VBProject, Optional ByRef outPrivateTI As tbShellLib.ITypeInfo) As Object
    	Return API.GetExtendedModuleAccessor(moduleName, proj, outPrivateTI)
    End Function
End Class

Compiles fine and from VBA I can interact with the ITypeInfo no problem

from windevlib.