Visual Studio 2013 Database Project Schema Compare, Case Sensitive Table Names

Hi,

Our current deployed development database is running under a non case sensitive collation "SQL_Latin1_General_CP1_CI_AS". When we run a schema compare from our database project to the deployed database. Any case sensitive changes to the database objects is not picked up. For example if we had a table in our database called names and Names in our database project, the schema compare would not show this as different.

Our database project has its schema set to Latin1_General_CI_AS, if I change this to Latin1_General_CS_AS then the schema compare will pick that both tables are different. If I then push the updates to my deployed database, it will not alter the existing Collation for my database. (So far so good).

However, if I try to publish my database project, even if I select the "Compare Using Target Collation" (Which I though should take the SQL Server's default collation), the database will always be deployed under the case sensitive "Latin1_General_CS_AS" collation.

I found this post for 2009:

http://social.msdn.microsoft.com/Forums/en-US/a9cfd3b5-3e51-4e11-b341-fa80ef87da31/use-target-collation-does-not-seem-to-affect-generated-script-via-schema-compareexport-to-editor?forum=vstsdb

It seems to say that this problem was fixed back then.

1.) Am I misunderstanding this?

2.) Is this a bug or can I use some other Ignore setting?

3.) Will it make a huge difference if I use a case sensitive schema?