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 have website which runs multiple threads. When user close the browser but threads are still running. How to kill/stop all thread in asp.net on browser close.
I have a web page with paypal. In the page user add items to list then buy it. when user add item to list i block that item in stock until user buy or delete that item.Now my problem is when user add item in the list and then close the broswer from IE close button , the item get blocked. I want to rollback the added items when user close the browser from IE button.
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.
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 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?
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).
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 know you can point to a OnSelecting event on the aspx page datasource. But I've created my SqlDataSource in the code behind. Is there any way to point to a selecting event in the code behind (I need this to provide the parameters)? Or should I just include all my logic in the Page_Load event (where I keep my SqlConnection)Here's what I have so far:
I am using this code.This pop up window pops up when I clicks a button on the main page.Now I want the pop up window to be closed if the password is successfully changed and reload the main page,but if the password is not changed then refresh the pop up window again.
I have a page where I load a couple of dropdown lists from the database (DB). I do this by calling a general function that connects to the DB and gets the data to the dropdownlist. This means that I can have three queries to the DB while rendering one page.
should I close and dispose the sqlconnection, sqlcommand and sqldatareader at the end of this function?
Would it be faster if I left it open for the next call, if you get what I mean, or is it best to close and dispose it every time?
I am having trouble closing jQuery Facebox from code behind. I am inserting a new record through FaceBox, on successful insertion the FaceBox needs to be closed. How can i achieve this?