Custom component for app - need one or not?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I’m building an XPe image for devices that will boot XPe from a hard drive.
An in-house application will be installed directly onto a target device (via
CD-ROM drive) for testing and, eventually, production purposes. This is the
only app that will be installed onto the target devices.

I’ve already built a component using the devices.pmq created with TAP on one
of the target devices. Should I also create a custom component for the app
that will include all the files and modules that the app will need? Is this
the recommended approach for my situation? (I don’t know if the client wants
a custom shell or not… does that make a difference?)

The reason I ask is that the application is at this point only about 75%
done – and I need to let the client know whether or not a testable OS image
is feasible before they finish coding the app.
 
Galisteo8 said:
I’m building an XPe image for devices that will boot XPe from a hard drive.
An in-house application will be installed directly onto a target device (via
CD-ROM drive) for testing and, eventually, production purposes. This is the
only app that will be installed onto the target devices.

I’ve already built a component using the devices.pmq created with TAP on one
of the target devices. Should I also create a custom component for the app
that will include all the files and modules that the app will need? Is this
the recommended approach for my situation? (I don’t know if the client wants
a custom shell or not… does that make a difference?)

The reason I ask is that the application is at this point only about 75%
done – and I need to let the client know whether or not a testable OS image
is feasible before they finish coding the app.
Click to expand...

Whether you need to componentise it depends on how often you think
you'll end up installing it once it's done.
 
Hi Heidi,

I'm afraid that I don't understand your response. The client ships
computers (with the in-house app on it) to their customers; all of these PC's
will use the XPe image on them. They will install XPe on a target computer,
load their app, and deliver the computer to a customer. Then load XPe onto
another computer... etc.

What difference will this make in whether I componentalize or not?
 
Galisteo8 said:
Hi Heidi,

I'm afraid that I don't understand your response. The client ships
computers (with the in-house app on it) to their customers; all of these PC's
will use the XPe image on them. They will install XPe on a target computer,
load their app, and deliver the computer to a customer. Then load XPe onto
another computer... etc.

What difference will this make in whether I componentalize or not?
Click to expand...
If you componentise it, it's already in the image when it's built. You
can also provide them a sealed image to put on that you've already
installed the application on, though. Personally I tend to componentise
things because I produce a lot of slight variants until we get to
something we're happy with, and installing the app every time would be a
waste of time. Also, componentising the app allows me to include the
configuration options so I don't have to set them every time - or risk
forgetting to.
 
Ah! So componentizing would inlcude all the app's required files PLUS THE
APP ITSELF right in the OS image? Is that correct?

If so.... what is the preferred way to complete the OS image if the client
wants to keep the app separate?
 
Galisteo8 said:
Ah! So componentizing would inlcude all the app's required files PLUS THE
APP ITSELF right in the OS image? Is that correct?

If so.... what is the preferred way to complete the OS image if the client
wants to keep the app separate?
Click to expand...
Make sure you've got everything in there to install the app (including
the installer service stuff) and check it works, then supply them a
version you've *not* installed the app on. If they want to install it
themselves that's their problem.
 
Hi, Heidi,

It makes sense to ensure the OS image has all the components that include
the files which the app needs. However... and I don't mean to be dense,
but... what do you mean by "the installer service stuff"?
Thanks for help!
 
She's referring to the "Windows Installer Service" and assorted Class
Installers. That's what makes various installers work (.msi).
 
Back
Top