Hi Aaron:
I was initially thinking of the StopWatch class but others came to mind as
perhaps being useful.
It would be cool if the Forms and Form related classes could be used but I
doubt that will work because of the additional files the compiler creates
without too much coding in VbScript, perhaps no better than the xml based
windows used currently.
I read an article that said Microsoft was not including the wrappers for
those framework classes previously referenced in the registry as they are no
longer providing any wrappers as of the 4.5, perhaps 4.0 frameworks and
thereafter.
The framework has some mighty powerful tools and if I understand it
correctly a wrapper can be used to make them available to VbScript apps or
might be able to make them available.
I can build wrappers, from what I read, in my Visual Studio platform so this
is a possibility.
But, I wouldn't want to waste all that learning curve and work if there is
already a .net Framework Wrapper Library - don't want to ReInvent the wheel.
By the way, if I did build a wrapper how would it be used in a VbScript?
Something like:
Set StopWatch = CreateObject("RicksWrappers.StopWatch")
StopWatch.Start (not sure the syntax off top of head)
Where the Library would be what, a DLL?
But that is what drew my attention to the actual looking into wrappers.
Rick USA_______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
