VS2012 Dependency Graph
-
I'm using VS2012 and have Sql Server Express 2012 installed on my dev box. When I try to use the Architecture | Dependency Graph feature, it throws an exception about not being able to connect to LocalDB. 0) Can I point it at Sql Server instead? If so, how? I looked in the devenv.exe.config file as well as the registry, and didn't find any connection strings. 1) I tried to find sqllocaldb on my system, but all I found were MSI files and a folder with database files (mdf, etc). It's almost like it used to be installed, but now it isn't. There is no sqllocaldb windows service running that I can see.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
I'm using VS2012 and have Sql Server Express 2012 installed on my dev box. When I try to use the Architecture | Dependency Graph feature, it throws an exception about not being able to connect to LocalDB. 0) Can I point it at Sql Server instead? If so, how? I looked in the devenv.exe.config file as well as the registry, and didn't find any connection strings. 1) I tried to find sqllocaldb on my system, but all I found were MSI files and a folder with database files (mdf, etc). It's almost like it used to be installed, but now it isn't. There is no sqllocaldb windows service running that I can see.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013LocalDB doesn't run as a service:
Introducing LocalDB, an improved SQL Express[^]
LocalDB doesn't create any database services; LocalDB processes are started and stopped automatically when needed. The application is just connecting to "Data Source=(localdb)\v11.0" and LocalDB process is started as a child process of the application. A few minutes after the last connection to this process is closed the process shuts down.
There doesn't appear to be an option to use full SQL Server instead of LocalDB. Try running VS elevated, in case it's a permissions problem. You could also try re-creating the LocalDB instance:
sqllocaldb stop "v11.0" -k
sqllocaldb delete "v11.0"
sqllocaldb create "v11.0"
sqllocaldb start "v11.0"
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
