Azure Web App deployment fails to build class library project that uses C# 6 features
Upgrading RDLC schema from 2008 to 2010 in Visual Studio 2013
Disclaimer: This worked for me, but as with all undocumented hacks, proceed at your own risk.
There may be a better way to do this, but I couldn’t find it. I trust that your
.rdlcfiles are in source control, and that you can rollback to a previously working version if this causes problems.
For various reasons, I needed to upgrade my RDLC report’s schema version from the default 2008 version to the 2010 version.
Azure WebJob with status "Never Finished"
I was a little confused as to why one of my Azure WebJobs had a status of “Never Finished”:
Ensuring a SQL Server column copies as text to an Excel column
The problem arises when you have a column with character strings that look like numbers. Looking like a number isn’t a problem in and of itself, unless the value starts with the character “0”. Excel will try to treat the column’s values as a number, and therefore eliminate any leading 0s.
Authentication fails with access_denied error while using Microsoft.Owin.Security.Google 3.0.0
Just a quick tip:
If you’re trying to use Google Oauth 2.0 to authenticate users in your MVC 5 application, start with this tutorial:
Enumerating HttpModules: MVC Edition
About 6 years ago, I wrote a post about Enumerating HttpModules in ASP.NET. On my current project, I once again needed to view the loaded HttpModules, but this time in ASP.NET MVC. The code is very similar; it just has some MVC-isms and has been LINQ-ified now.
Here is the relevant code:
CSC : warning CS1685: The predefined type ‘System.Runtime.CompilerServices.ExtensionAttribute’ is defined in multiple assemblies in the global alias
In one of my ASP.NET MVC 5 projects that targets .NET 4.5.1, I noticed that I was getting a new compiler warning at build time:
|
|
Using EFProf and MiniProfiler simultaneously in an ASP.NET MVC 5.1, Entity Framework 5 Code-First Project
We’re already using the excellent Entity Framework Profiler (EFProf) to gauge EF performance in our application. However, we wanted more information about the overall application performance, and thus turned to MiniProfiler.
Unable to start debugging on the web server
If you’re getting this error when trying to debug an ASP.NET Web application on IIS7 or greater, check the system.webServer element in your Web.config. If you have the httpErrors element configured, you won’t be able to debug. For your local dev environment, remove or comment out the httpErrors element, and you should be good to go.