Life cycle of a component

  • Thread starter Thread starter Doug G
  • Start date Start date
D

Doug G

OK, I've got some components that were created, debugged, and finally
released as V1.0 in my current XPE image. Now there are some upcoming
changes and I will be creating V2.0 (or V1.1?) of some of these components.
How does this work with regards to the component builder, database,
repositories, and target designer? I can see in the component builder that I
can use Edit -> Update to start updating the component, but what happens
when I'm done?

1) Do I have to use a different repository so that V2.0 files are kept
separate from the released V1.0 files?

2) In TD, will I have two versions of the component to choose from, or will
V2.0 just appear as an available "update" to the currently included
component?

As far as I am concerned, V2.0 should completely replace V1.0 in all cases,
so if there's a way to select that behavior, that's what I want to do. But I
have had some trouble in the past, especially with replacing files in
repositories, so that I am wondering what the correct way is to handle it
all.

Doug Gordon
 
1)
Usually all files that have changed should have changed original name but same destination name.
So users can use old component and new components depending on when they build project and if they upgraded component in TD.
If you have too much files changed then you can consider new repository. (I would not do that).

2)
When you select update you always update to most recent version, no choice in that :(
You can downgrade your component in project file itself.
As far as I am concerned, V2.0 should completely replace V1.0 in all cases,
so if there's a way to select that behavior, that's what I want to do. But I
have had some trouble in the past, especially with replacing files in
repositories, so that I am wondering what the correct way is to handle it
all.
Click to expand...

You can do that. Could you specify problems with replacing files in repositories that you had, I have not seen this behavior.
Or better to say there is a problem with user privileges on repository folder but this is more folder access administration problem
then XPe problem.

Regards,
Slobodan
 
Thanks for the info; I had not thought of using different file names in that
way.

I will let you know if I have repository problems. It probably does have to
do with privileges on the folder, but since I have all administrative
privileges on my PC (where the repositories are located) and since the XPE
tools are the ones who created the repository and all those folders, it
seems that they should have applied the necessary privileges to be able to
update the files.

Doug G

Slobodan Brcin (eMVP) said:
You can do that. Could you specify problems with replacing files in
Click to expand...
repositories that you had, I have not seen this behavior.
Or better to say there is a problem with user privileges on repository
Click to expand...
folder but this is more folder access administration problem
 
Doug G,
Thanks for the info; I had not thought of using different file names in that way.

I will let you know if I have repository problems. It probably does have to
do with privileges on the folder, but since I have all administrative
privileges on my PC (where the repositories are located) and since the XPE
tools are the ones who created the repository and all those folders, it
seems that they should have applied the necessary privileges to be able to
update the files.
Click to expand...

If I recall correctly, by default XPe install creates the Repository network share with read-only permissions for Everyone.

KM
 
Back
Top