<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="www.w3.org/2005/Atom" xmlns:sy="purl.org/rss/1.0/modules/syndication/" xmlns:dc="purl.org/dc/elements/1.1/" xmlns:content="purl.org/rss/1.0/modules/content/" xmlns:wfw="wellformedweb.org/CommentAPI/" xmlns:slash="purl.org/rss/1.0/modules/slash/"
  version="2.0">
  <channel>
    <title>dai</title>
    <atom:link
      href="https://docs.microsoft.com/archive/blogs/dai/feed.xml"
      rel="self"
      type="application/rss+xml" />
    <link>https://docs.microsoft.com/archive/blogs/dai/feed.xml</link>
    <description />
    <lastBuildDate>Wed, 17 Apr 2019 03:48:50 GMT</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>Customize the background colour of Office 2010 tiles on the Start screen</title>
      <link>https://docs.microsoft.com/archive/blogs/dai/customize-the-background-colour-of-office-2010-tiles-on-the-start-screen</link>
      <pubDate>Sun, 05 Apr 2015 16:21:00 GMT</pubDate>
      <dc:creator><![CDATA[Ḋai]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/dai/2015/04/05/customize-the-background-colour-of-office-2010-tiles-on-the-start-screen/</guid>
      <description><![CDATA[Did you know on Windows 8.1 you can customize the Start screen tiles for any shortcut to an...]]></description>
      <content:encoded><![CDATA[Did you know on Windows 8.1 you can customize the Start screen tiles for any shortcut to an executable (.exe) file? It's true!

<p>Here is what the Office 2010 tiles look like normally:</p>

<p><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/63/75/8664.2015-04-05-Before.png" original-url="blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-63-75/8664.2015_2D00_04_2D00_05_2D00_Before.png" alt="Screenshot of Office 2010 tiles" /></p>

<p>If you're like me and cling to Office 2010 but find the Windows-generated tile background colours distracting or too bright, you can customise the colours using a simple trick so they look like the screenshot below. Note you can change the background colour to anything you want, and also override the icon images too.</p>

<p><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/63/75/4657.2015-04-05-After.png" original-url="blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-63-75/4657.2015_2D00_04_2D00_05_2D00_After.png" alt="Screenshot of Office 2010 tiles after customizing them" /></p>

<p>Here's how:</p>

<ol>
<li>Create a new folder somewhere, such as your desktop.</li>
<li>Create a new empty XML file (e.g. New &gt; New Text Document then change the filename extension to .xml)</li>
<li>Rename the file to <kbd>winword.visualelementsmanifest.xml</kbd> (don't forget to uncheck "Hide extensions for known file types" in Folder Optjons!).</li>
<li>Open the file in Notepad or another text editor</li>
<li>Paste this into the file:
<pre>
&lt;Application xmlns:xsi=&quot;www.w3.org/2001/XMLSchema-instance&quot;&gt;
    &lt;VisualElements
        BackgroundColor=&quot;#323232&quot;
        ShowNameOnSquare150x150Logo=&quot;on&quot;
        ForegroundText=&quot;light&quot;/&gt;
&lt;/Application&gt;
</pre>
</li>
<li>Save and close the file.</li>
<li>Duplicate (copy and paste) the file for each Office program shortcut and rename them according to this list:
<ul>
<li><kbd>communicator.visualelementsmanifest.xml</kbd> (Lync) </li>
<li><kbd>excel.visualelementsmanifest.xml</kbd> (Excel) </li>
<li><kbd>infopath.visualelementsmanifest.xml</kbd> (InfoPath Designer and Filler) </li>
<li><kbd>msaccess.visualelementsmanifest.xml</kbd> (Access) </li>
<li><kbd>mspub.visualelementsmanifest.xml</kbd> (Publisher) </li>
<li><kbd>onenote.visualelementsmanifest.xml</kbd> (OneNote) </li>
<li><kbd>outlook.visualelementsmanifest.xml</kbd> (Outlook) </li>
<li><kbd>powerpnt.visualelementsmanifest.xml</kbd> (PowerPoint) </li>
<li><kbd>visio.visualelementsmanifest.xml</kbd> (Visio) </li>
<li><kbd>winproj.visualelementsmanifest.xml</kbd> (Project) </li>
<li><kbd>winword.visualelementsmanifest.xml</kbd> (Word) </li>
</ul>
</li>
<li>Cut and paste all of these files into your Office14 folder where the Office .exe files are. This will be a location similar to <kbd>C:\Program Files\Microsoft Office\Office14</kbd> (or "Program Files (x86)"). For Lync, the folder is <kbd>C:\Program Files\Microsoft Lync</kbd> rather than Office14.</li>
<li>Your Start Screen tiles won't look any different yet - you still need to trigger a tile cache invalidation. This is done by altering the "Date Modified" timestamps on the .lnk files. Follow these steps:
<ol>
<li>In your Start Screen, right-click an Office tile and choose "Open file location", this will open a folder full of shortcuts to Office programs.</li>
<li>Open an Administrative Command Prompt (File Explorer &gt; File &gt; Open Command Prompt &gt; Open Command Prompt as Administrator). Accept the UAC prompt.</li>
<li>In this elevated command prompt, run this command: 
<pre>for %f in (*.*) do copy /b "%f" +,,</pre> (don't forget both commas! This command updates the Date Modified timestamp on each file)</li>
</ol>
</li>
<li>Open the Start Screen and wait a few seconds and as if by magic, the tile appearances will be refreshed with your new background colour!</li>
</ol>

<p>This works for any Start Menu shortcut to an .exe file - shortcuts to other files (e.g. *.mmc files) don't work. You can use the technique on games, like Minecraft where the bright orange background burns my retinas.</p>

<p>The schema for the VisualElementsManifest.xml files is accessible on MSDN here: <a href="https://msdn.microsoft.com/en-us/library/windows/apps/dn393983.aspx
">https://msdn.microsoft.com/en-us/library/windows/apps/dn393983.aspx</a>. You also might want to consider renaming the shortcuts for brevity, I renamed "Microsoft Office Word 2010" to just "Word".</p>

<p>You can use any hexadecimal RGB color for the <code>BackgroundColor</code> attribute (prefix it with a '#' character). Windows will generate a subtle horizontal gradient effect with the color.</p>

<p><b>Note</b> that this does not work for certain programs like Firefox which has special behaviour (Windows handles web-browsers differently) the same applies to Chrome and Internet Explorer as well.</p>

<p>Enjoy!</p>
]]></content:encoded>
    </item>
    <item>
      <title>Using VHD Native Boot with UEFI Firmware - bcdedit vs bcdboot</title>
      <link>https://docs.microsoft.com/archive/blogs/dai/using-vhd-native-boot-with-uefi-firmware-bcdedit-vs-bcdboot</link>
      <pubDate>Thu, 10 Apr 2014 13:49:00 GMT</pubDate>
      <dc:creator><![CDATA[Ḋai]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/dai/2014/04/10/using-vhd-native-boot-with-uefi-firmware-bcdedit-vs-bcdboot/</guid>
      <description><![CDATA[Recently my team switched to a new internal tool that allows us to reimage our computers from daily...]]></description>
      <content:encoded><![CDATA[<p>Recently my team switched to a new internal tool that allows us to reimage our computers from daily Windows builds <a href="en.wikipedia.org/wiki/Windows_Imaging_Format">in the WIM format</a>. Previously we were largely responsible for our own reimaging and given a broad latitude in how we switched between OS installs - some people use Hyper-V VMs, some use dedicated bootable physical disks for each installation, and some like me use Windows' VHD Native Boot feature, <a href="https://technet.microsoft.com/en-us/library/dd799282(v=ws.10).aspx">where VHD files present on your HDD can be mounted by Windows' bootloader and run from just like a physical disk</a>.</p>

<p>Windows comes with two flavours of bootloader: one for BIOS systems, and a different loader for UEFI systems. The two bootloaders look alike, but can be told-apart because the UEFI bootloader presents "Boot from Device" as one of the root menu options.</p>

<p>Previously, everyone on my team using VHD Native Boot were using Windows' BIOS-based bootloader. This was simple enough to get working, you simply need to boot into your main Windows installation and run these commands from an elevated command-prompt:</p>

<pre>bcdedit /copy {default} /d "Boot from VHD Foobar.vhd"
bcdedit /set {guid} device vhd=[D:]\VHDs\Foobar.vhd
bcdedit /set {guid} osdevice vhd=[D:]\VHDs\Foobar.vhd</pre>

<p>(where <code>{guid}</code> is the new GUID returned after running the <code>bcdedit /copy</code> command and <code>D:\VHDs\Foobar.vhd</code> is the path to the VHD file you want to boot from)</p>

<p>The above commands will edit the boot configuration file which is stored on the hidden partition on the physical disk.</p>

<p>Our internal tool that I mentioned at the beginning of this posting converted our computers from the BIOS bootloader to the UEFI bootloader. Ordinarily this isn't a problem, in fact it's a benefit as it enables features like Secure Boot and <a href="https://blogs.msdn.com/b/b8/archive/2011/09/08/delivering-fast-boot-times-in-windows-8.aspx">faster boot times</a>. The problem, however, is that the boot configuration entries added by the <code>bcdedit</code> commands above didn't work!</p>

<p>...more precisely, the <code>bcdedit /copy...</code> commands did add entries to the bootloader configuration, whenever a VHD option was selected from the bootmenu the system would reboot, attempt to mount the VHD, then fail - no error messages were displayed on screen or logged to disk, the system would simply restart and display the Windows 8.x bootmenu again.</p>

<p>After some digging around both the public web and our internal websites I discovered an alternative approach to adding a VHD Native Boot option, but curiously the pages that mention it didn't make references to UEFI booting. The technique is such:</p>

<ol>
<li>First, remove any existing VHD Native Boot entries from the bootloader that you might have added with <code>bcdedit</code> by running <code>bcdedit /delete {guid}</code> (where <code>{guid}</code> is the GUID of the VHD entry. Run <code>bcdedit /enum ALL</code> to get a complete list.</li>
<li>Mount the VHD or VHDX file by double-clicking on it in Explorer or through Disk Management in Computer Management. The drive letter that the disk is assigned doesn't matter. Let's assume it's <code>K:</code></li>
<li>In an elevated command prompt, run <code>bcdboot K:\Windows</code> (where <code>\Windows</code> is where Windows is installed on the VHD)</li>
<li>That's it! - Reboot to the bootloader menu by holding down the Shift key while clicking Restart on the Shutdown menu and the VHD should now appear in the "Another OS" submenu.</li>
</ol>

]]></content:encoded>
    </item>
    <item>
      <title>Hello, World</title>
      <link>https://docs.microsoft.com/archive/blogs/dai/hello-world-2</link>
      <pubDate>Thu, 20 Feb 2014 21:49:00 GMT</pubDate>
      <dc:creator><![CDATA[Ḋai]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/dai/2014/02/20/hello-world-2/</guid>
      <description><![CDATA[I'll be writing about Visual Studio's Blend and its HTML design tools, and anything that interests...]]></description>
      <content:encoded><![CDATA[I'll be writing about Visual Studio's Blend and its HTML design tools, and anything that interests me in the Microsoft and Windows ecosystem. Your feedback is important, so please contact me if you have any questions or problems with Microsoft Blend or Visual Studio.]]></content:encoded>
    </item>
  </channel>
</rss>