How NOT to edit SSIS dtsx packages manually to change config filter in SQL Server configuration schema

Question

I have many packages that are using the package configuration with the following way:
-ALL Packages have the XML configuration file that has only one proporty defined. The ConnectionString of the SQL Server connection that holds the configuration table for the rest of the properties
-A SEPARATE SQL Server package configuration for
each connection manager in the package. 
-Finally an SQL Server configuration for all the properties that are specific to this package.
I attach a pic of what i mean: Yellow is the XML config with the connectionstring, Blue the connectionamangers and purple the package specific.
So with this setup  i can:
-Change the xml file location and just point all the setup in another sql server or another database.
- Or create different configuration filters in the same config table and try to go into the package and change the filter.
With all the above the problem is that if i do anything from within VS, i am loosing the password in the connectionstring because i am not using the encrypt property. And i dont want to use it...
What are my options? Just go in .dtsx with notepad and chage what i want BEFORE i open the package or before i deploy?
Elias

Answer 1

You are correct but:
-I dont want to use EncryptSensitiveWithPassword, so:
When i go to package configuration and try to change the ConfoigurationFilter to point to another setting then i am getting to the screen to select the property (connectionstring) and when i finish the DATABASE record for the setting is cleared from the
Password= that i have put previously.
So i short what i want:
-No EncryptSensitiveWithPassword 
-Being able to change configuration from within VS WITHOUT resetting the connectionstring string. 
Elias
Nope what you're asking is not possible
There's certainly a purpose why each of things are given in the current format
For design level settings you need to use connection manager properties and for it to persist values for someone other than creator to use you need to use protection level as EncryptSensitiveWithPassword 
And for runtime settings you need to specify values in config which has to be editted from outside the package by editing dtsconfig file or using update query depending on whether config is stored in file/table. In both the cases you can identify password
as a separate config item and modify its value from outside. That will work regardless of what you chose as protection level
see
http://blogs.msdn.com/b/runeetv/archive/2009/12/22/ssis-package-using-sql-authentication-and-dontsavesensitive-as-protectionlevel.aspx
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs