Is there any specific reason why SSIS (and SSAS as it seems) do not come pre-setup with a "Release" configuration within Visual Studio (using 2015 at present) when a new project of this type is created? - I can only see that they come with a "Development" configuration as standard.
What also seems to be a little counter-intuitive, is that by attempting to create a "Release" configuration for the SSIS project specifically, Visual Studio indicates this already exists so prevents you creating it. However, it does let you rename the "Development" configuration to "Release" (which would suggest it didn't already exist).
I quite often have solutions containing different types of projects (e.g. C#.NET, SQL Database, SSIS, SSRS) but if I want to build these using a standalone build server and build the project via the command line use of the Visual Studio "devenv" exe/application, there is no "Release" configuration for SSIS (and SSAS) as default. Building using the "Default" configuration may not be desired on some of the projects and it seems additional work to add a "Release" configuration into every new SSIS (and SSAS project) just for this purpose, when, on first view (please feel free to correct me if wrong or there is some good reasoning for this), it would seem a reasonable piece of functionality to have as standard on a new project of these types.
It's often more convenient (less setup) for me to build a Solution of Projects using the same configuration rather than each Project specifically using different configurations per project.
Any thoughts/reasoning on this?
