Argh, here's the deal: - I've got a Membership-enabled website with sql-managed sessions.. - I've written a webservice that performs some operations against my application's tables (No, not membership-related tables). I used a different website to develop this service and at least this part of it works just fine.
** THE PROBLEM ** - I'd like to able to access Membership, Profiles, and Roles from within the service but the second I throw the service into the application's site, my service-consuming client throws an error about the 'ole "AutoDetectCookies=1" parameter and all web method calls die a horrible death.. So... How can I fix this? Can I exempt the service from playing under membership-based model? Is there some seamless way for a service-client to "login" to successfully complete a web method call? To unsubscribe from this group, send email to dotnetdevelopment+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
