Entity Framework edmx click on diagram very slow

后端 未结 5 1386
鱼传尺愫
鱼传尺愫 2021-02-01 05:48

Background first: I have a database-first EF6 model in Visual Studio 2015 (latest nuget 6.1.3 pointing to a local SQL Server 2014 SP1 Express database) on a Windows 10 Pro lapto

相关标签:
5条回答
  • 2021-02-01 06:32

    We had the same issue on 2 laptops with Windows 10 and touchscreens. Killing the process TabTip.exe seems to solve the issue.

    Source: https://connect.microsoft.com/VisualStudio/Feedback/Details/2011437

    Go Task Manager and End Process on TabTip.exe (Touch Keyboard and Handwriting Panel). After doing that the designer will respond fine. Note if you click or touch the Keyboard icon in the TaskBar the TabTip.exe will re-start.

    0 讨论(0)
  • 2021-02-01 06:33

    I can't comment as I'm just under the minimum comment reputation, however I have been having exactly the same issue.

    Like you, I re-installed Windows 10 (Enterprise) and Visual Studio (both 2013 Pro and 2015 Pro) to no avail.

    For the moment, I've put this on the back-burner and am working around it by using a combination of DevArt's Entity Developer (https://www.devart.com/entitydeveloper/) and manually editing the classes to match database changes.

    It is tedious, and not a lot of fun - but it works for me (for the moment).

    Hopefully this helps someone.

    Edit:

    For anyone who may come across this post in the future, the following appears to have solved this issue for me:

    • Navigate to Tools > Options > General
    • Untick "Automatically adjust visual experience based on client performance"
    • Untick "Use graphics acceleration if available"

    Though you may not have to, I left "Enable rich client visual experience" unticked.

    If this doesn't work, take a look at the comments below this answer - it might be of use. :)

    Source: http://pinter.org/?p=2611

    Edit 2:

    My issue came back, and after further investigation it appears that it was caused by Remote Desktop (I am currently using an ESXi-hosted Windows 10 VM). Switching to VNC or using the VMWare VSphere Web Console results in Visual Studio running perfectly fine. Hopefully this helps someone! :)

    0 讨论(0)
  • 2021-02-01 06:34

    I tried the accepted answer and it did work for me, however the issue returned on restart. I also tried the other answers with no success. I found the offending windows service and used Windows 10 services management screen to disable the service. I hope this is helpful to others with this issue.


    How to disable the service fully

    Disable the service:

    1. User windows start search (by the start menu) and type in: Services
    2. You should see a windows desktop app called Services (open it).
    3. Find the services called "Touch Keyboard and Handwriting Panel Service".
    4. Open its properties, (by right clicking it).
    5. Under the General tab set the startup type to "Disabled".
    6. Stop the service if if it has not stooped already.

    Verification:

    1. Open Visual Studio's EDMX and you should notice the difference right-away, if not then you may not have the same issue as me.
    2. Restart your computer and test the EDMX again, it should not be slow.

    Note: This does mess with your gesture and touch pad a bit, so if you use that a lot then don't do this. This guide is for windows 10, and worked for me but may not work for you. Also I have not tested if Windows update will re-enable the service.

    0 讨论(0)
  • 2021-02-01 06:35

    if you have installed the extension productivity power tools, then disable it before you start to work with entityframework diagrams, then inable it when your done. i dont get into my entityframework diagrams very often, so this worked for me.

    0 讨论(0)
  • 2021-02-01 06:36

    This is an issue with Microsoft.VisualStudio.Modeling.Sdk on Windows 10 and also affects the LINQ to SQL (DBML) designer. The team that owns the VS Modeling SDK is currently working on this. We have an issue tracking it on the EF project site https://entityframework.codeplex.com/workitem/2861. We will keep that issue updated with progress, availability of a fix, workarounds, etc.

    0 讨论(0)
提交回复
热议问题