About

I'm Mike Pope. I live in the Seattle area. I've been a technical writer and editor for over 30 years. I'm interested in software, language, music, movies, books, motorcycles, travel, and ... well, lots of stuff.

Read more ...

Blog Search


(Supports AND)

Google Ads

Feed

Subscribe to the RSS feed for this blog.

See this post for info on full versus truncated feeds.

Quote

One of my greatest anxieties in life is the possibility of being at the mercy of a man less intelligent than me, yet highly skilled in an arena of which I have no knowledge.

— J. Robert Lennon



Navigation





<November 2017>
SMTWTFS
2930311234
567891011
12131415161718
19202122232425
262728293012
3456789

Categories

  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  

Contact

Email me

Blog Statistics

Dates
First entry - 6/27/2003
Most recent entry - 11/17/2017

Totals
Posts - 2460
Comments - 2563
Hits - 1,999,326

Averages
Entries/day - 0.47
Comments/entry - 1.04
Hits/day - 380

Updated every 30 minutes. Last: 8:04 PM Pacific


  10:23 PM

If you use membership in ASP.NET Web Pages, you might get the error To call this method, the "Membership.Provider" property must be an instance of "ExtendedMembershipProvider":


I happened to run across this while playing around with the new OAuth login capabilities in the beta version of Web Pages 2, but you might see it under other conditions as well.

Per one of our testers, this can indicate that the server has no AspNetSqlMembershipProvider configured. (A clue here is that everything works great when you test locally, but then throws an error when you deploy to your hosting provider.)

In my case, I fixed this by adding the following to the site's local Web.config file:

<appSettings>
<add key="enableSimpleMembership" value="true" />
</appSettings>
This is a child of the <configuration> element and a peer of the <system.web> element.

Anyway, that worked for me. I'm curious if others have seen this error and if so, how they fixed it.

[categories]   ,

[4] |