Hey all,
I'm a bit confused guys... Noticed they changed the membership stuff for
MVC websites so did some reading and found the new stuff is called
SimpleMembership. But then I find there's something else called Asp.Net
Identity which works with Azure and AD.
So now I've no idea which I should
I did a bit of research into standing desks, motivated by the health concerns
that Jason mentions (which are pretty worrying actually).
TL;DR - stability is everything.
I ended up just getting a fixed height bar table for home (105cm height), which
is fine given I only use it during the
Hi Stephen,
I have done a fair bit of reading about asp.net Identity over the last 6 months
and have currently implemented it in a few projects.
It can be as complicated or as simple as you want it but I guess there is a lot
to learn when starting from scratch and you are not sure what you are
Thanks, will check those out.
I eventually found a good article explaining the history of each and turns
out this project already is using it. I do have another that I need to
upgrade at some stage.
It comes down to when you created it (and which was in the template you
used at the time)
Sent
Is it a coincidence that my November 2014 issue of Scientific American just
arrived with dense article (pp 19-20) titled *Killer Chairs*? Author James
Levine's sub-title text says Standing more, even at a desk job, could
lower risk for obesity, illness and death, studies suggest. However, the
The bare bare minimum.
http://www.khalidabuhakmeh.com/asp-net-mvc-5-authentication-breakdown-part-deux
This is good thanks! I detest bloated generated code and always like to
know how to strip it down to the minimum required.
I also followed your link to storing passwords because
Also the linq-to-llblgen provider was - at least in it's first incarnation -
not actually very good. You would constantly come up against unsupported
operators, which again just goes to show what a significant effort writing a
linq provider is.
(As an aside, there is also the LinqToAzure
