When to use built in ASP.NET login control
might be a dumb question but since i am so new with ASP.NET i have a hard time understanding when you should use for example the built in login controller, vs. a custom login-form with custom code-behind? Coming from PHP and this is why i cant seem to get a grip on this, same about the ASP.NET SiteMapPath with a menu controller vs. just using a href or asp:HyperLink?
If the login control suits your needs, use it, after all it's tested, secure, standardised (so hopefully easily maintained). If you don't have any exotic requirements go with it. It's pretty flexible. On a tangent, if you're new to asp.net but not tied to it, I'd highly recommend MVC instead.
convert group by query to linq
How to give user an equivalent Excel-VBA environment for my application in C#
How to return type as a result of method execution
How to download infinitely-scrolling web page
How to execute asynchronously three separate queries in one method using ADO.NET ExecuteScalarAsync()
How to make a wall jump in Unity 2d?
What is the optimized way of finding count? LINQ or foreach? [duplicate]
How do I dynamically turn animations on and off in a Telerik RadTreeView under Silverlight?
Reinstallation of windows service
How to get output from SQL Server Insert Command with more than one row using C# ADO.Net?
Data conversion failed. [ OLE DB status value (if known) = 2 ]
ASP.NET MVC one particular view model property becoming null on returning to view
Getting Data from MicroSoftVisualBasic Collection
How can I remove duplicate, invalid, child nodes from an XML document using Linq to XML?
Flyout alternative Windows Phone 8.0
How to Construct IdentityResult With Success == true