asp.net-profiles

问题 I have an existing MVC 4 application that uses the AspNetSqlProfileProvider, configured like this: <properties> <add name="MyTypeAs" type="System.Collections.Generic.List`1[[My.Namespace.MyTypeA, My.Namespace, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]]" serializeAs="Binary" /> </properties> Now I wish to update the system (without removing the old profiles) like this: <properties> <add name="MyTypeAs" type="System.Collections.Generic.List`1[[My.Namespace.MyTypeA, My.Namespace,

问题 I recently asked this question How to persist anon user selection (ex: theme selection). and started to learn about ASP.NET profiles and their properties in the web config. I tried the answer from the link but i was unable to access profile.newproperty How to assign Profile values? This question specifies that web-applications don't support profile out of the box and a custom model based on ProfileBase must be created. The question was answered in 2009 and I wanted to know if this is still

问题 I'm trying to figure out exactly when the event Profile_MigrateAnonymous fires. My best guess from just tracing through my code is that it fires when it detects BOTH an anonymous membership cookie AND an authenticated membership cookie. Can anyone confirm this? I'm looking for real in depth answer here. Not just it gets called 'when a user logs in'. Now - why do I care? I was trying to keep the anonymous profile hanging around after a user had authenticated so that once they log out I'd still

问题 I'm trying to figure out exactly when the event Profile_MigrateAnonymous fires. My best guess from just tracing through my code is that it fires when it detects BOTH an anonymous membership cookie AND an authenticated membership cookie. Can anyone confirm this? I'm looking for real in depth answer here. Not just it gets called 'when a user logs in'. Now - why do I care? I was trying to keep the anonymous profile hanging around after a user had authenticated so that once they log out I'd still

问题 I discovered ASP.NET profiles a few years back and found it quick and easy to implement some powerful functionality in my web site. I ended up exclusively using "anonymous" profile properties because I am NOT using ASP.NET membership and wanted to track information and provide personalization for my site's users even though they weren't logged in. Fast forward 3 years and now I am struggling with keeping the size of my aspnetdb database within the 3 GB limit of my hosting provider. I decided

问题 we often use session, cache and profile in asp.net webform project. we often store data in session, cache and profile in asp.net webform project but i like to know when we should store data in session or when we should store in cache and profile. what is the scope of cache or profile. this two also session specific life time or application specific. suppose if i store any data in cache or profile from session 1 then can i access that data from session2 or not. just guide me with scenario &

问题 I am using the Profile feature of ASP.NET in a website. Updating a profile is working weirdly! A user can't update his/her own profile, neither the web site user nor the administrator, but, the administrator is able to update profiles of other users. In the backend, after Profile's save() is called, SQL Server traces show that aspnet_Profile_SetProperties stored procedure is called twice. First, with new values, then, with old values. The second execution is done after page unload. My code

问题 On my site when a user logs I create a session object with the following properties DisplayName, Email, MemberId Questions Would it make more sense to use a custom profile provider for holding user data? What are the pro's and con's of each approach (Session and custom profile provider)? Does it make sense to use a custom provider for read only data that can come from one or more tables? 回答1: My answer is not direct approach to your question. It is just an alternative approach. Instead of

问题 I am using ASP.NET profiles with allowAnonymous="true". I am NOT using ASP.NET membership. I recently took a hard look at the aspnetdb database and noticed that although my site gets 600-800 unique visitors daily, there are 4000-5000 "users" being created in the database. Clearly what is happening here is the users with cookies disabled end up creating a record for every request. My question: How do I prevent user and profile database records from being created if the client doesn't support

问题 I have an asp.net project and I am trying to develop the user profile part, so that users can log in with their own profile (profile containing admin and users). Is it okay to set a cookie on users computer, when the user is logged in and then let the user browse in site? I mean after after I check user name and password, by checking this cookie on every page I let the user browse the page or redirect to the login page. Is this way okay? Is this safe to use? Is there any better approach for