release component

  • Thread starter Thread starter Larry Waibel
  • Start date Start date
L

Larry Waibel

I'm not sure I understand the purpose of the Release Component Edit menu
option. When I've done that and then want to change I do an Update Component
and then I can edit it again. The only thing it does is bump the revision
number. But that happens every time I save; and I can't manually update the
revision anyway. I guess I was expecting it to force an update to the
Version number. Can anyone explain the purpose of this? Thanks!
 
Hi Larry,

I think that non released components will not pollute your database.
If you look in your database from CDBM you will see each component revision
that you have released in there.
So this is one of reasons why you should associate component with your
package. This will allow you to uninstall package and to automatically
remove all component revisions and other resources associated with package.

Regards,
Slobodan
 
Whether I release a component or not, if I import it into CDBM it's there so I
still don't see what releasing a component has to do with anything.
 
Another reason may be that by releasing components you get rid of annoying build messages about the unreleased ones.

Just FYI.. There is one bug of CD that I recently discovered about component release feature. If you have a CMI script assigned to a
component and encrypted, as soon as you update the component you will have to add (*update*) the script once again. Otherwise TD
build system will give you a non-descriptive message when you are trying to add the updated component to a SLX project. The error
message will say something like "The CMI Encountered a unexpected COM error".
 
Hi Larry,

It is not question whether it is there or not. But rather how many different
versions of your same component do you see from CDBM.

Regards,
Slobodan
 
Yeah, getting rid of the warning is about the only reason I can see to release a component
:-)

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: release component
Date: Wed, 9 Mar 2005 15:10:22 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Another reason may be that by releasing components you get rid of annoying build
Click to expand...
messages about the unreleased ones.
Just FYI.. There is one bug of CD that I recently discovered about component release
Click to expand...
feature. If you have a CMI script assigned to a
component and encrypted, as soon as you update the component you will have to add
Click to expand...
(*update*) the script once again. Otherwise TD
build system will give you a non-descriptive message when you are trying to add the
Click to expand...
updated component to a SLX project. The error
 
Back
Top