How to use non-thread-safe async/await APIs and patterns with ASP.NET Web API?
This question has been triggered by EF Data Context – Async/Await & Multithreading. I’ve answered that one, but haven’t provided any ultimate solution.
This question has been triggered by EF Data Context – Async/Await & Multithreading. I’ve answered that one, but haven’t provided any ultimate solution.
When creating a new ASP.NET application in Visual Studio, a couple of files and folders are created automatically. One of those folders is called App_Data.
Based on this question here and using code found here I’m trying to load views that are embedded resources in a separate DLL project, and the original question’s author says he has had success doing this – but I can’t get it to work as it seems the MVC view engine is intercepting the request and still looking at the file system for the view. Exception:
When I use Response.Redirect(…) to redirect my form to a new page I get the error:
Is the only difference between the RegisterStartupScript and the RegisterClientScriptBlock is that RegisterStartupScript puts the javascript before the closing </form> tag of the page and RegisterClientScriptBlock puts it right after the starting <form> tag of the page?
I want to change sql connection string in controller, not in ApplicationDbContext. I’m using Asp.Net Core and Entity Framework Core.
I have a requirement to implement an “Unsaved Changes” prompt in an ASP .Net application. If a user modifies controls on a web form, and attempts to navigate away before saving, a prompt should appear warning them that they have unsaved changes, and give them the option to cancel and stay on the current page. The prompt should not display if the user hasn’t touched any of the controls.
The best explanation I’ve found for a postBack is from Wiki.
Can ASP.Net routing (not MVC) be used to serve static files?
Is it possible to authenticate users across sub-domains when the authentication takes place at a sub-domain instead of the parent domain?