title: Visual Studio 2013 Schema Compare/Publish ignores column order in definition of foreign key constraint
body: <p>Visual Studio schema compare and database publishing tools are not detecting differences in the order of the columns defining foreign keys.</p>
  
  <p>Assume the following foreign key constraint exists on Source Database/Database Project:</p>
  
  <pre><code>ALTER TABLE dbo.ReferencingTable
  ADD CONSTRAINT FK_1
  FOREIGN KEY (Column1, Column2)
  REFERENCES dbo.ReferencedTable (Column1, Column2)
  </code></pre>
  
  <p>Assume Target Database/Database Project to be exactly the same except that for foreign key FK_1, columns are defined in a different order (Notice the Column2 now pointing to dbo.ReferencedTable.Column1, and Column 1 is pointing to dbo.ReferencedTable.Column2) like this:</p>
  
  <pre><code>ALTER TABLE dbo.ReferencingTable
  ADD CONSTRAINT FK_1
  FOREIGN KEY (Column2, Column1)
  REFERENCES dbo.ReferencedTable (Column1, Column2)
  </code></pre>
  
  <p>Note: Assume columns are type compatible (Ex. all INT)</p>
  
  <p>I would expect VS to detect this difference and generate the proper script to update the target schema (namely the target foreign key).</p>
  
  <p>Could not find a Setting/Option to control this behavior. Is this a bug?</p>