Hi Mike,
the suggestion was made because it is very simple to provide a sample program where you don't want to keep Passwords visible. It is very simple to make a sample program and instruct the user on how to create a "Password" file. Later you just copy the whole Thing without Password file and you are safe 100%. In my particular case, I have filenames associated to user and hostnames (like emails: filename = username(at)hostname, where I must escape Special characters).
1) Yes, the sample is very simple. A more complicated solution may use ini files (with GetPrivateProfileString).
2) In no way you can use my sample with "Shared repositories". At least not over Machine boundary. The encryption algorihms are based on Machine and (by Default) on User keys. If you Run your program on another machine you will not be able to decrypt the Passwords. Because of that, I suggested to check the documentation.
As far as I remember, with CredentialManager the constrains are the same.
the suggestion was made because it is very simple to provide a sample program where you don't want to keep Passwords visible. It is very simple to make a sample program and instruct the user on how to create a "Password" file. Later you just copy the whole Thing without Password file and you are safe 100%. In my particular case, I have filenames associated to user and hostnames (like emails: filename = username(at)hostname, where I must escape Special characters).
1) Yes, the sample is very simple. A more complicated solution may use ini files (with GetPrivateProfileString).
2) In no way you can use my sample with "Shared repositories". At least not over Machine boundary. The encryption algorihms are based on Machine and (by Default) on User keys. If you Run your program on another machine you will not be able to decrypt the Passwords. Because of that, I suggested to check the documentation.
As far as I remember, with CredentialManager the constrains are the same.