Hello Friends,

How to support Visual Basic tool programming in WINPE 2.0?

What exactly is the question? You can use Visual Basic 6 programs in WinPE because they do no require the .NET framework.

I had to add and register (with regsvr32) a collection of common VB6 DLLs in my PE image to get some of our VB applications to run. You can download a set from M$.

I had to add and register (with regsvr32) a collection of common VB6 DLLs in my PE image to get some of our VB applications to run. You can download a set from M$.

You had to do this for WinPE v2.x, even after building it with Scripting support?

What DLL's did you have to register?

You had to do this for WinPE v2.x, even after building it with Scripting support?

What DLL's did you have to register?

Probably whatever libraries are referenced in the project?

In the past, I had used comdl32 and comtrl, but I ended up dropping those and just using direct API calls to avoid the extra baggage of missing libraries. Whats the point of slimming down the CD and then stuff a bunch of DLLs and OCXs back in?

Yes, they were DLLs needed by the specific applications. Things like COMDLG32.OCX and MSVBVM60.DLL. As far as bloating the CD with files, I have yet to really notice any difference in load time as it relates to the size of the WIM.

Dear ALL ,

Thank you for your support