I had an issue one day where Visual Studio would not open my CSHTML files. It would give me the following error.
The operation could not be completed. Invalid pointer.
So naturally I took to Bing. I eventually found the work around on StackOverFlow.
The fix for me was not the question’s accepted answer but one further down. I deleted the contents in the %LocalAppData%\Microsoft\VisualStudio\14.0\ComponentModelCache folder.
After that I never had this issue again.
Recently I had a need to allow users to change their login on an MVC site that used Windows authentication. Of course we did not want the user to log out of their machine to do it. The trick of course involved sending a 401 response, but how to do that and not get stuck in an endless loop.
The 401 Loop
It seemed simple enough, in fact too simple. You just return a 401 challenge and have them move on to their previous page. The 401 response is what presents the user with the Windows login popup. In reality the 401 response acts like a redirect on itself, so you get two page loads and it forgets any variables you set.
Well that simply would not do. Read the rest of this entry
Angular 2 And Visual Studio 2015?
I want to start learning Angular 2! We have an enterprise project that will be developed in Angular 2. In fact the contracting firm will create a minimum viable product and then it will be up to us to do the rest. So I really must learn Angular 2. We also use Visual Studio 2015 Enterprise edition. Most of our current projects target .NET 4.
If you have looked into Angular 2 just a bit you will find a huge difference. Most people are teaching it using Code or some other IDE that is not Visual Studio. So my goal in this post is to take the 5 Min Quickstart from Angular 2 and make it run in Visual Studio 2015.
I will not go into detail on every bit, please see the Quickstart for that information. I am just focusing on getting it running in Visual Studio 2015.
The Art of Logging
During my time as a Naval Nuclear Field Machinist Mate I did a lot of logging. The data points we logged were not for busy work, they had a reason and a purpose.
Logging certain data points around the same time multiple times a day is a lot of data. As you know this data lets you see trends, maybe detect a potential equipment failure before it happens.
Application logging in the enterprise is not much different. The hard part is knowing what to log, where to log, and how to log it. I hope this article will help you answer some of those questions.
I really must apologize for waiting so long to post about this conference. It just kept slipping my mind. My team and I attended one in Orlando last year (2015). If you have never been to a large developer conference you are really missing out on some goodness.
This conference was my first real one I have attended. I thoroughly enjoyed it, and would love to attend it again. This year though, I am shooting for Microsoft Ignite.
We have all used the magic of the Web.config transformations. This is when we have our Web.config and connected to that is a version that does some work for release and one for debug; Web.Release.config and Web.Debug.config. These are a great way to automatically have the correct target use the correct settings, especially connection strings. Whether we use that or not and just leave it as something that looks cool is a different thing.
Did you know you can get this magic for your console applications as well? I know, a web developer doing console apps? As an enterprise one sometimes I find it is the best solution to some problems. While it seems like a small thing I wished I had it in the console applications, I am happy to say that I have found it!
Recently I was working on an older project. Nothing too big, just a really old Windows Service that consumed another third party SOAP web service. I finally had the chance to do something we don’t get to do in the enterprise, improve old code without a user request due something broken or needing a new feature. Yes for those that don’t know, if it isn’t broke you don’t fix it.
Working on this project I had become fixated on implementing something in a way that just could not be done. Because I was so focused on the one path I could not see what was plain and simple in front of my face. Little did I know I was on the Road to Nowhere.