What happens if you have a custom membership provider that's working fine, but the custom roles provider which goes with it is broken?

Can users log in like normal except that everyone has the same access rights?
Can you access their data in the membership table?
Or are roles required for membership to function?

What would be your recommended approach: deploy the basic functionality, build my own roles provider and use that instead? Or am I screwed and need to wait however many months it takes these guys to solve the problem and release a new version?

__________________
-------------------------

Whatever you can do or dream you can, begin it. Boldness has genius, power and magic in it. Begin it now.
-Johann von Goethe

When Two Hearts Race... Both Win.
-Dove Chocolate Wrapper

Chroniclemaster1, Founder of www.EarthChronicle.com
A Growing History of our Planet, by our Planet, for our Planet.

You don't need roles to use Membership. They work together, but they actually use seperate providers and APIs.

This means that you could use a custom Membership provider with the out-of-the-box AspNetSqlRoleProvider, if you put the correct schema / sprocs in place for that.

__________________
Visit my blog at http://leedumond.com
Follow me on Twitter: http://twitter.com/LeeDumond

Thanks Lee!

I knew they were separate providers, but I didn't want to spend a couple weeks trying to get a login system working only to query the forum and hear "Oh yeah, it won't work without that."

I will see what I can pull together on my own then.

__________________
-------------------------

Whatever you can do or dream you can, begin it. Boldness has genius, power and magic in it. Begin it now.
-Johann von Goethe

When Two Hearts Race... Both Win.
-Dove Chocolate Wrapper

Chroniclemaster1, Founder of www.EarthChronicle.com
A Growing History of our Planet, by our Planet, for our Planet.