Repositories Have Version Numbers. So why don't they "version" anything?

  • Thread starter Thread starter Gereon
  • Start date Start date
G

Gereon

When I come out with version 2.0 of my software, I would expect that I would
"Update" each of my "Released" components in component designer to 2.0. Any
target created before 2.0 existed still sees the settings for version 1.0 of
the component, no problem.

By the same token, I would also expect that when I upgrade, I would change
the component to use another "version" of the same repository. This new
version would keep its own separate archive, so that 1.0 and 2.0 do not
interfers. But apparently, that is not the case. If I change the version
on my repository and import it, it just overwrites my old files in the
database. What good is having a version number in a repository if it still
only stores one copy of my files for all of them?
 
Gereon said:
When I come out with version 2.0 of my software, I would expect that
I would "Update" each of my "Released" components in component
designer to 2.0. Any target created before 2.0 existed still sees
the settings for version 1.0 of the component, no problem.

By the same token, I would also expect that when I upgrade, I would
change the component to use another "version" of the same repository.
This new version would keep its own separate archive, so that 1.0 and
2.0 do not interfers. But apparently, that is not the case. If I
change the version on my repository and import it, it just overwrites
my old files in the database. What good is having a version number
in a repository if it still only stores one copy of my files for all
of them?
Click to expand...

Two approaches:
1. Use different filenames within the same repositories.
2. Use different repositories (version 1 rep, version 2 rep).

It's acheivable with the existing tools. For example, XP release and XP SP1
bits exist within the repositories.
 
Thanks Gordon. I have read that you need to create a new repository any
time you want to introduce new files. And if I gotta do it, I gotta do it.
It's just that, man, this tool seems to be its own beast in so many ways.
It's frustrating. And I was hoping somebody could tell me **WHY** they made
the decisions they did, especially with the repositories. Am I the only one
that thinks this is totally counterintuitive?
 
Sounds like you want Source Safe functionality in the XPe
toolkit. I agree with you that it would be nice, but MS
probably didn't want to reinvent the wheel. Personally,
I store all my component revisions in Source Safe and
only keep the latest version in the repository/component
database. I realize that you may not want this extra
step, but it works.

HTH,
Tony

-----Original Message-----
Thanks Gordon. I have read that you need to create a new repository any
time you want to introduce new files. And if I gotta do it, I gotta do it.
It's just that, man, this tool seems to be its own beast in so many ways.
It's frustrating. And I was hoping somebody could tell me **WHY** they made
the decisions they did, especially with the
Click to expand...
repositories. Am I the only one
 
Back
Top