Text Encoding Options for NLog

I’ve been using NLog for a while now and recently decided I wanted to have some of my log files written as Unicode text.  I learned that you can specify this in your <target> sections of NLog.config as follows:

Note that I only tested two different encodings, “Unicode” and “UTF-8”.  Also, “UTF-8” must have the hyphen in it to work.


This post was migrated from https://blogs.msdn.microsoft.com/rob/2013/01/05/text-encoding-options-for-nlog/.

The site is back online

After a problem with the web site about six months ago, I have recreated the Tardis Technologies blog.  Unfortunately, the WordPress database format changed a little bit, so I need to do some work to get it back in a format for posting.  The first post is back online.  I hope to get the rest of the old content online soon.


Migrating a Storage Pool from Windows Server 8 Beta to Windows Server 2012 RTM

I had a computer running Windows Server 8 Beta with a Storage Pool using the “Parity” resiliency type.  I installed Windows Server 2012 RTM “over it” (i.e. not an upgrade) and completely lost access to this Storage Pool when the  RTM install completed.  So, using a number of MSDN resources and PowerShell commands, I got the Storage Pool back using the following steps:

    1. Reinstalled Windows Server 8 Beta (Build 8250).
    2. Opened PowerShell as Administrator (i.e. elevated).
    3. Executed the following command:
    4. This showed that I had two Storage Pools available.
    1. The one named “RAID” is the one that I wanted to mount.
    2. I found instructions suggesting that I make it read/write, so I executed the following command:
    3. Executing Get-StoragePool again displayed the following:
    1. Storage Pools are mounted as Virtual Disks and need to be referenced by a Virtual Disk Friendly Name, not a Storage Pool Friendly Name.  To determine which Virtual Disks were available for mounting and their Friendly Names, I issued the following command:
    2. This showed the Virtual Disk’s name to be “RAID5”:
  1. Then I issued the following command to mount the Virtual Disk:
  2. At this point, the disk appeared in “Disk Management” (diskmgmt.msc), but it was offline.
  3. I right-clicked on the area labeled “Disk 6, Basic, … , Offline” and selected “Online”.  Then the drive was mounted to the first available drive letter:
    Disk Management 
  4. Then I went into the D: drive, copied all of the files to another partition, and reinstalled Windows Server 2012 RTM where I could create a new, RTM-compatible Storage Space and copy the data back to it.


This post was migrated from https://blogs.msdn.microsoft.com/rob/2012/12/18/migrating-a-storage-pool-from-windows-server-8-beta-to-windows-server-2012-rtm/.

Combining Files in PowerShell

If you need to combine text files in cmd.exe, you would issue the following command:

If you wish to do the same for binary files, you would use the following command:

To do the same in PowerShell is pretty straightforward.  If the destination file does not already exist or already contains content, you’ll want to issue the New-Item command first.  If you know it doesn’t exist or is empty, you can skip that line, below.

Thanks to Gerardo Lopez for his “Combine or Join Two Text Files Using PowerShell” article, which is the basis for this information.


This post was migrated from https://blogs.msdn.microsoft.com/rob/2012/11/21/combining-files-in-powershell/.

Solved: The working folder is already in use by the workspace

When trying to map a local folder to a TFS server as a different user than the one under which I was logged in, I kept getting the message:

I was finally able to map the folder by first deleting the local workspace as the logged in user:

Note that the “owner” was the currently logged-in user.

Thanks to the “Geek-A-Boo” blog for the solution at this page.


This post was migrated from https://blogs.msdn.microsoft.com/rob/2012/10/13/solved-the-working-folder-is-already-in-use-by-the-workspace/.

Load more