We decided to use the registry for handling our deployment with connection strings in our VB.net application.
The requirements are:
If the program cannot connect to the server, first check the registry for a connection string. IF not, create the folder and fill in the name, type, and data. Make sure its encrypted.
I have never edited or created anything in the registry.
My problem is storing multiple string in the my settings to clarify more on this ill try explaine as best as i can,
'I set my value like so
Dim strSettings As New My.MySettings
'On the form load i use this
Dim itemz As New ListViewItem
[Code]....
I've came to the stage where i need to save strings and application settings for my application. The My.Settings have worked it out until now. Now i have to store so many settings it's hard to keep track of them. That is why i need something new. So i've been looking around in INI files which seems impressively simple - but not very flexible. I've also took a look at XML which seems to be something to dive in to. But what i need now is advice. How do you store settings?
View 11 RepliesI recently had to use my "String converter" to convert 20 lines of text to a single line of "VB .Net String coding". For example:
This is line one
This is line two
This is line three "with extra stuff"
[Code]...
"This is line one" & vbCrLf & "This is line two" & vbCrLf & "This is line three " & chr(34) & "with extra stuff" & chr(34) & vbCrLf & vbCrLf & "Empty line above me"What is the best way to represent these types of Strings? For example, if you have to display a long message or just a label with information that changes.I was thinking of some sort of text file collection, but it is a little useless to have 100 text files of information of 5-6 lines.
I want to store a string variable value in the windows registry If the below is a correct statement. My.Computer. Registry. SetValue ("HKEY_ LOCAL_ MACHINESYSTEMMyKey", "Start", "ABC")i will declare a string variable Dim strvalue as String strval = InputBox("Enter a string")and now i want to insert the User given value in the Registry Key as above in place of "ABC".
View 2 RepliesWhen it comes to storing SQL in code, most people use strings:Dim strSql As String = "Select Foo, Bar From FooBarTable Where Something = @Something"The problem is, when you have very long SQL strings, reading them in code becomes difficult. You can usually split the strings up like this:
Dim strSql As String = "Select Foo, Bar From FooBarTable " & _
"Where Something = @Something"
This causes a number of problems:
[code].....
I'm rewriting a legacy application in .NET. In the earlier version, I used a few control .INI files that could be edited by the advanced user to provide variation in certain program options. (The program also permitted override of these same variabes via menus and such.) I used the API functions to read the .INI files and rewrite them to alter the user's environment for subsequent runs.
View 19 RepliesI'm having to store a user account locally on a machine, what would be the best method to store this? (Needs to be reversable encryption rather than hash)I'm accessing a UNC share as mentioned here: url...Can anyone suggest a better method or changes to the above to secure the credentials as much as possible?
View 1 Replieswhat is alternative way for storing data if connection of database fail in vb.net application
View 3 RepliesDoes anyone know how to store the connection string in a file rather than hard coding it in the application. For example i have declared this connection string in the form to connect to oracle database and it works. But i assume this is not the right way to go by if one is looking for more secured environment.
strcon = "Provider=MSDASQL;" & _
"Driver={Microsoft ODBC for Oracle}; " & _
"CONNECTSTRING=(DESCRIPTION=" & _
[code].....
I've always used this approach while implementing data layer DLL for web application:
1) put datasets into the dll project
2) use a helper class with a method like this:
public shared sub settCnnStr(strconnhere as string)
My.Settings.Item("connectionString") = strconnhere
end sub
3) when I need to use the dll I call a method like this (usually into global.asax):
xxxxxxx.helper.setCnnStr("yyyyyyyyyyyyyy")
This method always worked for me nicely but I'd like to know if this method could have serious drawback or if there's a better solution.
I have several programs I have written for my music studio/production company. Many dealing with inventory, customer DB etc. All of my programs are in VB6 and I have started to convert them all to VB.NET. I am getting proficient with VB.NET and connecting to DB using the very simple and generic connection strings, Example:
dbProvider = "PROVIDER=Microsoft.Jet.OLEDB.4.0;"
dbSource = "Data Source = C:/develop/Customer Tracking/resource.mdb"
con.ConnectionString = dbProvider & dbSource
[Code]....
As you can see I am using a basic MSAccess DB and I want to get away from this and start using SQLExpress,
connect to a standard SQLExpress DB? (when I loaded SQLExpress I took the defaults...)
What is a dynamic MS Office Connection string? I have realized that each each version of MS Access has a unique Connection String. Now my concern is that if I use MS Access 2007, for example, it may haave compatibility/connection problems if an application is deployed in a machine with a different edition of MS Access. Is my understanding correct? If so, how to go around this hiccup?
View 2 RepliesI'm creating a program in VB.Net that heavily interacts with 2 large MSSQL databases. I do not know a ton of vb and I'm fairly new, but I would assume just having the connection strings in the code and releasing the program it would be quite easy for someone to reverse the program and get my connection info? correct me if I'm wrong. My question is I'm wondering if there is a safer way to use a connection string in my program. Would I just have to encrypt my app? Create a module or dll?
View 2 RepliesI have read and worked through all of the examples in the book "ADO.NET 2.O", but there is so much there with so many ways to handle data, I am having difficulty translating the examples into my own real life application. I am confused about creating runtime connection strings, connection strings in my app.config file, connection strings in the properties for a sql connection control, etc.
I have a midichildform with a datagridview control, and I use a table adapter to edit and update the SQL Server 2005 Express edition database. There is no problem there. However, I also have a button control that I want to use to "process" the data that has been updated with the table adapter. I want to open the updated table, read each record on at a time, manipulate the data and add a records to another table. Do I have to create a connection string and an oleDBconnection? Or can I somehow use the connection string that is in my app.config file? [Code]
I need a bit of advice. I would like to store secure connection strings somewhere safe in vb.net. How can I build the secure connection strings in what situation and what would be the best?
As I have done the little research and found that the secure connection strings would be encrypted the strings and input the strings in app.config, so I would have to make a change in the app.config[code]...
I have been struggling with the construction of an Access connection string. Here's the problem.My Visual Basic 2008 project is located in a disk partition on my hard drive that I have named S:. My Access MDB file is in the same location.When I deploy the application it obviously will not be in an S: drive on the user's machine. My concern is that if I construct the Connection String using the file designations on my computer as:
(Provider =Microsoft.Jet.OLEDB.4.0; Data Source =S:MyApplicationmydatabase.mdb; User Id =admin; Password =
The deployed application won't know where to look for the data file. I know there are some shortcuts that will allow me to construct the connection string, but I do not know either the designated names or where to find them.
I have two executables that access a DLL containing Data Access Layer objects Each exe can have a different config containing info on server and database name, connection string etc.How do I pass the config info to the DAL objects?
Obviously I can pass the config strings to the DAL objects every time I instanciate one, but that seems messy and repetitive as every class in the DAL will require Properties for the Config strings..if there is a way for the instanciated DAL objects to read some properties from the calling object without me having to pass them explicitly?
I've just started ASP.NET for real, and I was wondering if it is possible to use connection strings from Data Sources instead of hard-coding them. I've added my connection in Data Sources and it works, and I can also drag a table to a page in design mode, but I can't figure out how to access it in code. Here's what I get when I drag it in:
<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="False"
DataSourceID="SqlDataSource1"
EmptyDataText="There are no data records to display.">[code].....
In the past I've used a Singleton Pattern to load the connection string when the application starts via the global.asa file.
I have a project now where each user has a unique connection string to the database. I would like to load this connection string once. The issue is that the singleton pattern will not work for me since each user has there own connection string. Basically the connection string is created dynamically.
I do not want to store it is session. If anyway has a clever way of doing this in .NET let me know ?
How can I call the connection string by name from an app.config file in my vb.net program?
View 1 RepliesI'm having trouble accessing the connection string from the app.config file. my connection string is:
Dim sConnect As String = "Data Source=.SQLEXPRESS;AttachDbFilename=G:VB Level 1ProjectContactsDB.mdf;Integrated Security=True;Connect Timeout=30;User Instance=True"
I using this string in a few different places, but I want to access it from the App.Config file. I've been at it for awhile and can't get it working.
from [url] they write this:
This example includes a password to demonstrate how DbConnectionStringBuilder works with connection strings. In your applications, we recommend that you use Windows Authentication. If you must use a password, do not include a hard-coded password in your application.but if we do not hard-code the password then does it mean that we are supposed to retrieve the password from some other place? so is it correct to say that we should save the password in a file and then retrieve it when the app runs?
I am using VB 2008 & MS Access 2007 Databases for my Windows Forms Applications.The Problem is my Connection strings have been disappeared from DataSource Configuration Wizards & now i am unable to edit any Connection String in DataSet Designer.I had tried to create a Macro in MS Access Data File but didn't know how to create & so desided not to save any & just quit from Access and came back to Visual studio. Since then only this prob. has started. Earlier to this everything was just fine.I have tried to uninstall MS Office as well as Visual Studio then Re-installed Visual Studio but the problem is still there.
1] Error while trying to Reconfigure Data Adapter in Dataset
2] Disappeared options & Empty Connection Combo Box
3] Add Connection DialogBox with no DataSource property line in the Grid control
I have a situation where I have a vb.net program that uses two connection strings. This program will be used on multiple web servers on multiple domains and the only difference for any of them is the two connection strings.What would be the best solution to read in these connection strings from a file separate from my actual .vb code?
Ideally I want to be able to drop the .vb and the connection string file into its own folder on any number of asp.net websites and not update anything else (for example add any connections to the web.config or anything) than the external file containing the connection strings, I assume something like xml would suffice?
I would like to store secure connection strings somewhere safe in vb.net. How can I build the secure connection strings in what situation and what would be the best??
As I have done the little research and found that the secure connection strings would be encrypted the strings and input the strings in app.config, so I would have to make a change in the app.config
To change from this unprotected app.config:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
[Code]....
The code have been built to a guy who known as Nick J. Fessel. I am not too sure if it very secure to use it so. Do anyone know that if the connection strings is secure or not?
info for the secure connection strings without being found out
I'm trying to create an ODBC in the registry using VB.NET. I had found some code on the internet(link below) to do perform this function in VB6, but have been unable to find a way in VB.NET.
[URL]
I am working on a VB.net winform application which makes extensive us of a mssql database. For the most part (almost exclusively), I have used the Visual Studio dataset for accessing the data. This means that the connection string was created as a program setting, and is saved in the app.config file. The problem that I have, is that I need to move this connection string to the system registry because it has been deemed by the powers that be that a config file is not secure enough.
I think that I can figure out how to access a registry key, and I know that I can save the string to a registry key, but the problem that I am running into is that I don't access the connection key in the code anywhere to easily swap out the registry key for the existing program setting. When VS creates the connection and dataset, where is the connection string referenced? Is there a simple way to swap these out? is it possible even to just reference the registry key in the setting so that I don't have to find where the setting is used and switch it out?
I have finished my program and now i am ready to deploy it. The only problem is it is a multi-user application. All i want to do is simply run the program with the database from a server, and have other local computers with the program access this same database. I know that you have to change the connection strings for the local computers, but how can i go along doing this?
View 2 RepliesI have upgraded my VB app from VB to VB.NET and its working fine. Now, I want to convert my existing DB connection strings from ADODB to ADO.NET so that I dont have to use MS Access on every client which runs this app. Currently the VB app looks up into an Access db to get the server ip, username, password etc. I aim to hardcode these values so that I wouldn't need the Access db anymore. Any inputs on how this could be done?
[Code]...