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?
But with MVC 3, I canīt create a child container per request(in really I can, using the old way), because container is hold at a static variable: DependencyResolver.SetResolver(new UnityDependencyResolver(container));
Which the better way to Dispose created objects? Since I use Repositories and Entity Framework (that need Dispose). As said here [URL] HttpRequestLifetimeManager donīt dispose objects....
I Want to know garbage collector works in .net there is something heap and stack funda.so can u please tell me from where i get reference of whole funda of that.and i have another question is that Please see below the code.here i declare one dt and get some data in it.and i don't want that dt after data come in text boxes.so in finally method i do dispose using dt.dispoe().but after that i write little code to check whether the dt correctly dispose or not.so i check with ifcondition after disposing.you can check code given below for that condition.as per condition it gives me "Nikunj" Ouput in message box it meanse dt is not disposed after calling the dispose method.so can u please tell me why?And i Want to know about all resources which i used i want to know how can i free it.whether it is variable,object,datatable,datareader etc..... if it is any where with example then please give me link.and if it's from msdn then it's better. i want to know from Microsoft that how Microsoft Suggest to do that.
Private Sub grd_expense_DoubleClick(ByVal sender As Object, ByVal e As System.EventArgs) Handles grd_expense.DoubleClick Dim dt As DataTable
Is there any real purpose to calling Dispose() on a Linq to SQL query? I want my site to be scalable so I'd like to control the datacontext but if it's not necessary I don't see a point.
If I explicitly put an oracle connection in a Using{} block I know that it will call the Dispose() method when it goes out of scope. My question is will the OracleConnection object be disposed in the following code block:
[Code]....
The OracleConnection is implicitly within the Using{} block for the OracleCommand and goes out of scope at the same time.
There's a problem, wherein a XML Document.Save is resulting in the error the process cannot access the file, because it is being used by another process or the statement an Invalid XML Document.I think it's because I do not dispose the XML Document object after it's operation is complete.Is it possible to do this.Is there a workaround?
When you create and use a Web Service proxy class in the ASP.Net framework, the class ultimately inherits from Component, which implements IDisposable. I have never seen one example online where people dispose of a web proxy class, but was wondering if it really needs to be done. When I call only one method, I normally wrap it in a using statement, but if I have a need to call it several times throughout the page, I might end up using the same instance, and just wondered what the ramifications are of not disposing it.
I have a member class that returned IQueryable from a data context
public static IQueryable<TB_Country> GetCountriesQ() { IQueryable<TB_Country> country; Bn_Master_DataDataContext db = new Bn_Master_DataDataContext(); country = db.TB_Countries .OrderBy(o => o.CountryName); return country; }
As you can see I don't delete the data context after usage. Because if I delete it, the code that call this method cannot use the IQueryable (perhaps because of deferred execution?). How to force immediate execution to this method? So I can dispose the data context..
I have an ASP.net page that is creating a service reference to a WCF service and making calls in multiple places in my page. I instantiate the service reference in Page_Load and have an instance variable to store it:
I just discovered that I need to be disposing of the service reference when I am done using it or else the connections will be kept alive and will block incoming connections if I reach the max number of connections. Where would the best place to dispose of these references be? I was thinking of doing it on the OnUnLoad event.
I have a class DocumentGenerator which wraps a MemoryStream. So I have implemented IDisposable on the class.
I can't see how/where I can possibly dispose it though.
This is my current code, which performs a file download in MVC:
using (DocumentGenerator dg = DocumentGenerator.OpenTemplate(path)) { /* some document manipulation with the DocumentGenerator goes here ...*/ return File(dg.GetDocumentStream(), "text/plain", filename); }
This errors as the stream is closed/disposed before the controller has finished with it. How can I make sure my resources are properly disposed in this situation?
EDIT: My implementation of IDisposable at the moment just disposes the MemoryStream. I know it's not a proper implementation, I just used it as a test. Is there something different I could do here to make it work?
public void Dispose() { _ms.Dispose(); _ms = null; }
I have created an asp .net ajax control, meaning i have a javascript object linked to this control. In that object as usual i have 2 crucial methods: initialize and dispose.
[Code]....
In internet explorer dispose method is invoked every time user leaves the page, even when closing the browser. But not in chrome, its invoked by refreshing the page but not by closing the tab or window. Do you know how to achieve this?
I use SmtpClient to send email. I want to ensure that the SMTP connection gets closed after each message is sent. I found an explanation of how to do this in the SmtpClient documentation on MSDN:
[URL]
One thing it says is: Call Dispose when you are finished using the SmtpClient. The Dispose method leaves the SmtpClient in an unusable state. After calling Dispose, you must release all references to the SmtpClient so the garbage collector can reclaim the memory that the SmtpClient was occupying.
I have a question about the last part. What exactly does "release all references" mean. How do I do that?
I'm trying to use linq to sql for my project (very short deadline), and I'm kind of in a bind. I don't know the best way to have a data context handy per request thread. I want something like a singleton class from which all my repository classes can access the current data context. However, singleton class is static and is not thread-safe and therefore not suitable for web apps. I want something that would create a data context at the beginning of the request and dispose of it along with the request
DataContext db = new DataContext(conString); var dvd = db.GetTable<DvdList>(); var category = db.GetTable<CategoryList>(); var query= from b in dvd join category on dvd.CategoryId equals category.CategoryId where b.Title.Contains(txtSearch.Text) select b; GridView1.DataSource =query;
project was clean after release build, but when i ran "Run Code Analysis" i got 256 errors. the error below is one of them. will be great help. if anybody can explain, what is the meaning of this error?
For no apparent reason (of course there must be one), my web project will no longer generate LINQ to SQL classes/data contexts!!!I am going about the usual routine of right clicking the project, adding new item, selected LINQ to SQL classes, then dragging over a table from Server Explorer, saving and build but no...the bloody thing won't appear!!!Does anyone know why this might be happening/what have I done wrong?
I'm running Visual Web Developer 2010 Express on Windows XP and I'm having some trouble linking my DataContext to a control.If I create a new "Web Site", add a new LINQ to SQL Class and add the database tables I want, then add a Control such as FormView and choose a new LINQ Data Source Type; my DataContext I created is visible in the list and all work OK.If I do the same after creating a new "Web Application", my DataContext doesn't show up in the list, but if I go into my Code Behind I can access my DataContext through:
i am working on Linq,as we know to use any table in linq we have to drag and drop it on our datacontext's Designer File,and at run time we got its value,till here no any problem,main point is if any changes in respective data source's schema has made ,then on datacontext we will not get that changes,for it we have to change this datacontext manually by by again drag and drop,it will not happen implicitly when this changes has been made on the data source. how i solve this problem so that datacontext change implicitly without any over head using .net 3.5.
I am using LINQ to SQL in a project. I create a new DataContext class (a "DBML").
This is a DotNetNuke portal, module project. DNN has a standard connection string named "SiteSQLServer." Of course, I want my DataContext class to use this same connection string.
In Server Explorer in Visual Studio, I have a connection to the development database. Of course, that connection knows nothing of the "SiteSQLServer" connection string in web.config.
When I drag a table into the DBML design screen, I get a popup message that the table I'm dragging in is from a different connection, and is it OK if it changes the connection string? If I say "No," then the table never comes in to the designer. If I say "OK," then Visual Studio adds a new connection string to my web.config file. Then I must click in the open area of the designer, then go to the Properties window and reset the connection string. If I miss this, then in testing everything works. But when I deploy to a production server, the connection fails. But even if I do not miss this, that extra connection string remains in my web.config file.
Is there a way to get Visual Studio to drop the table into the designer, and leave web.config alone?
System.Data.Linq.ChangeConflictException: 2 of X updates failed. at System.Data.Linq.ChangeProcessor.SubmitChanges(ConflictMode failureMode) at System.Data.Linq.DataContext.SubmitChanges(ConflictMode failureMode) at PROJECT.Controllers.HomeController.ClickProc(Int32 id, String code, String n)
This is what I get very often. This action is done thousands of times a day, and I get this exception about once every 5 seconds. From what I understand it happens when something changes in the database in the period between creating DataContext and updating it. Am I right?How can I fix it?I just debugged the error and found the following:
[Code]....
The Stats table is updated constantly. So how can I still make LINQsave the changes. With "classical" MS SQL access through SqlDataCommand I never had problems like that.