In my environment I have a .dtsconfig file where the deploy team will put all the property values( ConnectionString's from all data sources, ETL range period, etc...and this .dtsconfig has the path stored in a Windows Environment Variable.
I use this .dtsconfig like a web.config of a web server. All my environment configurations are stored on a single file. And all my .dtsx packages will point to this .dtsconfig
Problem: When I create a configuration value in the .dtsconfig, the Visual Studio show me a error when any of my .dtsx package that point to this .dtsconfig file not reference this configuration on the packet( reference through a variable or a connection string ). But this error is totally terrible for two reasons; first because even with this error I compile and run my packets normally, so is not a true error; second because it is terrible to try to force someone to create variables\connection string for ALL configurations in the .dtsconfig file.
Example: In my testconfig.dtsconfig I create a new property of connectionstring type called TestConnection for a new Data Source. I have 10 .dtsx packets that use this .dtsconfig, but only the packet number 5 will need this new connection string. So in the other 9 packages I will receive a fake error telling me that the connection TestConnection was not found on the package.
Constraint: I will not create more than one Windows Environment Variable to store the path of others .dtsconfig
Constraint2: My project type is: 'Package Deployment Model' type.
What I want: Somehow transform in optional this configurations values in the .dtsconfig OR some project configuration to never show again these fake errors.
Best Regards, Luis