Closed omni-htg closed 2 weeks ago
Hello @omni-htg,
I attempted to repo the issue myself and was unable. There is a chance there might be some more info logged in the <ProjectDirectory>\obj\Container\ContainerToolsExceptions.json
file but I'm doubtful.
Two things that could help narrow down what the issue might be: 1) Upgrade to VS 17.10 and see if the issue persists. 2) Downgrade the ContainerTools NuGet to 1.19.6
If none of those seem to help, I think I'll need a dump file to debug what is going on. When the exception occurs, at the top of VS select Help -> Send Feedback -> Report A Problem
then open an issue on developer community. There you can upload files/messages privately.
Hey @patverb ! We can try tomorrow, see where it takes us.
I'll need a dump file to debug what is going on
How can we generate this?
Thanks!
Hello @patverb ! Apologies for the delay. They have updated VS to 17.10.2 and now it doesn't throw the exception again, so we can close this issue out.
When I have time in the following days I will try to install that version of VS again and run the project that failed to try and fish out the <ProjectDirectory>\obj\Container\ContainerToolsExceptions.json
file.
Thank you for your assistance.
Similar to the experience in #276 , my coworker is currently experiencing this error:
when trying to start debugging a project from the first time they open the solution. In order to make it work, they have to Uninstall and Install the package.
They do have a
%Temp%\Microsoft.VisualStudio.Containers.Tools
folder, but after triggering the issue again, no log has been generated.In any case, I can provide the latest entries found in the
%Temp%\Microsoft.VisualStudio.Containers.Tools
folder:And the
%Temp%\Microsoft.VisualStudio.Containers.Tools.Extensions
folder:Their environment is:
Thank you for your assistance!