Hello.
When I’m trying to edit some entity (by example, name of class) SDE and VS frezes and do not responses any keyboard and mouse actions. But VP Suite 2.2 works fine. How can I solve this problem?
OS: Windows XP Professional SP2
VS2005 Professional
SDE 3.2(20060304a)
JDK 5.0
Yes, the problem on former remained.
For instance, I do following:
Start SDE through shortcut.
Open my existing solution.
Right click on a project “DataSetMerging” in solution and select “Open SDE-VS” menu item.
Then, I go to Model window and right click on the “DataSetMerging” node.
Select Add Model\Package item in popup menu. New package “Package” appears in Model window
Right click on new package and select Open Package Specification… menu item.
Then, when “Name” edit box in focus and I press any key (including Ctrl , Shift etc) but not mouse keys, “Package Specifictaion” dialog freezes and VS freezes too. And I can terminate this one only by Task Manager.
I has been tryed on diffrent computers, with VS2005 installed on clear OS and after VS2005 beta2. Everywhere this problem repeats. vp.log
Thanks for your reply. I tried in my machine with Beta2 but failed to repeat the problem. I have just passed your case on to our engineers for further testing. Once there is any progress, I will post here.
We checked that the problem of freezes in VS .NET could be caused by other running applications. Could you please try killing other applications when VS .NET freezes again to see if it can help? If you found any application that causes VS .NET to freeze, please let me know. Thank you.
I found one program that causes VS freeze - ABBYY Lingvo (I have version 10.0). This is multilanguage dictionary that registers its own global windows event hook… Maybe this feature causes VS.NET freeze?..
Well, I don’t remember exact name but I believe that it must be lingvo.exe or maybe lingvolauncher.exe or maybe just launcher.exe… Now I have uninstalled this program because I don’t really need it And how it’s name may help you? If you have Lingvo-distr just install it, if you don’t have it…
Thank you for your posts. We will install Lingvo and test with it. The process name is helpful for us to identify the problem with users by checking whether the Lingvo process is running.