Timeline for C# - Creating new SharePoint user in .Net Membership provider
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 16, 2014 at 22:57 | comment | added | Omegacron | I'll see if I can crack the EF way - the way I see it, every new technology I can learn just makes me more valuable as an employee. Plus... bragging rights. | |
| Dec 16, 2014 at 22:53 | comment | added | Derek Gusoff | Probably. I would find a tutorial on EF and see if that's the direction you want to go. If you're more comfortable with ADO.NET or some other data access technology, you can forget the EF stuff and just wire up that stored procedure in the technology of your choice. | |
| Dec 16, 2014 at 22:40 | comment | added | Omegacron | Ah, ok - so if I named my EF model "AppAccountsDB" I would use "AppAccountsDBEntities"? Sorry, I'm new to Entity Framework usage. | |
| Dec 16, 2014 at 22:38 | comment | added | Derek Gusoff | It's the class generated by the Entity Framework wizard. For example, if you create an EF model against the Northwind DB, you'll get a class called "NorthwindEntities". In my case above I named my database "Membership". | |
| Dec 16, 2014 at 19:56 | comment | added | Omegacron | Question: In your top snippet, where is "MembershipEntities" coming from? It doesn't seem to be a method in either System.Web or System.Web.Security, unless I'm looking in the wrong place. Are you manually defining that elsewhere? | |
| Dec 12, 2014 at 22:02 | history | answered | Derek Gusoff | CC BY-SA 3.0 |