Forum Replies Created
-
AuthorPosts
-
June 2, 2020 at 19:56 in reply to: "System.ObjectDisposedException: Cannot access a disposed object." #28318cwc-developerParticipant
Support,
Thank you for your prompt response!
We can add a new Linux project to a blank Visual Studio solution just not to the one that started throwing the error.
Tried deleting .vs folder and even the entire solution folder and pulling it again from Git – same error on adding a project to an existing solution.Switching to CMake is not a good option for us, since we have a number of projects relying on QMake in this solution, so it is a lot of effort to re-work the entire build system.
Is the workaround to copy-paste .vsgdbsettings files between those projects from different solutions? Are there any other workaround steps that should be performed?
Thank you, Alex
- This reply was modified 4 years, 5 months ago by cwc-developer.
June 2, 2020 at 19:21 in reply to: "System.ObjectDisposedException: Cannot access a disposed object." #28315cwc-developerParticipantIt has started happening with VisualGDB on my machine and also on another developer’s PC – pretty much simultaneously!
We both run VS2019 v16.4.5 and VisualGDB v5.4 R12.
The only common theme is that VisualGDB support has expired a few days ago, but it is still a fully licensed copy on both PC’s.
Does VisualGDB stop creating new projects within an existing solution if its support period has expired???
Please let us know what is the solution to this, because this sudden symptom on two separate computers looks very questionable.
Alex O.
VisualGDB version: 5.4.112.3309
—————— System.ObjectDisposedException ——————
System.ObjectDisposedException: Cannot access a disposed object.
Object name: ‘Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCConfigurationShim’.
at Microsoft.Verify.NotDisposed(Boolean condition, Object disposedValue, String message)
at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCConfigurationShim.<GetRuleAccessGeneralAsync>d__321.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCConfigurationShim.<GetConfigurationTypeAsync>d__287.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCConfigurationShim.<<get_ConfigurationType>b__56_0>d.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.ApartmentMarshaler.<>c__DisplayClass9_0`1.<<Invoke>b__0>d.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Threading.JoinableTask.CompleteOnCurrentThread()
at Microsoft.VisualStudio.Threading.JoinableTask`1.CompleteOnCurrentThread()
at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.ApartmentMarshaler.Invoke[TResult](Func`1 method)
at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCConfigurationShim.get_ConfigurationType()
at dg1.get_Configurations()
at bi2.u(fs1 e, IProjectEditContext a, h d, String c, String b, wi f)
at yn.k(LinuxWizardState c, fs1 b, String a, String e, pg d)
at yn.DoRunWizardOrThrowException(pg b, String a, String c)
at if2`1.Execute(Object d, Int32 c, Object[]& a, Object[]& e, wizardResult& b) -
AuthorPosts