Project 1: Web Application (.aspx/.ascx/.cs/)*
Project 2: Class Library (has one static class, Repository.cs, which is full of static methods used to put/get data to/from DB)
Project 3: Web Service (allows few of the mthods of the Repository to be used via WebService)
Conditions:
There will be about 10 copies of Project 1 (WebAppliation) runngin on IIS each for a seperate client.I want each copy of Project 1, and the Web Service to read/write data from/to DB via Repository only. So all 11 Projects (10 Project 1, and 1 Wb Service, will be using repository as DAL)Questions1) Where shall i put the connection strings??? because each web application will have its own connection string, i cant save it in repository. And if i keep it at the web.config of each project, then what is the best way to pass it to repository?
2) Repository.cs is a static class with all static methods, is this a good approach? Should it be static? or should i not make it static in order to allow creationof objects of Repository.cs. (this way may be i can also send connection strings to the objects
of repository, in whatever project required...???)
I have a db connection string 'ApplicationServices' defined in the connectionString section of web.config and 3 Entity Framework connection strings which have the provider connection string attribute with the same connection string as the one in 'ApplicationServices'. Is there a way to reference connectionString in 'ApplicationServices' for the provider connection string attribute of the EF connection string in the web.config, rather than providing the connection string all over again?
just for my testing purpose i know i can define both the connection's outside in a single web config file by different name's and access them in my front end according to it but what if i want to have seprate for both connection's web.config situation is like this see image so i want to access my connections from second web config file how i can do that.
I am preparing for an Access2007 db conversion at the beginning of the year and would like to know what the best process would be for connecting to the sqlserver2005 database. I have read about adding the connection string to the web.config file. I have also read about using ADO.NET and put the connection information into a class and not the web.config file.
I would like to hear from others as to what you have used, are using, or plan on using for a webapp (vs2010), and why so I can get an understanding.
I have an ASP.Net website running on IIS7. The Application Pool is set to ASPv4 Classic.
Authentication Mode is set to ASP.Net Authentication & Windows Authentication
My question is, when I want to connect to SQL using a "trusted connection" in the Connection String, what user will actually be passed into SQL?
I thought it would pass my logon details, but it is coming back with an NT AUTHORITYANONYMOUS LOGON error, which seems to point towards it not passing in my logon.
on VWD 2005 this code works fine, but on 2008 it says I haven't created an instance of the object. I want to convert the object connString (a connection string) into a string.
'This acceses the virtual directory web.config file for connection strings 'We have to convert the object to a connection string Dim rootWebConfig As System.Configuration.Configuration rootWebConfig = System.Web.Configuration.WebConfigurationManager.OpenWebConfiguration("/VirtualDirec") Dim connString As System.Configuration.ConnectionStringSettings connString = rootWebConfig.ConnectionStrings.ConnectionStrings("ConnectString1") Dim strConnString As String = connString.ToString().......
I have an ASP.NET project which gives me the following exception if I try to run it Where should I "call" it before I can use it ?There is no global.asax in my solution
I have an ASP project that works fine locally. It makes use of a dll that gets information from a database. I set this up using the datasource wizard, which is not how I like to do things. I find it to be a bit opaque, and this problem is a fine example. When I publish the website, I get an error that ultimately shows this:
Login failed for user 'NT AUTHORITYANONYMOUS LOGON'.]
That suggests that it is not using the username and password, so I went to the App.Config file in the dll, which is the one place that has the connection string that I know of (normally, I'd do it in code and it wouldn't be there, but I'm doing something new). If I change the DB name to a DB that is very similar to the correct one, then run one of the queries, it correctly complains about a few missing columns. As long as I use the correct DB name, then it works (there's a production DB and a dev DB. The two are identical except that I haven't added a few columns to the tables in the production DB). This shows that the connection string is being at least partially used.
However, if I alter the password, such that it is invalid, I have no problem running the query, which suggests that the username and password are being ignored, and my own local credentials are being used instead (or at least that's the going theory as to why I can connect just fine when the password is wrong). The credentials are set up correctly as far as I can determine. That portion of the connection string are copied directly from a different project that works fine.
So, despite having credentials that should be valid, the dll appears to be steadfastly using my local credentials and ignoring the ones in the connection string in App.config. I would assume that this has something to do with the datasource wizard, which I don't use.
I added a database to my project. When I did so an app.config file was added to my project. (Yes I know I have dangerous info in the connection string. I shall change that but for now I am messing around with test stuff.)
I did a google search on how to get the connection string value and found. string sConn = ConfigurationSettings.AppSettings["ConnectionString"]; I am getting a warning that this is obsolete. It has been replaced by ConfigurationManager.AppSettings. Ok Fine. According to the docs, it is also in System.Confiuguration which I already have a using statement for above. But when I attempt to use it, it is not part of the assembly.
Split off from http://forums.asp.net/t/1646657.aspx/1?MVC+3+Tutorial+Movies+database:
I have the same problem here.No matter what changes I make in the connection string, in the Web.Config file, MVC3 tries always to connect to the SQLEXPRESS database that I do not have. I am running the 2008 SQL Server Standard Edition on my desktop.
How and where can I replace the reference to SQLEXPRESS by one that allows me to connect to my local database?
I have created a ASP.NET 4 application in VS 2010 using Silverlight and RIA Services.
After finishing the first release on my development pc, I'm starting some deployment testing in a server in my local network.
After sucessfully published the web application using the Visual Studio FTP publishing option, I notice two strange things:
1 - On the IIS properties of the website I have uploaded my files to, you can see now a connection string, named as LocalSqlServer that points to the aspnetdb.mdf database file. I had a look in the web.config file and I could not find this connection strind defined there. So, where is it located? Where did IIs got it from?
2 - As the aspnetdb.mdf file is not deployed withtin the web application and I a musing SQL express in my testing server, where can I drop the mdf and ldf files so they can be attached when the applicaiton runs? I know I can perform an attach operation using management studio,but I'm wandering where is the DataDirectory folder ASP.NET looks for to attach it at runtime?
total noob question here. I'm toying around with Silverlight, and need to connect to a database. When I connect in server explorer (VS 2010) it works fine, because it's using my windows account to authenticate. However, when I start debugging the server side stuff is running on a different account (NT-SERVICE or something to that effect) which has no privileges on the SQL server. I've tried embedding my username/password like this:
but it doesn't seem to be working. I keep getting an error:The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.
I have just re-implemented an ASP.NET web application that uses NHibernate to use a session per request (using an IHttpModule). The SessionFactory is created at the start of the application using a connection string from the web.config file. The SessionFactory is then stored and sessions created and released using a thread-safe, lazy singleton.
This means that if say 20 users are using the application the same user (as specified in the connection string in web.config) is used when creating any connections to the database - is this best practice? Will SQL Server Express complain about the number of connections eventually? (as connections are created and released per request this may not be a concern in practice).
In my old architecture a connection was created using the user name of the current user - is there any advantage to this (perhaps if there is are security restrictions for the logins of each different user).
When using a thread-safe, lazy singleton (like below) which contains the SessionFactory and manages sessions, I believe this is available site wide wide e.g. 2 users accessing the application from different PCs will use the same instance?
public static NHibernateSessionManager Instance { get { return Nested.NHibernateSessionManager; } } private class Nested { static Nested() { } internal static readonly NHibernateSessionManager NHibernateSessionManager = new NHibernateSessionManager(); }
I have a entity data model generated from a database schema. Now that database is no more physically available, I want to generate a new database with the same schema model. I'm able to generate the tables from the script that the Entity Frame work generates for me.
I have two problems. I'm not able to generate the stored procedures from EDM. Second, I'm not able to change the connection string to the new database. Do I have to re-generate the edm from the new database that I'm trying to create?
i have create users and rolls and all thing work very good on my computer but after upload view exception
Code:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) how can i change connection string for mdf database
I am using a gridview control (.aspx page) that has bound columns. I have a sqlDataSource that connects to oracle. The userid and password is saved in the sqlDataSource control.
Code:
<asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="<%$ ConnectionStrings:ConnectionString %>" ProviderName="<%$ ConnectionStrings:ConnectionString.ProviderName %>" SelectCommand="SELECT BO_SECID, CUSIP, PRICE FROM QRM_MBS_CURR_EOM WHERE SETTLEMENT_DT > AS_OF_DT" </asp:SqlDataSource>
Question: When I deploy to a different region (like from Development to Test region), using MSI install, how can I change the connection string (because the userid and password are different in different regions).
I have a problem registering a stored procedure in the EDMX file in my web application. When I try to add the function, I have the message:
"No Database connection is defined for this model"
All the buttons are also disabled. If I click on the white spaces to get the properties of edmx file, the connection string is blank. I am not sure how this came about. Everything compiles and runs I can add tables and views but not Stored procedures. I created a test project from the scratch and added a new edmx file and I was able to add the stored procedure. i nthe new project the connection string is defined. Connection strings are defined in the web.cnofig. I suspect that somehow the edmx file or project got corrupted.
How do i configure connection string for Asp.Net Membership Provider? Do i have to write it by hand or any tool is available in Visual Studio where i can specify connection string as well as algorithm used to store password? I read one article and it specifies this connection string :-
