You searched for the word(s): userid:789667

More Search Options

RSS Available

• Re: The query contains references to items defined on a different data context.

  um... the DataContext property needs to be a singleton so that you only have one instance alive at a time in other words... private class WorkListGateway { private readonly RADSData context; private RADSData DataContext { get { if (context == null) { try { ... context = new RADSData(connectionString); } catch (Exception ex) { ... } } return context; } ... } the problem that you are having is that everytime you call the DataContext property you are newing up a new object which means that your joins

  Posted to Data Access and ObjectDataSource Control (Forum) by mmeisinger on 4/16/2009

• Re: Right way to use persistent class?

  great questions... let's start out by answering number 2 first which will lead into answering number 1 (again... these are just my thoughts on the matter, smarter people than i have spoken on this topic) there is a term or a practice called Persistance Ignorance which simply means that your entities (or persistant objects) don't know anything about the underlying datastorage public class User { public int Id {get; set;} public string FirstName {get; set;} public string LastName {get; set;

  Posted to Architecture (Forum) by mmeisinger on 4/15/2009

• Re: Trouble updating a row using LINQ to SQL

  one thing that you can try to do is to log the query coming out if you are using linq-to-sql then there should be a Log property where you can send in StringWriter or something like that to see what the query looks like prior to execution of course if the issue is prior to the Expression Tree being fully evaluated then the log won't help you there still is something about the "cast" exception that is bugging me perhaps it would be better to take a step back and break this issue down

  Posted to Data Access and ObjectDataSource Control (Forum) by mmeisinger on 4/14/2009

• Re: Right way to use persistent class?

  well... i guess that is one way of doing it is it the right way? great question i am not someone to state whether something is the "right way" or not but i am someone who is willing to give an opinion i personally wouldn't do it this way and here are the reasons why it appears that you have no way of creating a CMSUser without hitting the database first this means that when i want to new up a brand new CMSUser that will be added to the database (or persistant storage) i have to first

  Posted to Architecture (Forum) by mmeisinger on 4/14/2009

• Re: HttpContext.Current.Cache shares data between browsers

  um... so the Cache is global meaning it is available to all users i think that you are better off using a Session object which is tied to a browsers session cookie (understand that IE will re-use the session cookie if you open a new tab or a new window within an existing process) if you can't use a Session object, for what ever reason, then you will need to uniquely identify a user in the Cache with a user specific or unique key hope that helps

  Posted to State Management (Forum) by mmeisinger on 4/14/2009

• Re: Difference between connected and disconnected mode in ado.net

  hm... how to explain this practicaly... when "connected" the connection to the server (or database) is maintained in state when "disconnected" the connection to the server is not maintained and the changes must be transmitted back to the server to "reconnect" and save the changes to the database so think of a client/server app like a win form or something if you are "connected" then the data being moved between the client and the server are being done with

  Posted to SQL Server, SQL Server Express, and SqlDataSource Control (Forum) by mmeisinger on 4/14/2009

• Re: Trouble updating a row using LINQ to SQL

  my initial thought would be that the HttpManager.MemberID is not returning the correct type if the "Profile" object has it's MemberID property as an Int64 and the HttpManager.MemberID is a string then i would pre-cast the HttpManager.MemberID to an Int64 (by using the TryParse method) you need to understand that this conversion might also happen at the db level rather than at the code level so try something like this (if my assumption is correct) Int64 memberId = 0; if (Int64.TryParse

  Posted to Data Access and ObjectDataSource Control (Forum) by mmeisinger on 4/14/2009

• Re: Variable memory usage...

  not that mudassarkhan is not correct but... it is important to understand what to do, when to do it, and why both the StringBuilder and the Dataset will be cleaned up once they fall out of scope it is my understanding (and would love to be corrected if i am wrong so i can learn too) that the Dataset has a Dispose method because it inherits from IComponent which more or less allows it to live in a "Container". this means that when the container is disposed of it will dispose of the Dataset

  Posted to Getting Started (Forum) by mmeisinger on 4/14/2009

• Re: HttpRequest.InputStream and HttpResponse.OutputStream, when are they closed?

  interesting question i don't think you can do it but... let's work it out the HttpResponse and HttpRequest are created at the time the web server recieves the request for a page or some resource clearly the HttpRequest.InputStream will have all of the data about the request (referrer, query string, cookies, headers, etc...) so thinking it through (from the ASP.Net side) when the request comes in all of that data is parsed for you so you can have a Request.Form collection, Request.Cookies

  Posted to Getting Started (Forum) by mmeisinger on 4/3/2009

• Re: Migrating from 3.5 down to 2.0

  you should be able to specify the Target Framework for the site, library, or executable if you open up the project or site and view the properties there should be a "Compile" tab you should see something like "Target framework" or something like that that allows you to change the .Net framework used to compile if you don't see it there then look for an "Advanced Compile Options..." button and it should be in there hope that helps

  Posted to Migrating from ASP.NET 1.x to ASP.NET 2.0 (Forum) by mmeisinger on 4/3/2009