Reusing same connection in signalR while navigating through different pages
I have an MVC project, with multiple pages.
I have an MVC project, with multiple pages.
My goal is to have one data context (MainDbContext) per HTTP request in ASP.NET MVC and dispose the data context when the request ends.
I’m trying to implement the JWT Bearer Authentication in my AspNetCore MVC app (Web API only) using the JwtBearerMiddleware but am getting a 401 response with header:
I want using external logins so I installed Oauth by package manager:
I’m using iTextSharp for generating a pdf. I can save the PDF file from the PDF byte[].
Is is possible to write to the http response stream from a dynamically created bitmap using the Response.Write/WriteFile without saving the image to the hard drive?
I am experiencing a strange issue. I have an ASP.Net web application that uses Forms Authentication. If I open the log-in page and there is a couple of minutes of inactivity, the log-in attempt times out or IE / FireFox display “Cannot display this page”. If there is no pause or lack of activity, there is no issue and the website run as expected.
We are having two load balancing server. In that we have hosted a asp.net 3.5 application right now we are using request userhostaddress to get visitor ip but it is giving load balancer ip instead of real ip. Can anyone have code for this.
I have a form and stored procedure that inserts the data from the form. It works fine except that if a field isn’t filled in it doesn’t insert a NULL into SQL it inserts "".
I am currently storing normalized versions of strings in my SQL Server database in lower case. For example, in my Users table, I have a UserName and a LoweredUserName field. Depending on the context, I either use T-SQL’s LOWER() function or C#’s String.ToLower() method to generate the lower case version of the user name to fill the LoweredUserName field. According to Microsoft’s guidelines and Visual Studio’s code analysis rule CA1308, I should be using C#’s String.ToUpperInvariant() instead of ToLower(). According to Microsoft, this is both a performance and globalization issue: converting to upper case is safe, while converting to lower case can cause a loss of information (for example, the Turkish ‘I’ problem).