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

More Search Options

RSS Available

• Re: User Control Registered in Web.Config cannot be used

  I have been unable to find a solution to this either. The suggestion of adding a redundant Register directive at the top lets the application compile, however VS2008 shows warnings in the code that "Element X is not a known element." If anyone comes up with a good solution to this please let me know. What I am doing now is changing the tag prefix so that the tag name in the Register directive does not match the tag name specified in web.config.

  Posted to Custom Server Controls (Forum) by usp on 2/28/2009

• Re: Why extend the Profile provider it is limiting?

  Thanks for helping me think through this issue. I was initially going to extend MembershipUser since it seemed logical to me that extra user information should be associated with the membership user object. However, in my search I found knowledgeable people saying that extending MembershipUser to include that type of information wasn't a good idea. Enough people recommended against extending MembershipUser that I ruled out that technique and went searching for an alternative. The alternative

  Posted to Web Parts and Personalization (Forum) by usp on 10/2/2008

• Re: Why extend the Profile provider it is limiting?

  All that is needed is to query a user's name from a database and put it into the session scope. This is trivial code anyone can write. The code to extend the profile is rather complex and it requires a good understanding of how the profile works. I have spent many hours researching how to do extend the profile provider and membership user feature and I could have written code to query the database and store the result in a session in much less time. I had been thinking that the only methods to

  Posted to Web Parts and Personalization (Forum) by usp on 10/1/2008

• Why extend the Profile provider it is limiting?

  Storing a user's name is a common problem with the ASP.NET membership and profile model since items in the profile are unqueryable in the database without a lot of effort. There are plenty of examples in books and online of extending the profile provider to use a custom table where every profile property has its own column. Why go through this trouble of trying to morph this feature into something more usable if it isn't meeting my needs? Why not just run a query when people log in and cache

  Posted to Web Parts and Personalization (Forum) by usp on 9/30/2008
  Filed under: profile provider session

• Re: Extend MembershipUser or Profile to add FirstName property?

  From what I have read, about 30% of people recommend extending the MembershipUser and 70% of people recommend extending the Profile provider. A couple people suggested that Membership is only supposed to be used to enforce security while Profile is intended to contain all the user details that are unrelated to security. The above article is the first one I have seen that specifically recommends not extending either and instead direcly querying the database, which is a valid recommendation and it

  Posted to Security (Forum) by usp on 9/30/2008
  Filed under: Membership MembershipUser Profile Provider

• Extend MembershipUser or Profile to add FirstName property?

  I currently store FirstName and LastName for users using the default SQL Server profile provider, and it is difficult to directly query these values in SQL since all the datapoints are stored in a single column. I want to make use of a database table that has FirstName and LastName columns to make it easier to query. To do this, should I extend MembershipUser or the Profile? I'm wondering which method is more correct not which is easier to implement. Thank you. ASP.NET 2.0, SQL Server 2005.

  Posted to Security (Forum) by usp on 9/30/2008

• Re: Granular security design pattern

  Thanks, that is a nice article. When it comes to pulling out data from reports, what I was thinking of was storing a comma list in a session variable with a list of the accounts the user has access to (the number of possible accounts is <30). For every stored procedure I would pass in the list of allowed accounts and I will switch every stored procedure to use dynamic SQL with code like this: IF len(@allowedAccountIds) >0 SET @sql = @sql + ' AND a.accountId IN (' + @allowedAccountIds

  Posted to Security (Forum) by usp on 8/11/2008

• Granular security design pattern

  I would like to add a feature where we can specify user access permission to specific features in the site or to specific types of data. The Web application is established and uses the .NET 2.0 membership provider. It uses reporting services, SqlDataSource controls to populate visible controls, and SQL Server 2005. Scenario: picture an ecommerce site with categories for books and electronics. Some people have access to everything. Another class (role) of people only has access to the book category

  Posted to Security (Forum) by usp on 8/8/2008
  Filed under: security pattern resource

• Session vs Profile performance

  I researched whether to use sessions or profiles to manage persistent user data and the general conclusion I found was that profiles are good if it helps to have the data persist for a long time, otherwise use sessions for performance reasons. Some people suggested caching the profile in the session since the profile is so slow. The information I have never seen is why a profile is so much slower. If sessions are stored InProc the answer is obvious. However, every .NET book I have read says to store

  Posted to State Management (Forum) by usp on 8/8/2008
  Filed under: session profile performance optimization

• Re: How to get acces to Membership.GetUser() from the Login Control

  Does anyone know of a resolution to this question? The GetUser() can be fixed by passing in the username, but I'm also looking at putting variables in the user profile right after login, which seems to have the same issue. I'm looking to cache the UserId in the profile immediately after login to make it easier to use this value in database queries.

  Posted to Security (Forum) by usp on 8/7/2008