Anthony's Blog

If you haven't yet switch to using Access Tokens for your repo clone. Enable your  Two-Factor Authentication and create an access token under your profile. I've done this with my gitlab and keep forgetting the quick way to update the path/command. Go to https:/// YOURGITLAB.com/ profile/two_factor_auth Then go to  https:// / YOURGITLAB.com/ profile/personal_access_tokens  create a token with the api setting. Now switching your remote url for your git is simple. Using this command.. git remote set-url origin http://USER:TOKEN@YOURGITLAB.com/repo.git If you have multiple origin urls you might have to remove them and add back an origin upstream and reset the origin master as the default upstream. This doesn't normally happen but I had a unique case where I had multiple urls for the origin where I was pushing to multiple repos for the same code. This probably won't be your case but I figure I might add this bit in.

    Currently updating an application from Asp.net MVC 4.0 to MVC 5.0 but before I update MVC I wanted to update the Razor package. Since the MVC package is dependent on the Razor. So this article is about Razor 2 to Razor 3 and the problems I faced. Razor in my opinion Razor 3.0 (details in the link) is an awesome package in my opinion and I shudder to think anyone who writes Asp.net MVC applications using ASPX. For me the Razor syntax is an effective way to write visually clean code and because of this provide very low maintenance. Issues with Razor Updating from 2.0 to 3.0 As I updated I encounter numerous problem with the Razor package from 2.0 to 3.o and not only did it break my application but destroyed the Intellisense for Razor (mostly for ViewBags). So for my first problem... Inheritance security rules violated by type: 'System.Web.WebPages.Razor.WebPageRazorHost'. Derived types must either match the security accessibility of the base type or be less...

    Stumbled across this bad boy in the webconfig in an old project and was curious what it's purpose was. Since the comments didn't really help and I spent some time on to uncover its secrets. "This prevents the Windows Event Log from logging the  HMAC 1 that is being used (when  the other party needs it).When targeting ASP.NET MVC 3, this assemblyBinding makes MVC 1 and 2 references relink to MVC 3 so libraries such as DotNetOpenAuth that compile against MVC1." T he comments don't really help, in fact only rises more quesitions. Why is the DontNetOpenAuth ever compiling against MVC1? DotNetOpenAuth with MVC 4.0  - " Yes, DNOA is built against MVC 1.0, and this is by design so that it works against all versions of MVC (given the appropriate redirects). This is purely an M...