Test host can explode when dependencies change now

[davidfowl]

------ Discover test started ------
------ Test started: Project: ClassLibrary72 ------
Starting  Microsoft.Dnx.TestHost [C:\Users\davifowl\.dnx\runtimes\dnx-clr-win-x86.1.0.0-beta8-15562\bin\dnx.exe --appbase "C:\Users\davifowl\Documents\Visual Studio 2015\Projects\ClassLibrary72\src\ClassLibrary72" Microsoft.Dnx.ApplicationHost --port 39457 Microsoft.Dnx.TestHost --port 39495]

System.InvalidOperationException: Dependencies in project.json were modified. Please run "dnu restore" to generate a new lock file.
   at Microsoft.Dnx.Runtime.ApplicationHostContext.GetRuntimeLibraries(ApplicationHostContext context, Boolean throwOnInvalidLockFile)
   at Microsoft.Dnx.ApplicationHost.DefaultHost.Initialize(RuntimeOptions options, IServiceProvider hostServices, IAssemblyLoadContextAccessor loadContextAccessor, IFileWatcher fileWatcher)
   at Microsoft.Dnx.ApplicationHost.DefaultHost..ctor(RuntimeOptions options, IServiceProvider hostServices, IAssemblyLoadContextAccessor loadContextAccessor, IFileWatcher fileWatcher)
   at Microsoft.Dnx.ApplicationHost.Program.Main(String[] args)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.Dnx.Runtime.Common.EntryPointExecutor.Execute(Assembly assembly, String[] args, IServiceProvider serviceProvider)
   at Microsoft.Dnx.Host.Bootstrapper.RunAsync(List`1 args, IRuntimeEnvironment env, FrameworkName targetFramework)
   at Microsoft.Dnx.Host.RuntimeBootstrapper.ExecuteAsync(String[] args, FrameworkName targetFramework)
   at Microsoft.Dnx.Host.RuntimeBootstrapper.Execute(String[] args, FrameworkName targetFramework)
Unable to start Microsoft.Dnx.TestHost
========== Discover test finished: 0 found (0:00:01.4336816) ==========

This is because of my changes to the dnx. We might need to hide this from the user but I'll see if it makes sense to throw it in all cases.

[davidfowl]

@vijayrkn @rynowak

[rynowak]

Would you see the same thing if you ran dnx test at the commandline?

[Eilon]

@davidfowl doesn't the user just have to run dnu restore (from command line or VS)? Is there a bug anywhere?

[davidfowl]

Can close, it's expected

[ShaneCourtrille]

An ugly exception method is expected? Wouldn't it make a lot more sense to handle this a little more gracefully with just the dnu restore message?

[davidfowl]

We're going to change the handling in dnx