471,316 Members | 1,674 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,316 software developers and data experts.

Configuration Management of a Composite Application

Our tool control applicatioin is currently comprised of a .NET part written
in C#, components written in C++ and a Lab View component. They are at
different version levels. Not all composite parts change with each version
of the product. The .NET and Lab View components are outsourced.
Some questions:
1) What are the recommended practices for managing a composite configuration
such as this?
2) Are there tools on the market that facilitate management?
3) Is a top level version number typically assigned to the composite?
Tpically, should the main UI show only this version or should it also show
the composite part versions as well?
4) Should this top level change whenever one or more of the composite parts
5) How would the configuration be integrated with Install Shield?
6) Should there be an application that does nothing else but contain the top
level version number? Are there better mechanisms?


Ken Whelan
Software Group Leader
Jul 21 '05 #1
0 1085

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by Serge calderara | last post: by
reply views Thread by Philippe Poulard | last post: by
1 post views Thread by Paul Kia | last post: by
2 posts views Thread by Terry Holland | last post: by
reply views Thread by rosydwin | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.