So you’ve run the scripts to install the Oracle Providers for ASP.NET. You’ve verified that scripts executed without error. But no matter what you try, the code does not seem to use the OracleMembershipProvider.
You’ll quickly notice that the convenience overloads of Membership methods, implemented as extension methods, have not been implemented.
Make sure that the v4 provider dll has been installed into the Global Assembly Cache (via OraProvCfg).
OracleMembershipProvider does not have a static method for constructing new instances (use new OracleMembershipProvider()).
The default constructor does not initialize the object with the settings specified in the application config file. To read those settings call provider.Initialize() with the name you gave the oracle provider in app.config and a non-readonly NameValueCollection containing the membership settings.
But how do we get such a NameValueCollection? Using ConfigurationManager.AppSettings causes an exception indicating that the collection is read-only.