Are it Not support on Window Vista?

• 
  I can confirm this is happening in Vista RC1 using both SQL2005 Management Studio and Visual Studio 2005

  riceboyler September 27, 2006 09:29

  - 0 +
• 
  I also have the same problem (SQL Prompt will not insert any text) on Windows Vista. This seemed mysterious until I went into the Snippet Editor and clicked Test Snippet. Doing so resulted in this message box:
  

  ---

  SQL Prompt

  ---

  There was an error trying to send the code to the text box

  ---

  OK

  ---

  
  After clicking OK, another dialog box appeared, with 3 buttons: Details, Continue, and Quit, and this text:
  

  The application attempted to perform an operation not allowed by the security policy. The operation required the SecurityException. To grant this application the required permission please contect your system administrator, or use the Microsoft .NET security policy administration tool.
  
  If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will be shut down immediately.
  
  Unable to create hook.

  
  Clicking the Details button shows this text:
  

  See the end of this message for details on invoking
  just-in-time (JIT) debugging instead of this dialog box.
  
  ************** Exception Text **************
  System.Security.SecurityException: Unable to create Hook.
  at System.Windows.Forms.SendKeys.InstallHook()
  at System.Windows.Forms.SendKeys.Send(String keys, Control control, Boolean wait)
  at System.Windows.Forms.SendKeys.Send(String keys)
  at _37._1(Object , EventArgs )
  at System.Windows.Forms.Control.OnClick(EventArgs e)
  at System.Windows.Forms.Button.OnClick(EventArgs e)
  at System.Windows.Forms.Button.WndProc(Message& m)
  at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
  at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
  at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
  
  
  ************** Loaded Assemblies **************
  mscorlib
  Assembly Version: 1.0.5000.0
  Win32 Version: 1.1.4322.2032
  CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll

  ---

  RedGate.SQLPrompt
  Assembly Version: 2.0.0.59
  Win32 Version: 2.0.0.59
  CodeBase: file:///C:/Program%20Files/Development/SQL%20Prompt/RedGate.SQLPrompt.exe

  ---

  System.Windows.Forms
  Assembly Version: 1.0.5000.0
  Win32 Version: 1.1.4322.2032
  CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll

  ---

  System
  Assembly Version: 1.0.5000.0
  Win32 Version: 1.1.4322.2032
  CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll

  ---

  System.Drawing
  Assembly Version: 1.0.5000.0
  Win32 Version: 1.1.4322.2032
  CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll

  ---

  RedGate.SQL.Shared
  Assembly Version: 5.2.0.2
  Win32 Version: 5.2.0.2
  CodeBase: file:///C:/Program%20Files/Development/SQL%20Prompt/RedGate.SQL.Shared.DLL

  ---

  System.Xml
  Assembly Version: 1.0.5000.0
  Win32 Version: 1.1.4322.2032
  CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll

  ---

  System.Data
  Assembly Version: 1.0.5000.0
  Win32 Version: 1.1.4322.2032
  CodeBase: file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll

  ---

  RedGate.Update.Client
  Assembly Version: 1.2.0.3
  Win32 Version: 1.2.0.3
  CodeBase: file:///C:/Program%20Files/Development/SQL%20Prompt/RedGate.Update.Client.DLL

  ---

  System.Web.Services
  Assembly Version: 1.0.5000.0
  Win32 Version: 1.1.4322.2032
  CodeBase: file:///c:/windows/assembly/gac/system.web.services/1.0.5000.0__b03f5f7f11d50a3a/system.web.services.dll

  ---

  System.Web
  Assembly Version: 1.0.5000.0
  Win32 Version: 1.1.4322.2032
  CodeBase: file:///c:/windows/assembly/gac/system.web/1.0.5000.0__b03f5f7f11d50a3a/system.web.dll

  ---

  mqr8phi7
  Assembly Version: 0.0.0.0
  Win32 Version: 1.1.4322.2032
  CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll

  ---

  System.EnterpriseServices
  Assembly Version: 1.0.5000.0
  Win32 Version: 1.1.4322.2032
  CodeBase: file:///c:/windows/assembly/gac/system.enterpriseservices/1.0.5000.0__b03f5f7f11d50a3a/system.enterpriseservices.dll

  ---

  antlr.runtime
  Assembly Version: 2.7.5.2
  Win32 Version: 2.7.5.2
  CodeBase: file:///C:/Program%20Files/Development/SQL%20Prompt/antlr.runtime.DLL

  ---

  
  ************** JIT Debugging **************
  To enable just in time (JIT) debugging, the config file for this
  application or machine (machine.config) must have the
  jitDebugging value set in the system.windows.forms section.
  The application must also be compiled with debugging
  enabled.
  
  For example:
  
  <configuration>
  <system.windows.forms jitDebugging="true" />
  </configuration>
  
  When JIT debugging is enabled, any unhandled exception
  will be sent to the JIT debugger registered on the machine
  rather than being handled by this dialog.

  
  I tried to use the ".NET Configuration 1.1" control panel applet to give SQL Prompt the appropriate permission, but gave up after trying several things, the most promising of which was creating a Code Group for SQL Prompt, with a membership condition of SQL Prompt's Strong Name and the FullTrust permission group. But, like I said, that didn't work.

  bis November 30, 2006 23:36

  - 0 +
• 
  Hi guys,
  
  I'm afraid SQL Prompt 2 does not support Vista. SQL Prompt 3, which comes out shortly, will support Vista, however.
  
  Regards,
  
  Tilman

  Tilman December 04, 2006 05:05

  - 0 +

Add comment

Please sign in to leave a comment.