Category Archives: Visual Studio
Package management initialization failed: Access Denied
I encountered this error for the first time today on my work laptop. This seemed like a really odd error to receive especially since I had been using it last week.
There is an easy work around for it, or at least my version of it.
There is a file called privateregistry.bin located in C:\Users\username\AppData\Local\Microsoft\VisualStudio\15.0_someidentifier
You could be brave and just delete it, I was cautious and renamed it. You may lose your personal settings, but you’ll be able to use 2017 again.
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.
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.
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!
I have to admit I was wrong about the significance of the new Window Layout functionality in Visual Studio 2015. As it turns out I really have been using this feature.
Today while using Visual Studio 2015 CTP 6 I encountered a problem. It kept crashing. I know earlier today I had installed several extensions; two of which did not come from Microsoft or Microsoft employees. Naturally I suspected some extensions.
Command Line to the rescue. You simply start Visual Studio from the command line with the flag to start in safe mode. Once it comes up you can remove those suspect extensions.
I know we have intellisense in Visual Studio 2013 for the break point Condition, but we do not have it for the Action. I was toying around with 2015 and noticed we now have it for the Action as well.
This is very useful for creating output messages to the debugger window. In the screen shot below I have an object called myObject. This object has three properties, an Id, a Name, and a CreatedDate.