title: CREATE ASSEMBLY in UNSAFE mode with File path does not create Functions in database
body: <p>I am trying to register CLR assembly in SQL Server with following statement:</p>
  
  <pre><code>CREATE ASSEMBLY SQLCLRTest
  AUTHORIZATION [dbo]
  FROM 'C:\MyApp\SQLCLRTest.dll'
  WITH PERMISSION_SET = UNSAFE;
  </code></pre>
  
  <p>The CLR assembly is signed with a pfx key, and I have already created an Asymmetric key and a SQL login like to allow installing this particular assembly with UNSAFE permissions set.</p>
  
  <p>The problem is that above statement creates the assembly in database, but it doesn't show up any sql server functions I have created in the assembly.</p>
  
  <p>I dont see any issue with my CLR assembly, because when I publish the database through SQL Server Database project in Visual Studio I can see all functions getting created in the database. When I looked into the Publish scripts, I could see the database project uses Binary of the assembly. That means, it executes something like </p>
  
  <pre><code>CREATE ASSEMBLY SQLCLRTest
  AUTHORIZATION [dbo]
  FROM 0x4D5A90000300000004000000FFFF000.......
  WITH PERMISSION_SET = UNSAFE;
  </code></pre>
  
  <p>So my questions is why the assembly gets registered properly through the DLL binaries, but not when I use DLL's path?</p>
  
  <p>Any help on this will be much appreciated.</p>
  
  <p>Database server: SQL Server 2012. Database project is created in Visual Studio 2013. CLR assembly is created as a separate class library project in Visual Studio 2013. </p>