%Program Files%\Microsoft SQL Server\110\Tools\Binn\
We made an explicit decision not to include .NET Framework 4.0.2 in LocalDB installer. Installing the .NET Framework update would increase the size of the LocalDB installer and cause a likely
reboot. Since LocalDB is built to be independent of the .NET, we didn’t think we should take this cost for every LocalDB installation. Future .NET versions (including .NET 4.5, now in CTP) will support LocalDB out of the box. Some developers may also want
to opt in for ODBC, PHP Driver/PDO, and probably JDBC in the future. Those developers will not be interested in updating .NET.
I have compared this article with other ones about the same subject.
I don't see any mention about CTP3. Is it meaning that the release of SQL Server 2012 is imminent ?
I know you are not allowed to answer now, but if you reply after the release date, it will be kind
I Installed LocalDb on my Windows 7 64bit and try to create a connection using Visual Studio 2010 but their is no data source listed for it. Do I need to install something else?
Please note that the connect string format under "SSMS issues" applies only to shared instances. If you are using a private instance, or are the owner of the shared instance, you can connect with "(localdb)\InstanceName".
Updated the WIKI based on my previous comment, so it is now correct.
I have tried using the named pipes connection string from "sqllocaldb i MyInstance" as well as the shared instance connection string. Both fail with a "network-related or instance-specific error occurred..." - when using a named pipe connection string, the suffix of the error message changes to "(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server). Are there any API calls that might shed some light on this?
Connection strings are described in SQL Server Books Online in two topics. SQL Server 2012 Express LocalDB msdn.microsoft.com/.../hh510202.aspx and SqlLocalDB Utility msdn.microsoft.com/.../hh212961.aspx
I have problems connecting to LocalDB when I am running via msdeploy. It works fine with the same user if I run via an interactive sessions but if I run it via msdeploy it fails with error 575.