 |
SoftTree Technologies
Technical Support Forums
|
|
Author |
Message |
sloth
Joined: 23 Mar 2009 Posts: 1 Country: Australia |
|
BUG : SQLAssistant and Visual Studio 2005 Team Edition |
|
Using Visual Studio 2005 Team Edition with SQL Assist 4.5.9 installed.
I went to Team -> Team Project Settings -> Group Membership.
I then went to the Properties of a group.
Selected Windows User or Group
Clicked Add
Proceeded to type in the domain (got to c in the picture) and the SQL Assist kicked in
SQL Server 2005 is currently installed.
Trial version of SQL Assist 4.5.9

|
|
Mon Mar 23, 2009 11:26 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
This is ok. For Visual Studio (VS) and all derivative products, SQL Assistant is configured to monitor 2 window classes VsTextEditPane and RichEdit20W. This window classes are used by VS for code editing and it also happens that RichEdit20W is used in the dialog for user selection.
---
If you edit users permissions often and don't want SQL Assistant to activate in that edit box, you can use either of the following:
1. Whenever you need to modify user permissions, use regular method for managing users and permissions which is Windows Control Panel -> Admin Tools -> Computer Management -> Local Users and so on…
or
2. Modify Visual Studio target options in SQL Assistant settings and remove RichEdit20W class. You can find this in Advanced section of target options for Visual Studio target. This will make SQL Assistant appear only in edit windows having class VsTextEditPane (I don't recommend that)
or
3. When working with Select Users and Groups dialog, right-click in the edit and choose SQL Assistant menu and then choose Suspend command. When you are done, use right-click in the SQL code editor and then Resume command.
|
|
Tue Mar 24, 2009 12:57 am |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|