At image build time, there is a concept of 'repository fallback logic',
meaning that when a component's files are being bin placed to the new
runtime being created, if the file is not found the platform script will
search the system repositories in a particular order until the latest
version of a filename is found. If the file is not found after that, you
receive the build error.
This is why its acceptable to import a component who's files aren't in the
associated repository folder during import.
However, i do think it would be cool to write a script that compares the
file resources of a component against the associated repository to provide
you reassurance that you're golden before importing the component.
-andy
--
Embedded team blog:
http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Larry Waibel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> But it seems to me that your steps 5 and 6 should find that CDBM is
> importing a component
> that specifies a file it needs from a particular repository and if that
> file isn't there
> it should notify me at that point. I am creating a number of
> components/files/repositories that I have to formally release through our
> SCM group. If
> some of the files are missing and I don't find out until the formal
> release of the TD file
> then I have to do another release of each that I could have found out
> about much earlier.
>
> In article <#(E-Mail Removed)>, Slobodan Brcin (eMVP)
> wrote:
>> From: "Slobodan Brcin \(eMVP\)" <(E-Mail Removed)>
>> Subject: Re: Detecting missing repository files
>> Date: Thu, 21 Jul 2005 11:43:19 +0200
>> Newsgroups: microsoft.public.windowsxp.embedded
>>
>> Larry,
>>
>> There are no files that should go to repository. Import process work is
>> following way.
>>
>> 1. You can created repository node in your component project.
>> 2. You have created one or many components that use this or/and other
>> repositories and
> some files fom them (not necesarily all).
>> 3. You place all files in repository flat folder that you have specified.
>> 4. You import you components project.
>> 5. CDBM will delete all files if there were from old unique repository
>> folder in DB.
>> 6. CDBM will copy all files from your rep folder to DB folder.
>> 7. TD buring build phase will try to find filed in repository and if they
>> are not there
> it will complain.
>>
>> Based on this you can see that file fist that you made is for TD not for
>> CDBM import
> puroses.
>>
>> Regards,
>> Slobodan
>>
>> "Larry Waibel" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> > I've noticed that I can import a component without any errors even if
>> > the
>> > file(s) that need to go to the repository aren't found. Then I don't
>> > find
>> > out about it until I go to do a build. Is there some way to turn on
>> > better
>> > detection at component import time? Thanks!
>> >
>>
>
>
Similar Threads
