"Peter Zahn"
discussions.microsoft.com> wrote in message
news:2D54AB85-F1FB-4E3B-BC8B-E5E8E9060A44@microsoft.com...> Hello Dean,
>
> thanks for your reply!
>
>> From what you said I suspect that the link between the component and its
>> repository was either not made, or made improperly.
>
> I double checked the path to the assigned repository for one component in
> "Component Database Manager" (Repository tab -> Change location), which
> seemed to be correct.
>
>> an associated repository. Each component must point to the appropriate
>> repository; if it does not, then you will get "File not found" errors in
>> Target Designer when it tries to pull the files out of the repository.
>
> Now, what is unclear to me, how does a component reference a repository?
> As
> i can see in "Component Database Manager", each repository consists of a
> name
> and a version. Does TD simply look for a repository with the specific name
> and version, or is there a kind of "database connection" between component
> and repository? If yes, could it be that this "link" gets broken?
>
Start CD and open your .sld. On the left pane under "Windows XP Embedded
Client (x86)" you'll see a Components folder - in it you should have at
least 1 component. Click a component, and on the right pane in the bottom
block you'll see a field named "Repository". If the field contents does not
have the name of the repository where the files enumerated in the Files list
(revealed by expanding your component) are kept then TD will throw "File not
found" errors. This in the magic link that tells TD in what repository to
look for the files you've added to your component.
>> From what I can see, "releasing" a component is merely a way of tracking
>> a
>> component's status - it has nothing to do with files or their
>> repositories.
>
> I wrote this, because it was the reason for the problem. As i understand,
> after component changes (update or release), it is necessary to re-import
> it
> the normal way. As i did this, the import failed becaus of write
> permission
> errors, which i could solve by renaming the specific repository folder, so
> that the import created an identical, new folder. Did i make a mistake in
> this procedure?
>
Probably because I'm lazy I've never bothered to release my custom
components. TD throws warnings when building unreleased components but
otherwise builds the image.
> And general about the update of components: As i see, there are two
> possible
> ways: Changes in the component, but repository files are identical, or
> changes in the component and changes in the repository files.
> What is the right procedure in both cases. First, only re-import the
> component without importing files? And in the second case, i should change
> the repository version and re-import with files? Would this create a
> second,
> parallel repository for this component? Or how in general i should handle
> the
> update process?
>
> I temporarily fixed the problem by adding all "Not Found"-Files to a
> separate directory, which i added as "Additional Files Directory", which
> worked, but of course this is a rather dirty solution as i think.
>
> Peter Zahn
