Inctrl5 file

  • Thread starter Thread starter Mir
  • Start date Start date
M

Mir

If I install a program with the Inctrl5, it generates a txt file, all this
information is what I should add to make the embedded component?
How can I had it?
Thank u very much
 
InCtrl5 tracks changes to the system that are a result of running an
installation program to intall software on a system; it's an information
gathering tool. In general, it detects if the installation adds or modifies
registry entries or files. You can use the information it provides to create
a component for XPe. I don't believe that a tool exists that will take the
results from InCtrl5 and create a component from them but that might be a
good product to have. :-)

-Beau Cseri
 
My problem is that I don't know wich are the files to add.
I've been reading about the process... and I think is not so difficult.
But my problem is to know wich are the files, dlls... that I nedd to add.
Also my application nedds some folders with images, that's another component
or it's the same as the application?
I'm sorry for disturbing.
 
InCtrl5 should list all of the files that were added to your system as a
result of executing an installation executable on your development system
through InCtrl5. In the file list, it might also include things like system
log files that were created or modified as a result of the installation,
which are obviously files that don't necessarily need to be included in your
component. Maybe not all of your drives are being checked. Click on the
"Drives" button under "What to track..." and make sure your hard drives are
in the list.

Another issue that you might be having is determining file dependencies.
InCtrl5 will list files added or modified on the system as a result of
running an installation executable, but it won't tell you the existing files
that the installed program depends on. After you execute your installation
executable through InCtrl5, a list of files added to the system will be
generated. Those files may be dependent on other binaries that are assumed
to already exist in the o.s. (given that the installation executable assumes
that it is installing on a Windows desktop o.s.). You can use the Dependency
Walker tool (depends.exe) on the binaries that were installed to discover
the dependencies of those binaries. Dependency Walker ships with Visual C++.
Another binary files analyzer, Scanbin, can be downloaded for free from
http://www.belamyjc.net/en/scanbin.html. Yet another way to check binary
dependencies is to run the binary through DUMPBIN with the /DEPENDENTS
option.

Whatever option you use, you can either include the dependent binaries into
your component, or you can use the filter tool in Target Designer to search
for components that already contain your dependent files and include those
components as dependency resources in Component Designer.

-Beau Cseri
 
Back
Top