Parker Lewis

Hello everybody

Could someone explain me when you'd typically use the new. .NET 2.0 "Application settings" feature and when you would use the "Isolated storage" Both support a user scope, thus what's the real difference Any links to continuative articles would be appreciated.

Kind regards



Re: Windows Forms General "Application settings" versus "Isolated Storage"

nobugz

Application settings are more geared toward automatic binding of properties to simple preserved values, ones that could also easily be modified by an administrator. They rarely require coding. Isolated storage has none such features but allows you to preserve much more intricate data. Start by using settings, you'll know when you're ready to use IS when you hit a wall.





Re: Windows Forms General "Application settings" versus "Isolated Storage"

Parker Lewis

Ok, I see. Property binding is surely a good cue. Thanks for your answer.

So, if you'd have a logon dialog which typically consists of controls for the user name and the password and maybe a remember logon data checkbox, would you save these properties into the application settings (user scope) Unnecessary to say that the password has to be encrypted.

Or would you go for the isolated storage in this case (password)

Best regards





Re: Windows Forms General "Application settings" versus "Isolated Storage"

nobugz

As a simple string, Setting without a doubt. That's what the IDE does when you use the DataSource wizard (or whatever it is called). Encryption is an entirely different matter, neither a Setting nor IS would give you a ready solution to that one. IS would be just a bit more obscure but just as breakable. A hack0r would need 5 minutes with a setting, less than an hour with Reflector if you use IS. A connection string shouldn't contain any sensitive data, SQL server readily supports that with the Windows Authentication logon option. Post at one of the SQL server forums if you need to find out more.