I’m now a Microsoft Certified Professional!

Microsoft_Certified_ProfessionalFor the past few weeks, I’ve been hard at work studying for my Microsoft Certified Technology Specialist exam (70-573) – Microsoft SharePoint 2010, Application Development.

 

Well, today, I took the exam and am pleased to report that I passed!

 

Not only did I achieve the pass rate (which is 70%) but aced the thing and got 100% !  Needless to say, I’m thrilled to bits.

 

MCTS_logoSince this is my first Microsoft exam, I’m still awaiting emails and communication from Microsoft regarding my MCP ID, Transcript and Certificate (which I’m lead to believe you now have to print out for yourself!) but I do have the Transcript print-out that the Prometric test centre provide immediately after completing the exam.

 

Looks like I’ll have to dig out a frame for my print-out until I can get my hands on the actual certificate!  Smile

 

It’s really strange in many ways, as most developers seem to try to acquire certification earlier in their career, primarily to make up for the lack of experience when you’re first starting out.  I’ve done it the other way around.  Despite having nearly 20 years hands-on experience as a software developer, I’m only just now getting an industry recognized certification!

 

Ah well, better late than never, and I must admit it does feel good.  In many ways, it’s like going back 20-odd years and being back at school again.  The reality, though, is that this is probably my mid-life crisis!  Smile 

 

I’m not stopping here, though.  The next step is to get my head back into the books in preparation for the follow-up exam, which will give me Microsoft Certified Professional Developer (MCPD) status!  That’s exam 70-576 - Designing and Developing Microsoft SharePoint 2010 Applications.

 

Onwards and upwards!   Wish me luck!

Run As Administrator Keyboard Shortcut

Really short and sweet this one, but a very handy tip nonetheless, and something I simply did not know about until a couple of days ago.

 

imageYou may be aware that you can run a given program with escalated privileges with the “Run As Administrator” command on the Windows Explorer Context Menu, invoked with the Right-Mouse button and as shown in the picture on the right, but did you know you can achieve the same thing with a keyboard shortcut ?

 

It’s really simple.  Prior to clicking on the program link or shortcut, simply hold down:

 

image + image

and then left-click as normal.  Voila, you’re now running as administrator!

JavaScript IntelliSense in Razor Views

There’s an issue with getting JavaScript IntelliSense to display in a Razor view of an ASP.NET MVC project.

 

Turns out that despite having the JavaScript file corrected referenced within your _Layout.cshtml (or some other “global” location) like so:

<head>
    <meta charset="utf-8" />
    <title>@ViewBag.Title</title>
    <link href="@Url.Content("~/Content/Site.css")" rel="stylesheet" type="text/css" />
    <script src="@Url.Content("~/Scripts/jquery-1.6.2.min.js")" type="text/javascript"></script>
    @RenderSection("HeadContent", required: true)
</head>

 

The Visual Studio IDE won’t recognise or parse the:

<script src="@Url.Content("~/Scripts/jquery-1.6.2.min.js")" type="text/javascript"></script>

line when you’re working inside other views within your project.

 

There’s a hacky workaround for this, though.  You have to reference the JavaScript file from within the view that you’re currently working in.  Although this seems counter-intuitive, and you certainly don’t want a doubly-referenced script as part of your actual solution code, you can place this “dummy” reference in a conditional block of code that will never be reached when your solution is running:

@* Stupid hack to get jQuery intellisense to work in the VS2010 IDE! *@
@if (false)
{
   <script src="../../Scripts/jquery-1.6.2-vsdoc.js" type="text/javascript"></script>
}

The if (false) conditional ensures that, when this code is running, the script reference will never be output to the page as the conditional will never evaluate to false (it’ll always evaluate to true).  Despite this, when you’re working in the Visual Studio IDE, the script reference will be parsed and the relevant JavaScript file included (in this case a vsdoc.js file containing the IntelliSense information for jQuery 1.6.2).  This is because the IDE doesn’t care that this script reference code is effectively unreachable, and will happily parse the entire code block anyway!