Activity overview
Latest activity by brockweaver
Actually, only TLS 1.2 is enabled on the 2016 sql server box. That's when the problem appeared -- once support for TLS 1.0 and TLS 1.1 was removed from our db server. We do have .NET 4.6.1 installed on the box where SQL Compare runs. I upgraded to the latest version of SQL Compare (13.1.11.5591 Pro) before you responded and that fixed the issue. But I do appreciate you following up! By the way, what's the dilleo with the Asteroids game easter egg when you leave the Help | About screen up for a bit? Just curious [image] / comments
Actually, only TLS 1.2 is enabled on the 2016 sql server box. That's when the problem appeared -- once support for TLS 1.0 and TLS 1.1 was removed from our db server. We do have .NET 4.6.1 instal...
TLS 1.0 Disabled, can no longer Check For Updates or pull from TFS
Running version 13.0.2.5109 of SQL Compare, registered copy. Per our recent PCI audit, we had to disable TLS 1.0 on all our production servers. It is not an option to re-enable it for any reason....
Project-Refrenced CLR Assemblies Not Recognized
I'm using version 12.0.35.3485 (trial). If my database project references a CLR using a Project Reference in Visual Studio (i.e. it's another project in the solution, and is referenced as such), t...
I had this same issue -- pulled down latest (12.0.35.3485) and it fixed the problem.
However, the assembly we deploy has its "Permission Set" = UNSAFE in the db References, yet the script is still created having "WITH PERMISSION_SET = SAFE".
Easy enough to rectify after script is generated, just thought I'd bring it to your attention.
Note I've only tried generating the script, not deploying directly to the db. / comments
I had this same issue -- pulled down latest (12.0.35.3485) and it fixed the problem.
However, the assembly we deploy has its "Permission Set" = UNSAFE in the db References, yet the script is still ...