none
VS Designer Hangs on .aspx files

    Question

  • I am unable to get any .aspx file opened in designer mode.
    The error occurs whether I am using VS2015, VS2017, or VS2017RC.  Also occurs
    in both user and supervisor mode.
    I open a project solution (or create a new ASP.Net project) and VS loads it (or creates one). 
    But when I open any of the .aspx files and attempt to open using the designer feature
    I get error message from VS in a smaller window.
    =========================================
    Class not registered.
    Looking for object with CLSID:
    {583BAF91-C751-4D9E-8DB0-DAF81201F23F}.
    =========================================
    Looking at the registry for the object I find the following 6 entries with this CLSID:
    Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\14.0_Config\CLSID\{583BAF91-C751-4D9E-8DB0-DAF81201F23F}
    Computer\HKEY_USERS\.DEFAULT\Software\Microsoft\Blend\14.0_Config\CLSID\{583BAF91-C751-4D9E-8DB0-DAF81201F23F}
    Computer\HKEY_USERS\.DEFAULT\Software\Microsoft\VisualStudio\14.0_Config\CLSID\{583BAF91-C751-4D9E-8DB0-DAF81201F23F}
    Computer\HKEY_USERS\S-1-5-18\Software\Microsoft\Blend\14.0_Config\CLSID\{583BAF91-C751-4D9E-8DB0-DAF81201F23F}
    Computer\HKEY_USERS\S-1-5-18\Software\Microsoft\VisualStudio\14.0_Config\CLSID\{583BAF91-C751-4D9E-8DB0-DAF81201F23F}
    Computer\HKEY_USERS\S-1-5-21-2317499930-4218777071-2508544507-1001\SOFTWARE\Microsoft\VisualStudio\14.0_Config\CLSID\{583BAF91-C751-4D9E-8DB0-DAF81201F23F}
    All of them have the same data fields and contents:
    Name            Type       Data
    (Default)       REG_SZ     CLSID_CFPACEditor Class
    InprocServer32  REG_SZ     C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Ppackages\fpeditax.dll
    Once this error occurs the source window is unusable and the designer never comes up. The only way to
    continue editing is to close the pane and reload the source files (but I can never get the designer started). 
    The hangup also occurs in split mode.
    Does anyone have any fixes for the problem noted above or can anyone point me towards a solution??
    Thank you.
    Joseph Aquilino
    Wednesday, February 22, 2017 9:41 PM

Answers

  • Fletch,

    Thanks for the key to the solution.

    There were 2 issues. 

    First, I had to repair my installation of VS.  Unfortunately, it did not work due to some directory that was in Read-Only Mode.  I changed that directory to be read-write and restarted the Repair and it worked.

    The designer and split works now!

    Joseph Aquilino

    Thursday, February 23, 2017 11:29 PM

All replies

  • Hi Joseph,

    Thanks for your re-opening this post here.

    According the description above, which the dll file could not be re-registered by using regsvr32, and now the new project also suffers this issue.

    I suggest you repair your VS and then try to open the designer mode again.  

    http://stackoverflow.com/questions/35728353/design-split-hanging-in-webform

    This thread is almost as yours, and the original poster resolved this by repairing the VS, which might be useful to you.

    Best regards,

    Fletch


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, February 23, 2017 6:29 AM
  • Fletch,

    Thanks for the key to the solution.

    There were 2 issues. 

    First, I had to repair my installation of VS.  Unfortunately, it did not work due to some directory that was in Read-Only Mode.  I changed that directory to be read-write and restarted the Repair and it worked.

    The designer and split works now!

    Joseph Aquilino

    Thursday, February 23, 2017 11:29 PM
  • Hi Joseph,

    I'm glad your issue has been solved, that's great.

    Best regards,

    Fletch


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, February 24, 2017 1:19 AM