Unloading the selected projects hangs
Whenever I attempt to close the solution Visual Studio hangs, displaying a dialog containing the message, "Unloading the selected projects...".
I am running MS VS Community 2917 RC, VisualStudio/15.0.0-RC.4+26206.0.
My Visual Basic/C#/C++ components are reported as 00369-50000-00000-AA307.
I have opened up a very old solution (i.e., generated by Visual Studio several versions back) that contains 5 projects. One of the projects, an old CHM Help file project, is listed as "(incompatible)" in the Solution Explorer panel when the solution is open.
Add Comment
Thank you for submitting feedback. In order to efficiently investigate and reproduce this issue, could you please give us an ETL trace file so that we can conduct further research?
You are able to get the files with the following steps:
Download and extract PerfView.exe. http://www.microsoft.com/en-us/download/details.aspx?id=28567
Run PerfView.exe collect /zip:true /nogui /threadtime:true /AcceptEULA from an elevated command prompt. This will launch another windows and begin tracing.
Reproduce the hang that occurs.
Press S on the window that showed up in step 2. This will generate a file called PerfViewData.ETL.ZIP.
Upload your PerfViewData.ETL.ZIP by choosing insert file tag on add comment field then submit after signing in.
We look forward to hearing from you with this information.
Thank you for your feedback! In order for us to investigate this further, could you please provide your issue project for us so that we can reproduce this issue on our side?
I can't provide the actual project. I will attempt to pare it down to something that will reproduce the failure, but that may take some time to get to...
I can confirm that this is still an issue with the release version of Visual Studio.
I've reproduced this for you in PerfViewer here with latest Visual Studio 2017 update.
26228.12
Thank you for your feedback! We have fixed the problem in an upcoming release. Thank you for helping us build a better Visual Studio!
Oh, ok. The release notes indicated this was fixed in 26228.10, so just wanted to let you know it was still an issue. Maybe that was included by mistake.
