London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
Hi Chris,
Before you upgrade all the way it is probably best to migrate from SQLMembership to Asp.Net Identity and release this before the migration to CMS12 to reduce risk in you approach.
You can see how to migrate from sqlmembership to asp,net identity here .
Either way your going to need to migrate to asp.net identity.
Paul
Hi there
Busy working through upgrading our site to V12.
Have gotten through the worst of it now, but currently on something that I'm struggling to wrap my head around today.
The existing logins that we had in our V11 DB do not work - I have to allow creation of admin account to get in.
In V11 site was using SqlMembershopProvider. There does not appear to be any equivalent in .Net core.
Can't find anything remotely related to this when searching the net including Optimizely's docs, so I'm assuming I'm just missing something simple.
Should the existing logins just work, or is there some change required that I have been unable to find?
Thanks
Chris