none
One or more projects in the solution were not loaded correctly. Please see the Output Windows for details?

    Question

  • Dear All,

    How to fix the warning?

    VS 2017 is used, and no more information on Output Window

    Thanks and regards,

    E-John

    • Moved by CoolDadTx Tuesday, January 2, 2018 2:44 PM VS related
    Tuesday, January 2, 2018 6:08 AM

Answers

  • Hi CoolDadTX,

    This could be solved by following magic steps. (For my case)

    After following the steps, the warning message is gone. It is weird to me and don't know why.

    Thanks and regards,

    E-John

    https://stackoverflow.com/questions/6190402/visual-studio-warning-some-of-the-properties-associated-with-the-solution-coul

    I had the same problem, and my solution is:

    1. Open the solution in VS
    2. Set the Solution Platform to Default
    3. Save it
    4. Close the VS
    5. Open the .sln file in Notepad++ (or any other editor)
    6. Delete all of the other Solution Platform item from everywhere
    7. (for example:{73E03C8F-1F76-45E2-9D45-FA040A63F0AA}.Release|Any CPU.Build.0 = Release|Any CPU)
    8. Save it, and reopen the solution.

    This works for me.


    Thursday, January 4, 2018 5:47 AM

All replies

  • That means that VS was trying to load a project in your solution and couldn't. There are many reasons for this. You'll have to figure out which one applies to you.

    • The project type is not supported (common for older solutions). Also can be caused by not having the correct workload installed.
    • The project file is corrupt or missing.

    I would recommend that you first verify the project file actually exists by looking at which project didn't load. Then verify VS supports that project type by verifying it is an option in the New Project dialog.


    Michael Taylor http://www.michaeltaylorp3.net

    Tuesday, January 2, 2018 2:44 PM
  • Try changing the type of output using “Show output from” box, and check the details.

    Tuesday, January 2, 2018 4:45 PM
  • Hi Viorel,

    Where could I change this setting?

    Thanks and regards,

    E-John

    Wednesday, January 3, 2018 7:31 AM
  • Hi E-John,

    Does the project you opened was created in earlier version of visual studio?

    Please provide more information about the project, .net core project or something else....Besides, what item did you add to the project?

    Best regards,

    Joyce


    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.

    Wednesday, January 3, 2018 9:38 AM
  • Hi Joyce,

    It is VS2017 only. I don't old version Visual Studio 2015 or older installed.

    I remember I rename the namespace and file name, but I roll back it from my git repository, but still NOT work.

    This warning is pending for three months.

    Which file do you want? .sln or .csproj?

    Thanks and regards,

    E-John

    Thursday, January 4, 2018 12:52 AM
  • Look in Solution Explorer. Each project that failed to load in your solution will indicate Unloaded. Right click each one and try to load it. It'll display the error in the output window or message box if it fails to load. What is the type of each of those projects? 

    If this is a new solution and you stored things in Git then I'd go out on a limb and suspect that you didn't push all the project files to GitHub. But the error message will convey whether the project cannot be found or whether it failed to load. 

    Since you mentioned this has been going on for months then I'd also be interested in knowing what happened to cause this. Specifically, you added/created the project in the solution, then committed it to GitHub (presumably). At that point everything should be fine. But if you wiped or recloned your repo then those files were wiped. If you hadn't committed everything then at that point you'd be unable to load projects. Short of retrieving those files from some other source you'll have to recreate the projects manually.


    Michael Taylor http://www.michaeltaylorp3.net

    Thursday, January 4, 2018 4:57 AM
  • Hi CoolDadTX,

    This could be solved by following magic steps. (For my case)

    After following the steps, the warning message is gone. It is weird to me and don't know why.

    Thanks and regards,

    E-John

    https://stackoverflow.com/questions/6190402/visual-studio-warning-some-of-the-properties-associated-with-the-solution-coul

    I had the same problem, and my solution is:

    1. Open the solution in VS
    2. Set the Solution Platform to Default
    3. Save it
    4. Close the VS
    5. Open the .sln file in Notepad++ (or any other editor)
    6. Delete all of the other Solution Platform item from everywhere
    7. (for example:{73E03C8F-1F76-45E2-9D45-FA040A63F0AA}.Release|Any CPU.Build.0 = Release|Any CPU)
    8. Save it, and reopen the solution.

    This works for me.


    Thursday, January 4, 2018 5:47 AM
  • Hi E-John,

    Thank you for sharing the solution here.

    Could you please mark your reply as an answer which will be helpful for those who has the similar issue with you? Thank you for understanding.

    Best regards,

    Joyce


    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, January 4, 2018 5:57 AM
  • I copied the whole solution folder from OneDrive into my desktop and VS opened the solution no problem. I guess it makes no difference where will you copy the solution folder to as long as it's outside of OneDrive.
    Thursday, August 23, 2018 9:08 AM
  • Hi.

    In my case was very simple.

    I renamed de default project directory to a different than the one in the beginning.

    Y just put the original name and work just fine for me.


    • Edited by btejedaw2k Tuesday, August 28, 2018 10:12 PM
    Tuesday, August 28, 2018 10:11 PM
  • I had this same problem.  The problem for me was in the .sln file.  At the end of the file there were multiple of the following:

    GlobalSection(TeamFoundationVersionControl) = preSolution

    EndGlobalSection

    I deleted the extra ones and the message went away. 

    I believe the cause of this is when TFS merges different check-ins of the solution or someone does it manually and does it wrong.

    Paul


    • Edited by pslechta Thursday, September 20, 2018 7:49 PM
    Thursday, September 20, 2018 7:47 PM