Activity overview
Latest activity by WillC
Thanks, deleting the entire file sorted it. I fear I will come back to this in a few months and get the same issue and forget this fix. Is there anything you need from me or I can do to help your dev team diagnose the issue to help get a more permanent fix for this? / comments
Thanks, deleting the entire file sorted it. I fear I will come back to this in a few months and get the same issue and forget this fix.Is there anything you need from me or I can do to help your de...
I'm getting the same issue version 4.4.22207.31111 The ".sqlproj.user" file doesn't contain either of these properties. / comments
I'm getting the same issue version 4.4.22207.31111The ".sqlproj.user" file doesn't contain either of these properties.
Nigel, for me to fix this I had to modify the project file, it's actually the "Default Connection string" that throws the error that is used for the Shadow Database. (even though it sounds like it's the target connection) The Key in the proj file is "<DefaultConnectionString>" The Datasource property wasn't pointing to an existing database. / comments
Nigel, for me to fix this I had to modify the project file, it's actually the "Default Connection string" that throws the error that is used for the Shadow Database. (even though it sounds like it'...
SCA toolbar - Always reports "Could not connect to server"
When using the SCA toolbar within Visual Studio I am constantly having issues with connection. The server name is correct and configured to allow remote connections.When Configuring the connection ...
We have the version set to latest on our release and that version is not being picked up. It is using the 3.2.19157 version, I added that in as a specific version and it can't be found / comments
We have the version set to latest on our release and that version is not being picked up. It is using the 3.2.19157 version, I added that in as a specific version and it can't be found
I'm getting this issue with version 3.2.19157.8337, even though our last successful release was also deployed with the same version. / comments
I'm getting this issue with version 3.2.19157.8337, even though our last successful release was also deployed with the same version.