By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,592 Members | 1,931 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,592 IT Pros & Developers. It's quick & easy.

Configuration Management of a Composite Application

P: n/a
Ken
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
change?
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?

Thanks.

--
Ken Whelan
Software Group Leader
Jul 21 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.