Comments
Sort by recent activity
Chris at Atlassian pointed me in the right direction- https://community.atlassian.com/t5/Opsgenie-articles/How-to-Extract-Custom-Fields-and-Data-into-an-Alert/ba-p/2133902 Turns out a plain text version of the alert is sent in the email, you have to switch the Description to {{message}} [image] [image] / comments
Chris at Atlassian pointed me in the right direction- https://community.atlassian.com/t5/Opsgenie-articles/How-to-Extract-Custom-Fields-and-Data-into-an-Alert/ba-p/2133902Turns out a plain text ver...
Please consider making it available via Powershell Gallery so I can manage updates to the module with a quick check at the beginning of our scripts instead of having to manage another .Msi installer. / comments
Please consider making it available via Powershell Gallery so I can manage updates to the module with a quick check at the beginning of our scripts instead of having to manage another .Msi installer.
VS2017 / comments
VS2017
Got a response from RedGate support- Newtonsoft.json.dll is missing from the Extensions directory: C:\Program Files (x86)\Microsoft Visual Studio\(Visual Studio Version)\(Visual Studio Edition)\Common7\IDE\Extensions\001rr241.rgs\ Manually copying the .dll there resolved the problem for me. / comments
Got a response from RedGate support-Newtonsoft.json.dll is missing from the Extensions directory: C:\Program Files (x86)\Microsoft Visual Studio\(Visual Studio Version)\(Visual Studio Edition)\Comm...
Downloaded SQL Toolbelt installer today, and it did not update to 4.3.20209 Downloaded the extension from VS Marketplace per the link, and it did update to 20209: Using SQL Change Automation version: 4.3.20209.21516 Still getting the Newtonsoft.Json error: C:\Projects\database\SQLCore\PrimeReporting\PrimeReporting.sqlproj: Error: : Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.: Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified. / comments
Downloaded SQL Toolbelt installer today, and it did not update to 4.3.20209Downloaded the extension from VS Marketplace per the link, and it did update to 20209:Using SQL Change Automation version:...
Running into the same error while attempting to deploy pending scripts. Using SQL Change Automation version: 4.3.20205.21469 Error: : Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.: Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.
/ comments
Running into the same error while attempting to deploy pending scripts.Using SQL Change Automation version: 4.3.20205.21469Error: : Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0...
It's not the first deployment to this database, both __MigrationLog and __SchemaSnapshot exist in the database and have data in them. / comments
It's not the first deployment to this database, both __MigrationLog and __SchemaSnapshot exist in the database and have data in them.
WARNING: C:\Windows\TEMP\DLM Automation\4cbf3sqa.5cl\PrimeReporting.sqlproj: No schema snapshot could be retrieved from the target database; no report will be generated until your next deployment. If you continue to see this message, then it is possible that a schema snapshot file is not being created during build. To resolve, specify the ShadowServer property in your build configuration. See https://www.red-gate.com/sca/continuous-integration / comments
WARNING: C:\Windows\TEMP\DLM Automation\4cbf3sqa.5cl\PrimeReporting.sqlproj: No schema snapshot could be retrieved from the target database; no report will be generated until your next deployment. ...
This is not the first deployment. / comments
This is not the first deployment.
That's the frustrating thing about the way the Nuget team handled this- it's a subtle problem that will continue to creep through the ecosystem, randomly breaking processes as the tools are updated. I'm sure eventually I'll update my ProGet server to find half of my deployment processes failed due to SemVer normalization. / comments
That's the frustrating thing about the way the Nuget team handled this- it's a subtle problem that will continue to creep through the ecosystem, randomly breaking processes as the tools are updated...