Community
Participate
Working Groups
The ServiceModelManager has a method setActiveConfiguration() which is never called from anywhere. So when the active build configuration is changed the corresponding service model configuration is not set to active. The first service model configuration created for a project becomes the active one and it never changes. Steps to reproduce: - Create an RDT project with one configuration, call it Default - Set up the service model using the wizard and create the project - Create a new build configuration, call it Release - Switch to the Release configuration - Open the Service Model properties page, make edits. The edits effect the Release configuration. - The problem is the ServiceModelManager still thinks the active configuration is Default, so the changes to the Release configuration are not visible. When switching build configurations the service model configuration should be switched too. Also the new configuration dialog has a section to allow copying of settings from an existing configuration. This should copy the service model as well.
Question: is there supposed to be a correspondence between CDT build configurations and RDT service model configurations? Right now RDT uses the build info to get the name it will use for the service configuration. Perhaps it would be best to manage service model configurations separately. We could add a section to the Service Model properties page for creating and managing service model configurations. I'm thinking its likely the user will only want one service model configuration, so the user should be able to create build configurations without worrying about the service model. Also the user may want to switch build configurations without necessarily switching service model configurations. Thoughts?
We had intended that service model configurations would map to build configurations. But upon further thought, I think you're right. We should probably change this.
Given that we (as a rule) can't do any new UI right now, I would say that the best way to go about this for this release is to only have one configuration, which is always the default.
Created attachment 114707 [details] proposed patch In this patch, new service model configuration will not use the active build configuration's name. All service model configurations are created with 1 name, therefore there's only 1 configuration for each project Unfortunately, this will break existing projects.
Committed to HEAD. Thanks.
