ASP.NET Membership with more than 2 million users – any problem(s)?
Will ASP.NET Membership handle a scenario with more than 2 million users? Does anybody have good or bad experiences with (very) large scale use of this provider?
Will ASP.NET Membership handle a scenario with more than 2 million users? Does anybody have good or bad experiences with (very) large scale use of this provider?
I have an existing asp.net webforms application that I would like to add some unit testing to but am unsure of exactly how to go about it.
I know I can use Request.Browser.IsMobileDevice.
I want to create a GridView that displays records for PDF Files. These records can have meta data attached that is customizeable by the user, so they can create their own columns and enter their own information in there. I then want it to be displayed in a GridView, so they can order each column and the column order if the column order is -1 it will not display in the GridView.
I’ve got a form with a FileUpload control where users can upload images. Can I ensure that the file size of the uploaded image is lower than the configured maxRequestLength before the upload occurs, and by doing so prevent an exception from being thrown when file size is too large?
When using SharePoint DLLs (which are x86 only) from a non-ASP.NET app, you can set the “Platform target” to x86 (instead of “Any CPU”) so both Visual Studio 2010 and the app load the SharePoint assemblies fine.
I’m using Forms authentication and I would like to make use of roles, can I somehow set the role of the user without Membership ?
I have a view which contains a users id and an image column.
I have a code behind page that has several method; one of them is a page method.
This question is related to this, hopefully better phrased.