Comments
Sort by recent activity
That is great news and I'm glad you both have Prompt up and running. The double checkbox is a carry over from a Visual Studio bug in the execution of our extensions. With SSMS now using the VS framework it's going to be visible to a larger user base of our Toolbelt products. Our development team do have it on their backlog and hopefully can be reprioritized for a solution to be implemented as we see SSMS21 use grow. The manual copy of settings issue should also be resolved from V11.0.1 onwards for people migrating into V11 from an existing install. / comments
That is great news and I'm glad you both have Prompt up and running. The double checkbox is a carry over from a Visual Studio bug in the execution of our extensions. With SSMS now using the VS fra...
I did now see that you mentioned having both unchecked - this should be the trigger for it to appear. I was able to replicate the menu disappearing by having one or both of the extensions checked. Did you upgrade straight from V10 to V11? and if so into V11.0.0? There is a known issue with some settings not being copied over. It may be worth also checking this info to manually copy over some user-settings that may not have migrated. https://documentation.red-gate.com/sp/troubleshooting/common-issues/manual-migration-of-settings-from-sql-prompt-v10-to-v11 If that still doesn't resolve the displaying of SQL Prompt, please advise and we can look deeper into this. / comments
I did now see that you mentioned having both unchecked - this should be the trigger for it to appear. I was able to replicate the menu disappearing by having one or both of the extensions checked.D...
Hi OverAchiever, Thank you for reaching out on the Redgate forums regarding your SQL Prompt & SSMS21 query. There are a couple of steps that are required to get Prompt showing within SSMS21, we have a guide available here: https://documentation.red-gate.com/sp/getting-started/installing-and-running-sql-prompt under the Running SQL Prompt with SSMS 21 section Specifically you need to un-check the two SQL Prompt extensions from the Extension menu and restart. This should allow the SQL Prompt menu to appear. / comments
Official comment
Hi OverAchiever, Thank you for reaching out on the Redgate forums regarding your SQL Prompt & SSMS21 query.There are a couple of steps that are required to get Prompt showing within SSMS21, we have...
A fix for the display issue on datatype DATETIMEOFFSET has been released in SQL Data Compare. Please patch into V15.4.18 or later to receive this fix Download link here: https://download.red-gate.com/checkforupdates/SQLDataCompare/SQLDataCompare_15.4.18.28452.exe Patch notes https://documentation.red-gate.com/sdc/release-notes-and-other-versions/sql-data-compare-15-4-release-notes
15.4.18.28452 - 03 June 2025
* Fixes
ZD-332834 and ZD-328669: Fixed handling of DATETIMEOFFSET when the timezone triggers rolling over months
/ comments
A fix for the display issue on datatype DATETIMEOFFSET has been released in SQL Data Compare.Please patch into V15.4.18 or later to receive this fix Download link here: https://download.red-gate.co...
Hi and thank you for reaching out on the Redgate forums regarding your SQL Prompt V11 upgrade. Our developers have been made aware of a migration issue when first installing V11. A number of custom features such as SQL History, Tab Color, Styles and Snippets may not migrate We would recommend the following guide to help manually migrate your settings for continued usage of the tool into its new Major Release https://documentation.red-gate.com/sp/troubleshooting/common-issues/manual-migration-of-settings-from-sql-prompt-v10-to-v11 / comments
Official comment
Hi and thank you for reaching out on the Redgate forums regarding your SQL Prompt V11 upgrade.Our developers have been made aware of a migration issue when first installing V11. A number of custom ...
Hi Tim Thank you for reaching out on the Redgate forums regarding your SmartAssembly query. You're correct that obfuscating a large solution with multiple assemblies — especially when working with ReadyToRun, self-contained builds — requires a bit more setup, particularly without using the merge feature. The recommended approach in this scenario is to use a traversal project. Here’s how that typically works:
Create a .saproj file for each assembly you want to obfuscate. Each .saproj will define the input/output paths and relevant obfuscation settings.
Set up a traversal MSBuild project that sequentially runs SmartAssembly for each of those .saproj files. This is done by referencing the SmartAssembly MSBuild task like so:<SmartAssembly ProjectFile="Path\To\YourAssembly.saproj" />
These entries can be listed one after another inside a custom MSBuild target, allowing you to run all obfuscation steps in a single build pass. Each project will need to be defined explicitly, as SmartAssembly does not currently support wildcards or dynamic project discovery.
Ensure obfuscation occurs before the ReadyToRun compilation — obfuscating after native image generation isn’t supported, as native images cannot be modified by SmartAssembly.
While this process is more manual than using the merge feature, it provides the flexibility needed for large applications deploying assemblies individually. / comments
Official comment
Hi TimThank you for reaching out on the Redgate forums regarding your SmartAssembly query. You're correct that obfuscating a large solution with multiple assemblies — especially when working with R...