in my application when i type sqlconnection it is not showing any intellisence, i added the namespace System.Data.Sqlclient not only sqlconnection even i am not getting Page calss can u help me.actually i am sharing this application from my company server.
in our company previously there was .net 2.0 frame work when this project was developed(one year back).
yesterday our company installed 3.0 .net frame work is this any problem for previous project which are developed in 2.0 how can i go through this problem.
I have a strange problem in my ASP.Net 3.5 application. When multiple users try to access the same page (which has some long running methods), the application crashes at a point where it tries to open a connection to the database (a static method inside a static class). It appears that the connection is already open. However, this does not happen when there is only one user using the application. What I cannot understand is that how do actions of one user affect the other in a web application?
I double checked that all my open connections are being closed after performing their operation by appending a line of text to a text file whenever a connection is opened or closed. The number of opened and closed connections was equal. Also, the connections are opened and closed from one place only, where the close method is inside a Finally() block.
I'd like to pass data from one asp.net page to another. I've seen that using System.Web.Caching.Cache is a good way to accomplish this. I'm wondering if it's a good way to do it and also is there any cleanup or other things I need to keep in mind when you the Cache?
We have a Page Method on a web page using ASP .Net. We tried to put in a trace statement using both System.Diagnostics and System.Diagnostics.Debug. In Visual Studio 2008, the break point is not even hit for the line, but other break points on other lines are hit.There is no output from either method that we can see.
There is also a Global.asax error catcher that works fine in other cases, but in the Page Method is not being catched.why a Page Method and System.Diagnostics do not play well together?
i would like to know if there's something wrong in this asp.net code:
mydatareader = mycmd.executeReader() if myDataReader.HasRow then // Do something end if myConnection.Close()
If i avoid to call a "MyDataReader.Close()" does the connection close anyway ? I ask this because i'm assuming that if call a "MyConn.Close" it automatically close the associated datareader... or am i wrong ?
I got any error from the code, saying 'not all code path return a value', i suspect it is the catch block doesnt return a value. If so, what value should i return?
i have 5 methods in classA. each and every methods i have open the sqlconnection and close it, instead of that is there anyway to create a sqlconnection at one time if its opened then no need to create a new connection, if its closed then we have to connect.
I always use SqlConnection() To open a connection then use the connection to interact database. But I have heard somewhere that opening SQLconnection() take a time. and if on different pages of projects I repeatedly Connect database then It will take long access time always. So I want to know that if there is any other methods which don't use the SQLConnection to interact database and increase the response time of database.
so i have the function below in a webservice. and it works, but when i try to copy it to aspx page code behind, i get the message in the subject. Can someone tell me if the function below is valid? One of my project uses it and it works.
I have a problem that is really confusing me.. I'm trying get get info from a database and populate the relevant labels. I've got it working on one page, but not on another. The only difference is that the one that works is in a repeater.
My code is as follows:
[Code]....
The error I am getting is the following:
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0117: 'System.Web.UI.Page'does not contain a definition for 'DataItem'
i would like to write a streaming programming which will keep updated or query the database. I would like to use a connection instead of open and close connection on each transaction. But the streaming programming would not end, running at all the time. So, is it any effect if i am using only one connection (within a long period). Such as performance, timeout issue, or others exception.
I have a whole bunch of data access methods where in each one I am doing this
[Code]....
and them moving on with my SqlCommand and SqlDataReader and so on.Is this creating to many instances of an SQLConnection?I was thinking doing this instead. Creating a SqlConnection Manager which would look like this
[Code]....
and then in my database access methods
[Code]....
Is this a good or bad idea and why?Also would this even be neccesary?
Because of the way the server is set up I'm using, I don't think I can use Integrated Security=SSPI in my SQLConnection string. However, I'm a bit wary of giving the database username and password in the connection string in a aspx.cs file. Is there any way of making it more secure?
When i fill my sql adapter daAuthors.Fill(dsPubs, "MYTable") sometime i get A first chance exception of type 'System.Data.SqlClient.SqlException' occurred in System.Data.dllmy code can run for a lot hours without any problems but sometime i get the message
Declaring the SqlConnection and SqlCommand objects in a webform without CodeBehind I am trying to query data from a MS SQL server with a C# web form without "CodeBehind". I want to write the information to a table in the web form's body.
I am having trouble declaring the SqlConnection and SqlCommand objects that connect to the server.
How do you use "using System;", "using System.Data;", "using System.Data.SqlClient" inside the script element of an .ASPX file?
I'm trying to determine whether it is better to declare the connection outside with it's own using statement or to create it inside the sqlcommand itself. This is in regards to a single command interaction with the database (no loops).
