none
Projects created in VS 2013 Ultimate and opened in VS 2017 Pro won't work in either now.

    Question

  • I just installed Visual Studio 2017 Professional. I still have Visual Studio 2013 Ultimate installed. Both have all the latest updates. Now I'm having some peculiar problems opening and working with projects, all of which are C# .NET WinForms projects created in VS 2013 Ultimate:

    1. VS 2013 Ultimate crashes when I try to open a project regardless of whether or not the project was created with VS 2013 Ultimate.

    2. I can open a VS 2013 Ultimate project in VS 2017 Pro, but if I add, say, a Windows Form with a picture box and then add an animated GIF to the picturebox, the GIF won't animate. Also, I can't get code in background workers to execute in VS 2017 Pro. If I create a new project in VS 2017 Pro, however, it works just fine.

    Did something in VS 2013 Ultimate get corrupted by the VS 2017 Pro installation? Is something suited for VS 2013 Ultimate being used by mistake in VS 2017 Pro or vice versa? I tried running a Repair on VS 2013 Ultimate, uninstalled VS 2017 Pro and THEN tried opening a project in VS 2013 Ultimate, but the problems persist. Is there something I can do with settings in either/both IDE's or something I can change in VS 2013 projects so they'll work properly in VS 2017?
    • Edited by WikiGrrrl Sunday, April 09, 2017 7:28 PM typo
    Sunday, April 09, 2017 5:52 PM

All replies

  • WikiGrrrl

                I would recommend to check the logs of VS2013 in that case and of VS2017 too.

    You can leverage help from here


    Mark Answered, if it solves your question and Vote if you found it helpful.
    Rohit Arora

    Monday, April 10, 2017 3:39 AM
  • Thanks for your response, RohitArora. Below is the log file. I couldn't paste the whole thing, but these entries look like they might indicate what the problem is.
    <?xml version="1.0" encoding="utf-16"?>
    <?xml-stylesheet type="text/xsl" href="ActivityLog.xsl"?>
    <activity>
      <entry>
        <record>751</record>
        <time>2017/04/10 23:22:37.993</time>
        <type>Information</type>
        <source>Profile manager</source>
        <description>Not exporting category &apos;CoffeeScript_CoffeeLint&apos; ({d87c87c9-b788-4c01-9d3c-78cdda5ee60e}) from package &apos;CoffeeScriptPackage&apos; ({52244C9D-DB46-4905-BDA0-B3406C46D2A4}) because the package is not loaded and no imported settings are available for copy-export.  Packages will not be loaded for export during shutdown.</description>
      </entry>
      <entry>
        <record>752</record>
        <time>2017/04/10 23:22:37.993</time>
        <type>Information</type>
        <source>Profile manager</source>
        <description>Not exporting category &apos;CSS_CssLint&apos; ({4f8c9198-522a-48e6-bfa8-e704f98b88ee}) from package &apos;CssPackage&apos; ({5330C67F-305C-4B17-A3DC-FBB7AEE69C09}) because the package is not loaded and no imported settings are available for copy-export.  Packages will not be loaded for export during shutdown.</description>
      </entry>
      <entry>
        <record>753</record>
        <time>2017/04/10 23:22:37.993</time>
        <type>Information</type>
        <source>Profile manager</source>
        <description>Not exporting category &apos;TypeScript_EsLint&apos; ({a9135013-531c-4a70-9782-02836a29dcf2}) from package &apos;JavaScriptWebExtensionsPackage&apos; ({30DB8F9B-EC9F-44D6-B377-83C7C27A1A8B}) because the package is not loaded and no imported settings are available for copy-export.  Packages will not be loaded for export during shutdown.</description>
      </entry>
      <entry>
        <record>754</record>
        <time>2017/04/10 23:22:37.994</time>
        <type>Information</type>
        <source>Profile manager</source>
        <description>Not exporting category &apos;Web_Code Analysis&apos; ({fa109e91-2d0d-4251-bce1-02a4e92cde10}) from package &apos;WebEditorPackage&apos; ({72C65C2E-977E-4E9C-A422-F2743D2BDD43}) because the package is not loaded and no imported settings are available for copy-export.  Packages will not be loaded for export during shutdown.</description>
      </entry>
      <entry>
        <record>755</record>
        <time>2017/04/10 23:22:37.994</time>
        <type>Information</type>
        <source>Profile manager</source>
        <description>Not exporting category &apos;Work Items_TeamFoundation&apos; ({89E620E1-9593-402C-905A-B1944CED0C38}) from package &apos;Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPackage, Microsoft.VisualStudio.TeamFoundation.WorkItemTracking&apos; ({CA39E596-31ED-4B34-AA36-5F0240457A7E}) because the package is not loaded and no imported settings are available for copy-export.  Packages will not be loaded for export during shutdown.</description>
      </entry>
      <entry>
        <record>756</record>
        <time>2017/04/10 23:22:38.295</time>
        <type></type>
        <source>VisualStudio</source>
        <description>Destroying Main Window</description>
      </entry>
      <entry>
        <record>757</record>
        <time>2017/04/10 23:22:38.942</time>
        <type>Information</type>
        <source>VisualStudio</source>
        <description>AppId stopped registry detouring</description>
      </entry>
      <entry>
        <record>758</record>
        <time>2017/04/10 23:22:38.942</time>
        <type>Information</type>
        <source>VisualStudio</source>
        <description>Shutting down pkgdef registry</description>
      </entry>
      <entry>
        <record>759</record>
        <time>2017/04/10 23:22:38.942</time>
        <type>Information</type>
        <source>VisualStudio</source>
        <description>PkgDef registry shutdown complete</description>
      </entry>
    </activity>
    

    Monday, April 10, 2017 11:36 PM
  • Hi WikiGrrrl,

    Welcome to the MSDN forum.

    Usually, we discuss one question in one thread, it can help us to focus on this issue and trace it, thank you for your understanding.

    Basically, the VS 2013, VS 2015 and VS 2017 can work side by side with each other.

    >> 1. VS 2013 Ultimate crashes when I try to open a project regardless of whether or not the project was created with VS 2013 Ultimate.

    The crash behavior only happens when you open an existing project with the specific project type or any types?

    Except open the existing projects, does the crash issue occurs for other actions in VS 2013?

    Please have a try with the following to troubleshot this issue:

    Open the VS ultimate 2013 installation location, usually locates C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE and run the following commands:

    devenv /resetuserdata: clear the old user data

    devenv /safemode: run the VS as safe, if it works fine that means the installed extensions may be corrupted the VS, please go to Tool—Extensions and Updates… and remove all installed extensions one by one to find the culprit.

    If the crash issue persists, please go to Event Viewer to check if there has any error message and share it in here, it will help us to analysis this crash issue, thank you for your coopearation.

    >> 2. I can open a VS 2013 Ultimate project in VS 2017 Pro, but if I add, say, a Windows Form with a picture box and then add an animated GIF to the picturebox, the GIF won't animate. Also, I can't get code in background workers to execute in VS 2017 Pro. If I create a new project in VS 2017 Pro, however, it works just fine.

    Refer to your description, this issue is more relates to the development of Windows Form. Since our forum is to discuss Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor. Please redirect to this appropriate forum: https://social.msdn.microsoft.com/Forums/windows/en-US/home?forum=winforms and start a new thread to seek for a professional support and it will help you to quickly solve your issue.

    Sorry for this inconvenience and thank you for your understanding.

    Best regards,

    Sara


    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.

    Tuesday, April 11, 2017 3:11 AM
    Moderator
  • Looks like an issue with extension packages. try removing them.

    Mark Answered, if it solves your question and Vote if you found it helpful.
    Rohit Arora

    Tuesday, April 11, 2017 3:29 AM