Handling similar file names

  • Thread starter Thread starter KM
  • Start date Start date
K

KM

If you want to go with only one component (sometimes makes sense), you may
also do:

1. Create a few repositories for the component and sort out all you files as
you wish
2. Have only one flat repository but if you have name collisions, rename one
of the files in the repository, then change the appropriate file resource's
Source Name property to
reflect the name change. This path may be laborious if you component has a
huge number of files.

KM
 
Victor,

Sorry, I wasn't clear in my previous post and did not read your post
carefully.
Basically, the first option I suggested is the same as you mentioned -
creating multiple components and multiple repositories. I was just thinking
of one SLD file that gets all the component and repositories plus a macro
component to union all the components with different repositories assigned.
This way you can easy handle component (read SLD) in your build.

Using/changing Source Name properties is painful (I know that cause I had to
integrate a couple of applications with a huge number of files). However, I
don't see any good alternatives unless MS changes flat repository approach
in XPe.

And again, as you mentioned as a second option, you can "zip" all you files
in your repository (your SLD will have one or few files listed) and then
create an FBA command to "unzip" the archive on the target. Zip/Unzip could
be implemented with different tools, e.g. self-extracting WinZip, WinRar,
etc. I don't like this approach, though. It is not elegant and not flexibly
solution.

KM
 
Hi Everyone,

I'm trying to sort out what to do as my component includes similar file
names (but
will be stored in the run-time image into different sub paths). To my
understanding,
this requirement cannot be stored in the XPE repository. And the solutions
may be:
(1) create multiple components, (2) or employ a setup.exe that will
"runonce" and
handle this predicament. I'm geared to doing the latter. Is this the correct
way to
go? Any other suggestions?

Best Regards - Vic
 
Hi,

KM said:
If you want to go with only one component (sometimes makes sense), you may
also do:

1. Create a few repositories for the component and sort out all you files as
you wish
Click to expand...

If I will create numerous repositories for a single component, how can I set
my
single component's Files node definitions to make use of these numerous
repositories/sources?
I'm not really sure if I follow this correctly. Perhaps you can ellaborate
further ;o), like:

Create YYY, then set XXX via Component node -> Files node -> Tweak Item X
2. Have only one flat repository but if you have name collisions, rename one
of the files in the repository, then change the appropriate file resource's
Source Name property to
reflect the name change. This path may be laborious if you component has a
huge number of files.
Click to expand...

This will defintely be very painful as my component app reads MANY like file
names stored in
different paths (reading is only directed by means of Junctions: Symbolic
links for UNIX/Linux).
 
Hi,

KM said:
Victor,

Sorry, I wasn't clear in my previous post and did not read your post
carefully.
Basically, the first option I suggested is the same as you mentioned -
creating multiple components and multiple repositories. I was just thinking
of one SLD file that gets all the component and repositories plus a macro
component to union all the components with different repositories assigned.
This way you can easy handle component (read SLD) in your build.

Using/changing Source Name properties is painful (I know that cause I had to
integrate a couple of applications with a huge number of files). However, I
don't see any good alternatives unless MS changes flat repository approach
in XPe.

And again, as you mentioned as a second option, you can "zip" all you files
in your repository (your SLD will have one or few files listed) and then
create an FBA command to "unzip" the archive on the target. Zip/Unzip could
be implemented with different tools, e.g. self-extracting WinZip, WinRar,
etc. I don't like this approach, though. It is not elegant and not flexibly
solution.
Click to expand...

Well, not really. But it will do the job :o). A single cab file that will be
wextract.exe'ed
during FBA should do it . Thanks anyway.

Regards - Vic
 
Back
Top