[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 913
  • Last Modified:

Running VB Apps in WINPE

Hello,

I am currently using WinPE to help build machines. I would like to use some VB programs to automate certain tasks; however, it seems WINPE does not support this. I know it can be done using BARTPE but the company would rather stay as close to the offical supported microsoft product as possible....

Any Ideas?

Thanks,

Jamie.
0
purejamie
Asked:
purejamie
  • 2
1 Solution
 
RevelationCSCommented:
most versions of windows can be set up with a unattended install script that can be customized to what you want to have unattended on the install process. I would do a search on Microsoft's web site to see if you can find how to do this based on the version of Windows you are using in your environment...
0
 
RevelationCSCommented:
0
 
purejamieAuthor Commented:
Thanks for the input, however, we use unattend to build the machines - however, we use a VB front end to choose build type/server/setup,restore options/hidden backups etc. that I need to get working in WINPE - when I run the program nothing appears on the screen.
0
 
Cyber-DudeCommented:
Not inherently, but yes, so what you need to do is you actually need to add the files that are specific to Visual Basic. Basically, if you package up your application and you figure out all of the executables and binaries that are required for that, and you make sure those are in WinPE and registered, as long as those don't have any dependencies (such as trying to call DirectX or things like that), you should be okay. As long as you keep your application very simple, very rudimentary, remember you're in a preinstallation environment. You're not in, say, an embedded environment, like XP Embedded would provide. You want to keep it very simple, but yes, you should definitely be able to build VB apps. Visual C applications should work inherently. The .NET Framework is not available in there, so you'll probably want to keep your applications, based on VB 6 or VC 6 rather than writing .NET Framework applications.

Cyber
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now