Comments
3 comments
-
Hello Antonio,
Thanks for your inquiry and sorry to hear about your issue with SQL Prompt.
Can you confirm if you've uninstalled SQL Prompt from Control Panel/Programs and Features?
Can you confirm if you still have any leftover folders and files from the following directories?
C:\Users\username\AppData\Local\Red Gate\SQL Prompt 10
C:\Program Files (x86)\Red Gate\SQL Prompt 10
C:\ProgramData\Red Gate\SQL Prompt 10
Thanks! -
Thank you for your response. I reinstalled SQL Prompt (same as first time) and unistalled again (same as first time) and now I'm no longer getting the error messages. Maybe issue was that during the first unistall Visual Studio was not closed.
Answering above questions:
Can you confirm if you've uninstalled SQL Prompt from Control Panel/Programs and Features? Yes - unistall was via Control Panel
Can you confirm if you still have any leftover folders and files from the following directories? - none of the below exist
C:\Users\username\AppData\Local\Red Gate\SQL Prompt 10
C:\Program Files (x86)\Red Gate\SQL Prompt 10
C:\ProgramData\Red Gate\SQL Prompt 10
-
I'm also receiving an error in VS2022 after uninstalling SQLPrompt that the 'SQLPromptPackage' package did not load correctly. The program was uninstalled using Windows' "Add or remove program" control panel after its subscription expired. Restarted VS, restarted Windows, and deleted leftover folders, but each time I start VS, I get that annoying dialog that package did not load correctly. Please help.
Add comment
Please sign in to leave a comment.
Thanks,
-antonio
CreateInstance failed for package [SQLPromptPackage]Source: 'mscorlib' Description: Could not load file or assembly 'file:///C:\Program Files (x86)\Red Gate\SQL Prompt 10\RedGate.SqlPrompt.VsPackage2022.dll' or one of its dependencies. The system cannot find the file specified. System.IO.FileNotFoundException: Could not load file or assembly 'file:///C:\Program Files (x86)\Red Gate\SQL Prompt 10\RedGate.SqlPrompt.VsPackage2022.dll' or one of its dependencies. The system cannot find the file specified. File name: 'file:///C:\Program Files (x86)\Red Gate\SQL Prompt 10\RedGate.SqlPrompt.VsPackage2022.dll' at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark) at System.Reflection.Assembly.LoadFrom(String assemblyFile, Evidence securityEvidence) at System.Activator.CreateInstanceFromInternal(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo) at System.AppDomain.CreateInstanceFrom(String assemblyFile, String typeName) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].