If you are using Windows 8 and you need to run Visual Studio as Administrator, you could always Right Click on the shortcut, then right click on the Visual Studio icon and then select Run As Administrator. But do you really want to do this each and every time you need to run Visual Studio?
Visual Studio 2012 has a quirk that many users despise. The Uppercase menu. Now personally I don’t mind it, but some developers simply hate it. Unfortunately, it’s not an option you can just enable or disable. Fortunately, there are people out there that have a solution for this (See Reference below).
Before we continue, the solution involves editing the registry. Modifying the registry can cause problems or unexpected results, so continue at your own risk. (Seeing as the intended audience will probably be developers, I guess you have no qualms with modifying the registry). Now that this warning is out of the way, let’s continue.
The PowerPoint Add-In for Visual Studio Premium and Ultimate users is a great tool to quickly create interface designs that you can provide to your customers. This in turn allows you to gain valuable feedback from them because you can make these designs interactive.
What is even better is that, because it is PowerPoint, your customers can change elements on the form to illustrate exactly what they mean. To start using PowerPoint Storyboarding, head on over to your Windows 8 Search. (Windows Key + C to activate the Charm Bar and select Search)
As you type “PowerPoint Storyboarding” into the search field, the results will filter until you can select the application from the search results.
Recently I have had to call a .NET Dll from a VBScript. Why would I need to do this I hear you ask? Well sometimes it is easier to do certain things in .NET or you might have previously written functionality in a .NET DLL that you now need to duplicate in the VBScript. That was what I was faced with. I didn’t want to have to re-write code, and I make no excuses for being lazy. So I decided to try and find a way to call a .NET DLL from a VBScript.
This turned out to be much easier than I had initially thought. In order to illustrate this, fire up Visual Studio and create a new Class Library Project.