This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Connect
- :
- FlexNet Connect Forum
- :
- Re: Managing multiple versions
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 28, 2003
07:12 PM
Managing multiple versions
I use ISX 4, and I am familiar with using the upgrade paths, product code GUID vs Upgrade code GUID. What's confusing me is that ISUS only uses the Product Code, not the Upgrade code. So when I use ISX4's registration feature and connect to ISUS, with each new version I create, I have a new Product defined.
Using ISUS's Add a Version feature, I created a new version and added a message under it, but of course the product code belonged to an older version, so the message never gets displayed.
Is this a conflict in implementation, or am I looking at this completely wrong?
Using ISUS's Add a Version feature, I created a new version and added a message under it, but of course the product code belonged to an older version, so the message never gets displayed.
Is this a conflict in implementation, or am I looking at this completely wrong?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 30, 2003
01:52 PM
Express 4 supports two types of updates.
1. Using the upgrade path
2. Using a quick patch project
Using the upgrade path, you can only create major upgrades. This means the your product code must change. As a result, you will need a new product in the Update Service each time you distribute an upgrade using this method.
Using the quick patch, you can update your application and keep the product code the same. Optionally, you can choose to increment the version or not. (we recommend that you do update the version) In this case, you would have multiple versions under one Update Service product.
1. Using the upgrade path
2. Using a quick patch project
Using the upgrade path, you can only create major upgrades. This means the your product code must change. As a result, you will need a new product in the Update Service each time you distribute an upgrade using this method.
Using the quick patch, you can update your application and keep the product code the same. Optionally, you can choose to increment the version or not. (we recommend that you do update the version) In this case, you would have multiple versions under one Update Service product.