NullReferenceException when opening solution in Visual Studio

5 posts, 0 answers
  1. Jon
    Jon avatar
    14 posts
    Member since:
    Nov 2015

    Posted 01 Nov 2019 Link to this post

    Hello all,

    I am looking for help with an issue I'm having after installing Visual Studio 2019. I had Visual Studio 2017 previously installed on this system. The Test Studio extension was also installed and in good working order. Once I was done installing Visual Studio 2019, I uninstalled and reinstalled Test Studio so that I would get the extension. I believe this is when the problem started. When attempting to open a project/solution (does not matter if it's a brand new fresh project or a pre-existing one), I see the "Locating Tests...." in the Output Window, followed by "Upgrading project..." and then the crash happens. Loading the project works fine in Test Studio IDE.

    I have attempted the following to fix:

    • Uninstalled all versions of Visual Studio and Test Studio, then re install Visual Studio 2019, then Test Studio. I restarted the PC after each un/reinstallation.
    • Uninstalled Visual Studio using Revo Uninstaller and used CCleaner between each uninstall to ensure all extraneous files and registry entries were cleaned up, then reinstalled Visual Studio, then Test Studio.
    • Tried loading a fresh new project created via Visual Studio.
    • Tried loading a fresh new project created via Test Studio.

    The following is the error message found in the Event Viewer, I have more debug information if required:

    Application: devenv.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.NullReferenceException
       at ArtOfTest.WebAiiVSIP.ProjectModel.ImportFiles.ImportFilesController.GetTestDiffFiles(ArtOfTest.WebAii.Design.ProjectModel.Project)
       at ArtOfTest.WebAiiVSIP.ProjectModel.ImportFiles.ImportFilesController.Import(ArtOfTest.WebAii.Design.ProjectModel.Project)
       at ArtOfTest.WebAiiVSIP.ProjectModel.VSProject.LightProject_LightProjectLoaded(ArtOfTest.WebAii.Design.ProjectModel.Project)
       at ArtOfTest.WebAii.Design.ProjectModel.Providers.Modules.LightProjectModule.OnProjectLoaded(ArtOfTest.WebAii.Design.ProjectModel.Project)
       at ArtOfTest.WebAii.Design.ProjectModel.Providers.FileSystemProvider.<OnBeforeProjectLoad>b__123_0()
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.DispatcherOperation.InvokeImpl()
       at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
       at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Windows.Threading.DispatcherOperation.Invoke()
       at System.Windows.Threading.Dispatcher.ProcessQueue()
       at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

     

    Application Error information:

    Faulting application name: devenv.exe, version: 16.3.29424.173, time stamp: 0x5db24333
    Faulting module name: KERNELBASE.dll, version: 10.0.16299.1004, time stamp: 0x690aa820
    Exception code: 0xe0434352
    Fault offset: 0x00104622
    Faulting process id: 0x3ed8
    Faulting application start time: 0x01d590f31f3c6ae5
    Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\devenv.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report Id: aba74370-4a0b-476f-8dc8-21ad7c996e88
    Faulting package full name: 
    Faulting package-relative application ID: 

     

    Thanks for any help!

    Jon

  2. Jon
    Jon avatar
    14 posts
    Member since:
    Nov 2015

    Posted 04 Nov 2019 in reply to Jon Link to this post

    After further efforts I have been able to get the extension running again. I ended up having to download and advanced registry editor program and comb through the registry, deleting all keys and stores related to Telerik/Test Studio. Once I did that, restart the computer and reinstalled Test Studio one last time, I was able to open the extension in Visual Studio with no crashes. So far things are working as expected. Hopefully this helps someone else in the future.

    To the devs--you may want to do some more testing around which registry entries get added/removed during installation/uninstallation and how those entries have changed over time. I noticed there were some old registry entries from previous installs when I was combing through the registry. As a developer I understand how difficult it can be to keep track of what all gets added when the software is installed and what all needs to be cleaned up when software is uninstalled. Just some feedback to avoid more posts like these.

    Regards,

    Jon

  3. Elena
    Admin
    Elena avatar
    1222 posts

    Posted 06 Nov 2019 Link to this post

    Hi Jon,

    Thank you for getting back to us with details of what helped you resolve the installation issue -  I also granted your Telerik account with 500 points as a small reward from our side. 

    I suspect that there was something wrong in the initial uninstall that you have performed. And then you observed the rest of the troubles with performing the different installations. Currently you have completely new installations for both Test Studio and Visual Studio, so it won't be an option to explore what might have gone wrong. 

    Apart from that, I will share your note to the developers team, but I am wondering if you can provide details for which were the keys you needed to delete in the registry. You mentioned Telerik/Test Studio, which is not supposed to be left over and we will continue the investigation internally. Were there any other keys that you removed?

    Thank you once again for your efforts on the case.

    Regards,
    Elena
    Progress Telerik

     
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
     
  4. Jon
    Jon avatar
    14 posts
    Member since:
    Nov 2015

    Posted 06 Nov 2019 in reply to Elena Link to this post

    Thanks for the points Elena.

     

    Unfortunately I did not take the time to reinstall after deleting each key one by one to determine which keys were giving me problems. I could possibly get the backup of the registry and compare it against my current registry and see what's different, but I deleted 60+ entries so I don't know how much it would help. I have had many versions of Test Studio and Visual Studio on this workstation over the past 3 years, so I was probably a corner case, but I thought I would at least give the information I had.

     

    Thanks,

    Jon

  5. Elena
    Admin
    Elena avatar
    1222 posts

    Posted 06 Nov 2019 Link to this post

    Hi Jon,

    Please, don't bother that you didn't collect any specific details - after all you were trying to get a successful installation and luckily managed to. 

    As I mentioned I will share your feedback with the development team and we will try to reproduce and investigate similar misbehavior.

    Thanks once again for your cooperation.

    Regards,
    Elena
    Progress Telerik

     
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
     
Back to Top