locked
Visual Studio 2013 Ultimate Missing ADO.Net Entity Data Model / Designer RRS feed

  • Question

  • I just installed VS2013 Ultimate and tried both opening my project as well as creating a new project.  Neither one allows me to add a new ADO.NET Entity Data Model nor can I view my existing model in the designer.

    The template isn't in the list when trying to add and opening my existing only opens the xml.  I've tried right-clicking and open-with, however the designer is not an option in the list to select.

    I had this problem with using VS2013 Express for Web, but I cannot figure out how I fixed it.  Has anyone else experienced this and can help with a fix?

    I have attempted repairing.  I have not attempted a full re-install.  I have attempted a very thorough search online, but all results are for earlier versions of VS, and 2013 reportedly has EF built in. 

    Sunday, October 27, 2013 9:23 AM

Answers

  • Hi,

    First try resetting VS to the default settings with the following commands to see if it helps.

    1.devenv.exe /installvstemplates

    2.devenv.exe /resetsettings

    3.devenv.exe /resetuserdata

    Note that the above steps are unrelated and so checking if your issue has been resolved, after every step may help you save time on steps that were not required!

    If it can't solve your issue, I suggest you reinstall VS2013 Ultimate by these steps below.

    1. Update your windows and disable Anti-Virus software.

    On Windows 8.1 and Windows Server 2012 R2, KB2883200 (available through Windows Update) is required

    2. Use ISO file to install VS 2013 Ultimate. You can download the ISO file from the website below.

    http://go.microsoft.com/fwlink/?LinkId=320679

    Before you install it, I suggest you use this tool http://support.microsoft.com/kb/841290 to verify hash of the ISO. The point of the exercise is to generate a hash value (SHA1) from the ISO file so that it can be checked against the known value for that file. Any discrepancy would indicate that the file was corrupted.

    The sha1 value of ISO is “79DBBA7B6EF12B1A4E715A7F20951EE66FBCDAB4”.

    3.Clear your %temp% folder.
    The %temp% folder is a reference to the Temp folder associated with the current user. To clear it, do the following:
    Sign on to your system with the Administrator user account you will use to run the installer. Click the Start Orb and type %temp% in the search box. The search results will show the Temp folder you want. Click on the Temp folder to open it in Windows Explorer, then delete the entire contents.

    4.Run the setup file as administrator.

    Note: Just using an administrator account is not enough. To activate full privileges, you must right-click the installer, then select Run as administrator.

    5.If the installation fails, please use http://aka.ms/vscollect to gather the latest installation logs. After using it, you will find vslogs.cab from %temp% folder. Please upload the file to https://skydrive.live.com/ and share the link here.

    Best Regards.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    • Marked as answer by A_Li_N Wednesday, October 30, 2013 1:47 AM
    Tuesday, October 29, 2013 9:15 AM

All replies

  • Hi,

    First try resetting VS to the default settings with the following commands to see if it helps.

    1.devenv.exe /installvstemplates

    2.devenv.exe /resetsettings

    3.devenv.exe /resetuserdata

    Note that the above steps are unrelated and so checking if your issue has been resolved, after every step may help you save time on steps that were not required!

    If it can't solve your issue, I suggest you reinstall VS2013 Ultimate by these steps below.

    1. Update your windows and disable Anti-Virus software.

    On Windows 8.1 and Windows Server 2012 R2, KB2883200 (available through Windows Update) is required

    2. Use ISO file to install VS 2013 Ultimate. You can download the ISO file from the website below.

    http://go.microsoft.com/fwlink/?LinkId=320679

    Before you install it, I suggest you use this tool http://support.microsoft.com/kb/841290 to verify hash of the ISO. The point of the exercise is to generate a hash value (SHA1) from the ISO file so that it can be checked against the known value for that file. Any discrepancy would indicate that the file was corrupted.

    The sha1 value of ISO is “79DBBA7B6EF12B1A4E715A7F20951EE66FBCDAB4”.

    3.Clear your %temp% folder.
    The %temp% folder is a reference to the Temp folder associated with the current user. To clear it, do the following:
    Sign on to your system with the Administrator user account you will use to run the installer. Click the Start Orb and type %temp% in the search box. The search results will show the Temp folder you want. Click on the Temp folder to open it in Windows Explorer, then delete the entire contents.

    4.Run the setup file as administrator.

    Note: Just using an administrator account is not enough. To activate full privileges, you must right-click the installer, then select Run as administrator.

    5.If the installation fails, please use http://aka.ms/vscollect to gather the latest installation logs. After using it, you will find vslogs.cab from %temp% folder. Please upload the file to https://skydrive.live.com/ and share the link here.

    Best Regards.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    • Marked as answer by A_Li_N Wednesday, October 30, 2013 1:47 AM
    Tuesday, October 29, 2013 9:15 AM
  • Thank you for the response!
    I have since uninstalled Ultimate and reverted to the Express editions.  I likely wouldn't be able to afford the purchase by the time the trial ran out.

    However, your response led me to fixing similar issues (here) I was having with the Express for Web, changing the devenv.exe to VWDExpress.exe.  Once I ran those, I no longer was experiencing the similar problems.

    Thank you again for the response and help!

    Wednesday, October 30, 2013 1:47 AM