When you go from Visual Studio Code, and step into Visual Studio Code – Insiders however, you will quite fast experience that you no longer can simply type code .\ from the command line to start developing. This is because Microsoft is nice enough to ensure that you can co-run these two together, and the command would actually be code-insiders .\

To solve this, you simply have to copy two files and rename them to code.

Note! This will break the coexisted experience between VS Code and VS Code – Insiders.

Let’s step trough them

1. 1. Browse to the path where you have installed Visual Studio Code – Insider. Default path is C:\Program Files\Microsoft VS Code Insiders\bin.
   2. Copy code-insiders and code-insiders.cmd and paste them back in the same folder.
   3. Rename both copied files to simply code and code.cmd

That’s it. You can now start Visual Studio Code – Insiders from the command line just as you’re used to.

The rescue squad in this case is something called Enterprise Mode
https://technet.microsoft.com/en-us/itpro/microsoft-edge/emie-to-improve-compatibility

Configuring the Enterprise Mode list is quite straight forward when using the Enterprise Mode Site List Manager, so I won’t cover that one in this post.

The next step after getting the configuration right, is to make it available for all clients, and what’s better than a server less infrastructure to handle that part.

In this case I’ve chosen to host the file in a Azure Storage Account, which makes it highly available with a decent SLA, and it’s really fast to get started if you have a Azure Subscription.

1. Start by creating an Azure Storage Account in a datacenter near you.
2. Create a container, and set the Access type to Blob
3. Upload your generated XML file.

There is just one caveat that I want to highlight. That’s the Cache-Control of your blob. If you don’t remove that one, the file will be cached on the client and it takes time to get new configuration rolled out.

Luckily, solving it is simple. Open Microsoft Azure Storage Explorer, browse to the file you have uploaded, and edit the Properties. In the CacheControl field, add “public, no-cache” , and click Save.

This ensures that the file isn’t cached on the client, and therefor also updated fast when you change it. For details on how to configure the perfect CacheControl for your environment, have a look at the following document: https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9

If you ever wonder where to find them, they are all available from the Details Window for your registered devices in the Azure AD Management Portal.

A few easy steps to get there

1. Open Azure AD in the Management Portal
   https://manage.windowsazure.com
2. Open the Users tab and search/browse for the account you need to find recovery key for, then open it.
3. Go to the Devices tab, and in the View box, select Devices.
4. Select the affected device, and click View Details.
   All registered keys should be visible

The case

We have multiple countries with the same HR system each (Same system, but different databases). In all countries’ databases, the employee number stated on 10001. To solve this, we chose to prefix the employee number upon import. This isn’t a big deal, but it’s a bit more tricky when we need to make sure that a join is successful.

Solution

Not that tricky, but it takes time if you don’t know where to start, right?

As we have chosen to use Employee ID as the linked attribute, we decided to use this attribute for joining also. Why make it more complicated than we need to?

To begin, create a Management Agent Extension, and add the following Join rules there

void IMASynchronization.MapAttributesForJoin(string FlowRuleName, CSEntry csentry, ref ValueCollection values)
{
    switch (FlowRuleName)
    {
        case "JoinEmployeeID":
            if ((csentry["employeeID"] != null) || (csentry["employeeID"].StringValue != ""))
            {
                String emloyeeIdWithPrefix = "NO" + csentry["employeeID"].StringValue;
                values.Add(emloyeeIdWithPrefix);
            }
            else
            {
                throw new Exception(String.Format("EmployeeID can't be blank!"));
            }
            break;
        default:
            throw new EntryPointNotImplementedException();
    }
}

Then configure the following join rules on the Management Agent

Thanks, and hope this could help someone else also

After skimming over the agenda, I see that not all of them are just for hard core developers. There is actually quite a few sessions that at least I find extra interesting. Below you can see the session I will be following, not all will be live, but hopefully most of them will be available on demand later on

• Keynote Presentation
  https://channel9.msdn.com/Events/Build/2016/KEY01
• To Be Announced
  https://channel9.msdn.com/Events/Build/2016/C901
• Microsoft Research Presentation
  https://channel9.msdn.com/Events/Build/2016/B821
• Designing Hybrid Applications that Span Azure and Azure Stack
  https://channel9.msdn.com/Events/Build/2016/B843
• Enabling DevOps for Every Team
  https://channel9.msdn.com/Events/Build/2016/B845
• IoT Development 1: Intro to Windows 10 IoT Core on Raspberry Pi 3
  https://channel9.msdn.com/Events/Build/2016/L714-R1
• Windows in the Enterprise
  https://channel9.msdn.com/Events/Build/2016/B850
• Building Applications Using the Azure Container Service
  https://channel9.msdn.com/Events/Build/2016/B822
• Microsoft Identity: State of the Union and Future Direction
  https://channel9.msdn.com/Events/Build/2016/B868
• Introducing: NEW Options for PaaS Development
  https://channel9.msdn.com/Events/Build/2016/B858
• Enterprise Apps and the Windows Store for Business
  https://channel9.msdn.com/Events/Build/2016/B851
• Mark Russinovich Live
  https://channel9.msdn.com/Events/Build/2016/C918
• Windows Advance Threat Protection Service
  https://channel9.msdn.com/Events/Build/2016/B890
• Windows Store: Publishing Apps and Games to Desktop, Mobile, and Xbox
  https://channel9.msdn.com/Events/Build/2016/B839
• DevOps and Visual Studio Team Services
  https://channel9.msdn.com/Events/Build/2016/C921
• Close of Build
  https://channel9.msdn.com/Events/Build/2016/C926

For a complete list of all Channel9 live session, check this filter at channel9.msdn.com
https://channel9.msdn.com/Events/Build/2016?y=Channel%209%20Live

Join me watching these videos, and lets prepare for Ignite 2016 later this year

Please find my slide deck at https://doc.co/wW8sFv

A few Bing searches later, and AutoHotkey is my new favorite tool. It allows us to write scripts that executes based on, well, hotkeys. Another quick search teached me that the Top button sends keystroke F19 and F20. Double-click is F19 and a single click is F20.

After some minutes with the AutoHotkey Help document the following script was born

#NoEnv  ; Recommended for performance and compatibility with future AutoHotkey releases.
; #Warn  ; Enable warnings to assist with detecting common errors.
SendMode Input  ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir%  ; Ensures a consistent starting directory.

#IfWinActive ahk_class screenClass
#F20::
  Send, {Right}
Return

#F19::
  Send, {Left}
Return

Thanks to the #IfWinActive line, the pen also works as it’s suposed to do while not presenting.

That’s it. Now I’m able to go forward and backward in a presentation by clicking the Surface Pen Top button. A few tests shows that the range is up to about 10 meters, so most stages should be covered.

To get started yourseft, please make http://www.autohotkey.com/ a visit

They can all be downloaded in PDF format at http://1drv.ms/1QnvxbV

If you want the PPTX format, please feel free to contact me and I’ll send them to you

The view allows you to browse resources much in the same way as the current Management Portal, but in a more “modern” view, if I can say so.

As you can see from the image below, we are able to search, select subscription and choose what columns we want to see.

Another great tip is to pin this blade to the dashboard, and let it use 4×6 tiles.

To do so follow these simple steps

1. Click Browse everything
2. Click the Pin up in the right corner
3. Left click the dashboard, and select customize
4. Move the blade to you location of choice, and select 4×6 as the size.

Update:

Also note that subscription and name filtering are available on all other blades as well. Perfect when you have multiple subscription connected with the same Azure Active Directory. When we choose a subscription where, it’s also “sticky” so when browsing to another blade, your section will be remembered.

Happy Azure time

The most probable reason for this is that there is no Local Networks configured in the subscription where you created the new Virtual Network.

Try browsing to New, Network Services, Virtual Network, All Local Network, and create a new one for the subscription where you need it. Then go back to the Virtual Network Configuration tab and you should see the create a site-to-site connectivity option.