Printable View
;) Simple question...
I need to store a constant kind of like a connection string / or a file path in vb.net. In asp.net I usually store these in the web.config file. Then in aspx when I need the value I simply do:
ConfigurationSettings.AppSettings("NameOfMyTag")
to get the value I need. How would I do this in vb.net ? Do I store it in the assemblyinfo file ?
You have something similar available in vb.Net.
The xml file named applicationname.Exe.Config will reside where your exe exists and you can use System.Configuration.ConfigurationSettings.AppSettings to read the data within.
If you are using 2005, you have the new My namespace. You can add the values to the Settings.settings file and then reference them with My.Settings.ConnectionString, etc.
I am using vs.net 2003 there is no xml that I see. My exe is inside the bin folder and the only file with it has a .pdb extension.
Select Add Item and then select "XML File". Make you sure you name the new file "App.Config". The item will be placed in your project directory. But now, when you build the application, Vb.NET will automatically copy the file with the appropriate name to where it's supposed to be (your debug or release directory).
Add a config file to your project the same way you add any other file type. Alternatively, if you create a connection in the designer you can open the DynamicProperties section of the properties window and bind the ConnectionString to an entry in the config file there, which will automatically create a config file.
Can you give me a sample line item inside of this file...and how to call it.Quote:
Originally Posted by Bananafish
Like a constant...
In the config file,
<configuration>
<appSettings>
<add key="ConnectionString" value="......." />
...
To access it,
System.Configuration.ConfigurationSettings.AppSettings ("ConnectionString")
A database connection string stored in plain sight? :eek: That's not a security risk. :p :D
Yeah, it's insecure and the user has direct access to it. One could choose to encrypt the string before placing it in the config file, and decrypt it just before the code needs to use it.Quote:
Originally Posted by MrGTI
It would not be insecure in a web app, since the config file sits on the server.
Maybe for app.config, Ive never had to write a vb.net with db app...Quote:
Originally Posted by MrGTI
but for a web.config asp.net application how is it insecure ?
It's more secure than in the case of winforms.Quote:
Originally Posted by JAKSupport
Unless a hacker gets direct control of the server itself. Otherwise the HttpModules for ASP.NET handle requests for web.config and call it 'unauthorized'.
There are many ways a webserver could be vulnerable.
Besides the obvious idea of a hacker getting onto the machine, there’s many other ways. Maybe the server is backed up each night, and the backups are stored on another machine. Maybe someone makes a copy of that backup, and then restores it to their personal machine. Then they can browse your files with all the time in the world, and locate your easily visible database connection string.
Keep that info as tightly guarded as possible!
.NET 2.0 adds explicit support for config file encryption and on-the-fly decryption. Just one more improvement to add to the list.