title: VBA equivalent to C# using or VB.NET imports / creating aliases
body: <p>Base Reference: <a href="http://msdn.microsoft.com/en-us/library/office/aa164018%28v=office.10%29.aspx">Ten Code Conversions for VBA, Visual Basic .NET, and C#</a><br></p>
  
  <p>Note: <em>I have already created and imported a <code>*.dll</code>, this question is about</em> <strong><em>aliases</em></strong>.</p>
  
  <p>Let's say the programmatic name of a <code>Test</code> class is <code>TestNameSpace.Test</code></p>
  
  <pre><code>[ProgId("TestNamespace.Test")]
  public class Test ...
  </code></pre>
  
  <p>Now, say a C# solution has been sealed and compiled into a <code>*.dll</code> and I'm referencing it in a Excel's VBE. Note: at this point I cannot modify the programmatic name as if the <code>*.dll</code> wasn't written by me. <br></p>
  
  <p>This is in <strong><code>VBA</code></strong> : Instead of declaring a variable like this:</p>
  
  <pre><code>Dim myTest As TestNameSpace.Test
  Set myTest = new TestNameSpace.Test
  </code></pre>
  
  <p>I'd prefer to call it (still in VBE) </p>
  
  <pre><code>Dim myTest As Test
  Set myText = new Test
  </code></pre>
  
  <p>In C# you would normally say</p>
  
  <pre><code>using newNameForTest = TestNamespace.Test;
  newNameForTest myTest = new NewNameForTest;
  </code></pre>
  
  <p>Note: Assume there are <em>no namespace conflicts</em> in the <code>VBA</code> project</p>
  
  <p>Question: <strong>is there an equivalent call in <code>VBA</code> to <code>C#</code> <em><code>using</code></em> or <code>VB.NET</code> <em><code>imports</code></em> aliases?</strong></p>