VS2022 extension installation error.
bmarge
Posts: 3 New member
Trying to install RedGate.SqlChangeAutomation.VisualStudio.vsix
I get an error:
Inspecting the file in the error message I get:
I get an error:
Inspecting the file in the error message I get:
SetSite failed for package [SqlChangeAutomationVsPackage]Source: 'Autofac' Description: An exception was thrown while activating RedGate.Versioning.Client.VsShell.VisualStudio.EventsDispatcher -> RedGate.Versioning.Client.VsShell.VisualStudio.ShellIntegration.Events.ProjectMenuEvents -> RedGate.Versioning.Client.VsShell.VisualStudio.Windows.ToolWindow.ToolWindowVisibility -> RedGate.Versioning.Client.VsShell.VisualStudio.ProjectSelection.SelectProjectService -> RedGate.Versioning.Client.VsShell.VisualStudio.PendingChangeModel -> RedGate.Versioning.Client.VsShell.VisualStudio.Views.ContentSwitcher -> RedGate.Versioning.Client.Licensing.Admittance.UserAdmittance -> RedGate.Versioning.Client.Licensing.RedgateLicensing.RedgateLicensor. /****** UPDATE 2022-11-11 *****************/ This problem is now solved. |
Tagged:
Comments
I tried to revert to previous version, but that didn't resolve the problem.
I ended up unstalling and reinstalling VS2022.
Then I installed a SCA version from a month ago. That gave no issues.
Then I updated to the last version.. Got the error back.
Reverted to previous SCA version and then I did work again.
I have seen this before and it usually happens if you have another Visual Studio extension that uses an older version of the Serilog library. Are you running any other extensions in Visual Studio, not just RedGate's?
If you are, I would recommend trying to disable any other extensions temporarily to see if you can find which one might be causing the error.
If that doesn't work, please let me know.
That is not the problem this time. Activitylog.xml doesn't mention serilog problems.
This is a new problem happening only in the latest release of SCA.
We've since seen other customers experiencing the issue too. We have replicated it, and for an immediate solution, Downgrading to version 4.5.22300.32307 is a workaround.
However, I'll now keep you updated as it is escalated to the development team.
https://download.red-gate.com/checkforupdates/SQLChangeAutomation/SQLChangeAutomation_4.5.22300.32307.exe
The bug has been identified and we're hoping it will be included in the next release of SQL Change Automation.
Kind regards,
Kurt McCormick
Product Support Engineer, Redgate
Need help? Take a look at our Help Center
https://documentation.red-gate.com/sca4/troubleshooting/logging-and-log-files
I have been advised the fix is confirmed to be in the next SQL Change Automation release. This should hopefully be released Thursday.
Kind regards,
Kurt McCormick
Product Support Engineer, Redgate
Need help? Take a look at our Help Center
SQL Change Automation v4.5.22313 has just been releases which should address this, please pull it down at your earliest convenience and let us know if it resolves your issue.
Glad you're up and running, have a good weekend.