[UnrealVSPackage]Source: ‘UnrealVS’ Description: Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at UnrealVS.Utils.GetProjectConfigProperty(Project Project, Configuration Configuration, String PropertyName) at UnrealVS.CommandLineEditor.GetProjectCommandLineProperty(Project InProject) at UnrealVS.CommandLineEditor.MakeCommandLineComboText() at UnrealVS.CommandLineEditor.UpdateCommandLineCombo() at UnrealVS.CommandLineEditor…ctor() at UnrealVS.UnrealVSPackage.Initialize() at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.Shell.Interop.IVsPackage.SetSite(IServiceProvider sp)
I have not yet been able to reproduce any issues with UnrealVS in Visual Studio 2017 Community RC. There is likely some small detail that I am missing. I’ll outline what I did, and if you could let me know where you are doing things differently, that would be very helpful.
Download 4.15.0 source code from GitHub as a .zip file.
Extract the source code.
Run Setup.bat.
Use a commandline to run GenerateProjectFiles.bat -2017.
Verified that a VS 2017 UE4.sln file was created.
Navigate to Engine/Extras/UnrealVS/VS2017 and double-clicked the UnrealVS.vsix file to install UnrealVS in Visual Studio. This does display a prompt that the addon may be unstable, but the installation was successful.
Double-clicked the UE4.sln file to open the solution in Visual Studio 2017.
Verified that the expected UnrealVS toolbar was present.
Clicked the Batch Builder button to open the Batch Builder window and verified that all of the Project, Config, and Platform options were present.
Clicked the Refresh button to refresh the projects (this changed the UE4.sln from VS 2017 to VS 2015, which I suspect may not be correct behavior, but doesn’t sound like the issue you described).
In the past couple days we have had a few engineers report having issues with UnrealVS internally. We were able to reliably reproduce the issue, and have entered UE-42756 to have this looked into. An update to UnrealVS was already being worked on, and I suspect that this update will resolve the trouble that you were experiencing.