added external packages.

.gitignore

@@ -2,6 +2,8 @@ bin
 obj
 tags
 *.exe
+*.dll
+*.pdb
 *.suo
 *.pfx
 *;*

packages/BouncyCastle.1.7.0/BouncyCastle.1.7.0.nuspec

@@ -0,0 +1,34 @@
+<?xml version="1.0"?>
+<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
+  <metadata>
+    <id>BouncyCastle</id>
+    <version>1.7.0</version>
+    <title>Bouncy Castle</title>
+    <authors>Bouncy Castle Project Contributors</authors>
+    <owners>Bouncy Castle Project Contributors</owners>
+    <projectUrl>http://www.bouncycastle.org/csharp/</projectUrl>
+    <requireLicenseAcceptance>false</requireLicenseAcceptance>
+    <description>BouncyCastle.Crypto is a cryptography API providing:
+ -Generation and parsing of PKCS#12 files.
+ -X.509: Generators and parsers for V1 and V3 certificates, V2 CRLs and attribute certificates.
+ -PBE algorithms supported by PBEUtil: PBEwithMD2andDES-CBC, PBEwithMD2andRC2-CBC, PBEwithMD5andDES-CBC, PBEwithMD5andRC2-CBC, PBEwithSHA1andDES-CBC, PBEwithSHA1andRC2-CBC, PBEwithSHA-1and128bitRC4, PBEwithSHA-1and40bitRC4, PBEwithSHA-1and3-keyDESEDE-CBC, PBEwithSHA-1and2-keyDESEDE-CBC, PBEwithSHA-1and128bitRC2-CBC, PBEwithSHA-1and40bitRC2-CBC, PBEwithHmacSHA-1, PBEwithHmacSHA-224, PBEwithHmacSHA-256, PBEwithHmacRIPEMD128, PBEwithHmacRIPEMD160, and PBEwithHmacRIPEMD256.
+ -Signature algorithms supported by SignerUtilities: MD2withRSA, MD4withRSA, MD5withRSA, RIPEMD128withRSA, RIPEMD160withRSA, RIPEMD256withRSA, SHA-1withRSA, SHA-224withRSA, SHA-256withRSAandMGF1, SHA-384withRSAandMGF1, SHA-512withRSAandMGF1, SHA-1withDSA, and SHA-1withECDSA.
+ -Symmetric key algorithms: AES, Blowfish, Camellia, CAST5, CAST6, DESede, DES, GOST28147, HC-128, HC-256, IDEA, NaccacheStern, RC2, RC4, RC5-32, RC5-64, RC6, Rijndael, Serpent, Skipjack, TEA/XTEA, Twofish, and VMPC.
+ -Symmetric key modes: CBC, CFB, CTS, GOFB, OFB, OpenPGPCFB, and SIC (or CTR).
+ -Symmetric key paddings: ISO10126d2, ISO7816d4, PKCS#5/7, TBC, X.923, and Zero Byte.
+ -Asymmetric key algorithms: RSA (with blinding), ElGamal, DSA, ECDSA.
+ -Asymmetric key paddings/encodings: ISO9796d1, OAEP, and PKCS#1.
+ -Digests: GOST3411, MD2, MD4, MD5, RIPEMD128, RIPEMD160, RIPEMD256, RIPEMD320, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, Tiger, and Whirlpool.
+ -Signer mechanisms: DSA, ECDSA, ECGOST3410, GOST3410, ISO9796d2, PSS, RSA.
+ -Key Agreement: Diffie-Hellman and EC-DH.
+ -Macs: CBCBlockCipher, CFBBlockCipher, GOST28147, HMac, and ISO9797 Alg. 3.
+ -PBE generators: PKCS#12, and PKCS#5 - schemes 1 and 2.
+ -OpenPGP (RFC 2440)
+ -Cryptographic Message Syntax (CMS, RFC 3852), including streaming API.
+ -Online Certificate Status Protocol (OCSP, RFC 2560).
+ -Time Stamp Protocol (TSP, RFC 3161).
+ -TLS/SSL Client with support for client side authentication.</description>
+    <summary>BouncyCastle.Crypto is a cryptography API providing: -Generation and parsing of PKCS#12 files. -X.509: Generators and parsers for V1 and V3 certificates, V2 CRLs and attribute certificates. -PBE algorithms supported by PBEUtil: PBEwithMD2andDES-CBC, PBEwithMD2andRC2-CBC, PBEwithMD5andDES-CBC, PBEwithMD5andRC2-CBC, PBEwithSHA1andDES-CBC, PBEwithSHA1andRC2-CBC, PBEwithSHA-1and128bitRC4, PBEwithSHA-1and40bitRC4, PBEwithSHA-1and3-keyDESEDE-CBC, PBEwithSHA-1and2-keyDESEDE-CBC, PBEwithSHA-1and128bitRC2-CBC, PBEwithSHA-1and40bitRC2-CBC, PBEwithHmacSHA-1, PBEwithHmacSHA-224, PBEwithHmacSHA-256, PBEwithHmacRIPEMD128, PBEwithHmacRIPEMD160, and PBEwithHmacRIPEMD256. -Signature algorithms supported by SignerUtilities: MD2withRSA, MD4withRSA, MD5withRSA, RIPEMD128withRSA, RIPEMD160withRSA, RIPEMD256withRSA, SHA-1withRSA, SHA-224withRSA, SHA-256withRSAandMGF1, SHA-384withRSAandMGF1, SHA-512withRSAandMGF1, SHA-1withDSA, and SHA-1withECDSA. -Symmetric key algorithms: AES, Blowfish, Camellia, CAST5, CAST6, DESede, DES, GOST28147, HC-128, HC-256, IDEA, NaccacheStern, RC2, RC4, RC5-32, RC5-64, RC6, Rijndael, Serpent, Skipjack, TEA/XTEA, Twofish, and VMPC. -Symmetric key modes: CBC, CFB, CTS, GOFB, OFB, OpenPGPCFB, and SIC (or CTR). -Symmetric key paddings: ISO10126d2, ISO7816d4, PKCS#5/7, TBC, X.923, and Zero Byte. -Asymmetric key algorithms: RSA (with blinding), ElGamal, DSA, ECDSA. -Asymmetric key paddings/encodings: ISO9796d1, OAEP, and PKCS#1. -Digests: GOST3411, MD2, MD4, MD5, RIPEMD128, RIPEMD160, RIPEMD256, RIPEMD320, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, Tiger, and Whirlpool. -Signer mechanisms: DSA, ECDSA, ECGOST3410, GOST3410, ISO9796d2, PSS, RSA. -Key Agreement: Diffie-Hellman and EC-DH. -Macs: CBCBlockCipher, CFBBlockCipher, GOST28147, HMac, and ISO9797 Alg. 3. -PBE generators: PKCS#12, and PKCS#5 - schemes 1 and 2. -OpenPGP (RFC 2440) -Cryptographic Message Syntax (CMS, RFC 3852), including streaming API. -Online Certificate Status Protocol (OCSP, RFC 2560). -Time Stamp Protocol (TSP, RFC 3161). -TLS/SSL Client with support for client side authentication.</summary>
+    <tags>bouncycastle cryptography encryption security</tags>
+  </metadata>
+</package>

packages/BouncyCastle.1.7.0/Readme.txt

@@ -0,0 +1,6 @@
+
+For documentation and mailing lists, see the project web site: http://www.bouncycastle.org/csharp/
+
+Contact me directly for package/build issues: www.soygul.com/contact
+
+© 2011, Bouncy Castle Project

packages/Ookii.Dialogs.1.0/Ookii.Dialogs.1.0.nuspec

@@ -0,0 +1,16 @@
+<?xml version="1.0"?>
+<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
+  <metadata>
+    <id>Ookii.Dialogs</id>
+    <version>1.0</version>
+    <title>Ookii Dialogs WPF library</title>
+    <authors>Sven Groot</authors>
+    <owners>Sven Groot</owners>
+    <projectUrl>http://www.ookii.org/software/dialogs/</projectUrl>
+    <iconUrl>http://www.ookii.org/favicon.ico</iconUrl>
+    <requireLicenseAcceptance>false</requireLicenseAcceptance>
+    <description>Ookii.Dialogs is a class library for .Net applications providing several common dialogs. It includes classes for task dialog, credential dialog, progress dialog, input dialog, and common file dialogs. This library is intended for use in WPF applications.</description>
+    <summary>Ookii.Dialogs is a class library for .Net applications providing several common dialogs. It includes classes for task dialog, credential dialog, progress dialog, input dialog, and common file dialogs.</summary>
+    <tags>wpf task dialogs</tags>
+  </metadata>
+</package>

packages/Ookii.Dialogs.1.0/license.txt

@@ -0,0 +1,29 @@
+License agreement for Ookii.Dialogs.
+
+Copyright © Sven Groot (Ookii.org) 2009
+All rights reserved.
+
+
+Redistribution and use in source and binary forms, with or without 
+modification, are permitted provided that the following conditions are met:
+
+1) Redistributions of source code must retain the above copyright notice, 
+   this list of conditions and the following disclaimer. 
+2) Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution. 
+3) Neither the name of the ORGANIZATION nor the names of its contributors
+   may be used to endorse or promote products derived from this software
+   without specific prior written permission. 
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
+LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
+THE POSSIBILITY OF SUCH DAMAGE.

packages/Ookii.Dialogs.1.0/readme.html

@@ -0,0 +1,223 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+    <title>Ookii.Dialogs</title>
+    <style type="text/css">
+        body
+        {
+	        font-family: Calibri, sans-serif;
+	        background: white;
+	        color: black;
+        }
+        a:link, a:visited, a:active
+        {
+	        color: #00008B;
+        }
+        h1
+        {
+	        font-weight: bold;
+	        font-size: xx-large;
+        }
+        h2
+        {
+	        color: #00008B;
+	        font-weight: bold;
+	        font-style: italic;
+	        font-size: large;
+        }
+        h3
+        {
+	        font-size: medium;
+        }
+        img
+        {
+	        border: none;
+        }
+        .copyright
+        {
+            font-style: italic;
+        }
+    </style>
+</head>
+<body>
+    <h1>
+        Ookii.Dialogs
+    </h1>
+    <p class="copyright">
+        Copyright © Sven Groot (Ookii.org) 2009, see license.txt for details
+    </p>
+    <h2>
+        Overview
+    </h2>
+    <p>
+        Ookii.Dialogs is a class library for .Net applications providing several common dialogs. Included are classes for
+        task dialogs, credential dialogs, progress dialogs, input dialogs, and common file dialogs.
+    </p>
+    <p>
+        This package contains two class libraries: Ookii.Dialogs.dll for use with Windows Forms, and Ookii.Dialogs.Wpf.dll
+        for use with Windows Presentation Foundation. The classes inside are pretty much identical; only the input dialog
+        is not available for WPF. Some additional utility classes for Windows Forms are provided that are not available for
+        WPF, see below for details.
+    </p>
+    <p>
+        Ookii.Dialogs requires the <a href="http://www.ookii.org/link.ashx?id=NetFramework35">Microsoft .Net Framework 3.5 SP1</a>.
+        The included source code is intended for use in Visual Studio 2008.
+    </p>
+    <p>
+        The included sample applications Ookii.Dialogs.Sample.exe and Ookii.Dialogs.Sample.Wpf.exe demonstrate the dialogs
+        for Windows Forms and WPF respectively. View the source of these applications to see how to use the dialogs.
+    </p>
+    <p>
+        Full reference documentation for the class library is available in the <a href="Ookii.Dialogs.chm">included help file</a>.
+    </p>
+    <h2>
+        Included dialogs
+    </h2>
+    <h3>
+        Task dialog
+    </h3>
+    <p>
+        <a href="http://msdn.microsoft.com/en-us/library/bb760441(VS.85).aspx">Task dialogs</a> are a new type of dialog
+        first introduced in Windows Vista. They provide a superset of the message box functionality.
+    </p>
+    <p>
+        <img src="images/taskdialog.png" alt="A task dialog" />
+    </p>
+    <p>
+        The Ookii.Dialogs.TaskDialog (for Windows Forms) and the Ookii.Dialogs.Wpf.TaskDialog (for WPF) classes provide access
+        to the task dialog functionality. The TaskDialog class inherits from System.ComponentModel.Component and offers full
+        support for the Windows Forms designer and component designer of Visual Studio 2008.
+    </p>
+    <p>
+        The TaskDialog class requires Windows Vista or a later version of Windows. Windows XP is not supported. Note that it is
+        safe to instantiate the TaskDialog class and set any of its properties; only when the dialog is shown will a NotSupportedException
+        be thrown on unsupported operating systems.
+    </p>
+    <h3>
+        Progress dialog
+    </h3>
+    <p>
+        Progress dialogs are a common dialog to show progress during operations that may take a long time. They are used
+        extensively in the Windows shell, and an API has been available since Windows 2000.
+    </p>
+    <p>
+        <img src="images/progressdialog.png" alt="A progress dialog as it appears on Windows Vista and later" />
+    </p>
+    <p>
+        The Ookii.Dialogs.ProgressDialog (for Windows Forms) and the Ookii.Dialogs.Wpf.ProgressDialog (for WPF) classes provide
+        a wrapper for the Windows progress dialog API. The ProgressDialog class inherits from System.ComponentModel.Component and offers full
+        support for the Windows Forms designer and component designer of Visual Studio 2008. The ProgressDialog class resembles
+        the System.ComponentModel.BackgroundWorker class and can be used in much the same way as that class.
+    </p>
+    <p>
+        The progress dialog's behaviour of the ShowDialog function is slightly different than that of other .Net dialogs; please
+        read the reference documentation for more information. It is recommended to use a non-modal dialog with the Show function.
+    </p>
+    <p>
+        The ProgressDialog class is supported on Windows XP and later versions of Windows. However, the progress dialog has a very different
+        appearance on Windows Vista and later (the image above shows the Vista version), so it is recommended to test on both
+        operating systems to see if it appears to your satisfaction.
+    </p>
+    <p>
+        When using Windows 7, the ProgressDialog class automatically provides progress notification in the application's task bar
+        button.
+    </p>
+    <h3>
+        Credential dialog
+    </h3>
+    <p>
+        The Ookii.Dialogs.CredentialDialog (for Windows Forms) and the Ookii.Dialogs.Wpf.CredentialDialog (for WPF) classes provide
+        wrappers for the CredUI functionality first introduced in Windows XP. This class provides functionality for saving and
+        retrieving generic credentials, as well as displaying the credential UI dialog. This class does not support all functionality
+        of CredUI; only generic credentials are supported, thing such as domain credentials or alternative authentication
+        providers (e.g. smart cards or biometric devices) are not supported.
+    </p>
+    <p>
+        <img src="images/credentialdialog.png" alt="A credential dialog as it appears on Windows Vista and later" />
+    </p>
+    <p>
+        The CredentialDialog class inherits from System.ComponentModel.Component and offers full
+        support for the Windows Forms designer and component designer of Visual Studio 2008.
+    </p>
+    <p>
+        On Windows XP, the CredentialDialog class will use the CredUIPromptForCredentials function to show the dialog;
+        on Windows Vista and later, the CredUIPromptForWindowsCredentials function is used instead to show the new dialog
+        introduced with Windows Vista. Because of the difference in appearance in the two versions (the image above shows
+        the Vista version), it is recommended to test on both operating systems to see if it appears to your satisfaction.
+    </p>
+    <h3>
+        Input dialog
+    </h3>
+    <p>
+        The input dialog is a dialog that can be used to prompt the user for a single piece of text. Its functionality
+        is reminiscent of the Visual Basic InputBox function, only with a cleaner API and UI.
+    </p>
+    <p>
+        <img src="images/inputdialog.png" alt="An input dialog as it appears on Windows Vista and later" />
+    </p>
+    <p>
+        The Ookii.Dialogs.InputDialog class provides the input dialog functionality for Windows Forms. This class is not
+        available for WPF.
+    </p>
+    <p>
+        Unlike the other classes in this package, this class is not a wrapper for any existing API; the dialog uses
+        a custom implementation in Windows Forms. This dialog is supported on Windows XP and later versions of windows;
+        on Windows Vista and later, the visual styles API is used to draw the dialog to mimic the appearance of task dialogs,
+        as shown in the image above.
+    </p>
+    <p>
+        The InputDialog class inherits from System.ComponentModel.Component and offers full
+        support for the Windows Forms designer and component designer of Visual Studio 2008.
+    </p>
+    <h3>
+        Vista-style common file dialogs
+    </h3>
+    <p>
+        Windows Vista introduced a new style of common file dialogs. As of .Net 3.5 SP1, the Windows Forms OpenFileDialog and
+        SaveFileDialog class will automatically use the new style under most circumstances; however, some settings (such
+        as setting ShowReadOnly to true) still cause it to revert to the old dialog. The FolderBrowserDialog still uses the
+        old style. In WPF, the Microsoft.Win32.OpenFileDialog and SaveFileDialog classes still use the old style dialogs,
+        and a folder browser dialog is not provided at all.
+    </p>
+    <p>
+        <img src="images/folderbrowserdialog.png" alt="The Vista-style folder browser dialog on Windows 7" />
+    </p>
+    <p>
+        The Ookii.Dialogs.VistaOpenFileDialog, Ookii.Dialogs.VistaSaveFileDialog and Ookii.Dialogs.VistaFolderBrowserDialog
+        provide these dialogs for Windows Forms (note that in the case of the OpenFileDialog and SaveFileDialog it is
+        recommended to use the built-in .Net classes unless you hit one of the scenarios where those classes use the old
+        dialogs). The Ookii.Dialogs.Wpf.VistaOpenFileDialog, Ookii.Dialogs.Wpf.VistaSaveFileDialog and Ookii.Dialogs.Wpf.VistaFolderBrowserDialog
+        classes provide the same functionality for WPF.
+    </p>
+    <p>
+        The classes have been designed to resemble the original Windows Forms and WPF classes to make it easy to switch.
+        When the classes are used on Windows XP, they will automatically fall back to the old style dialog; this is also
+        true for the VistaFolderBrowserDialog on WPF; that class provides a complete implementation of a folder browser
+        dialog for WPF, old as well as new style.
+    </p>
+    <p>
+        The Vista-style file and folder dialogs classes for Windows Forms inherit from System.ComponentModel.Component and offer full
+        support for the Windows Forms designer and component designer of Visual Studio 2008.
+    </p>
+    <h2>
+        Additional functionality for Windows Forms
+    </h2>
+    <p>
+        Three additional classes are provided for Windows Forms only, in the Ookii.Dialogs library. These classes are used to
+        support the InputDialog (with the exception of the Aero glass functionality, which the InputDialog does not use) but
+        are made public for your convenience.
+    </p>
+    <p>
+        The AdditionalVisualStyleElements class provides some visual style elements used by task dialogs on Windows Vista and later.
+    </p>
+    <p>
+        The Glass class provides functionality for extending Aero glass into the client area of a window on Windows Vista and later,
+        and for drawing text on a glass surface.
+    </p>
+    <p>
+        The ExtendedForm class serves as an alternative base class for forms, and provides functionality to automatically use the
+        system font (e.g. Tahoma on XP and Segoe UI on Vista and later), and easy access to some of the functionality of the Glass
+        class.
+    </p>
+</body>
+</html>

packages/WindowsAPICodePack-Core.1.1/WindowsAPICodePack-Core.1.1.nuspec

@@ -0,0 +1,18 @@
+<?xml version="1.0"?>
+<package xmlns="http://schemas.microsoft.com/packaging/2011/08/nuspec.xsd">
+  <metadata>
+    <id>WindowsAPICodePack-Core</id>
+    <version>1.1</version>
+    <title>Windows API Code Pack - Core</title>
+    <authors>Aybe</authors>
+    <owners>Aybe</owners>
+    <licenseUrl>http://code.msdn.microsoft.com/WindowsAPICodePack/Project/License.aspx</licenseUrl>
+    <projectUrl>http://archive.msdn.microsoft.com/WindowsAPICodePack</projectUrl>
+    <requireLicenseAcceptance>true</requireLicenseAcceptance>
+    <description>Core library for Windows API Code Pack</description>
+    <summary>Windows® API Code Pack for Microsoft® .NET Framework provides a source code library that can be used to access some features of Windows 7 and Windows Vista from managed code.</summary>
+    <releaseNotes>Fixes TaskDialog.Icon bug that wasn't visible unless specified duringTaskDialog.Opened event.</releaseNotes>
+    <language>en-US</language>
+    <tags>WindowsAPICodePack</tags>
+  </metadata>
+</package>

packages/WindowsAPICodePack-Shell.1.1/WindowsAPICodePack-Shell.1.1.nuspec

@@ -0,0 +1,20 @@
+<?xml version="1.0"?>
+<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
+  <metadata>
+    <id>WindowsAPICodePack-Shell</id>
+    <version>1.1</version>
+    <title>Windows API Code Pack - Shell</title>
+    <authors>Aybe</authors>
+    <owners>Aybe</owners>
+    <licenseUrl>http://code.msdn.microsoft.com/WindowsAPICodePack/Project/License.aspx</licenseUrl>
+    <projectUrl>http://archive.msdn.microsoft.com/WindowsAPICodePack</projectUrl>
+    <requireLicenseAcceptance>true</requireLicenseAcceptance>
+    <description>Shell library for Windows API Code Pack</description>
+    <summary>Windows® API Code Pack for Microsoft® .NET Framework provides a source code library that can be used to access some features of Windows 7 and Windows Vista from managed code.</summary>
+    <language>en-US</language>
+    <tags>WindowsAPICodePack</tags>
+    <dependencies>
+      <dependency id="WindowsAPICodePack-Core" version="1.1" />
+    </dependencies>
+  </metadata>
+</package>

packages/repositories.config

@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="utf-8"?>
+<repositories>
+  <repository path="..\..\GARbro.GUI\packages.config" />
+  <repository path="..\ArcFormats\packages.config" />
+</repositories>