Jared Parsons
d861f4a6ee
The connection to the worker process was sync on the UI thread which could lead to hangs. Made it an async operation instead. This did require me to upgrade to the 4.6 framework to use the NamedPipeClientStream::ConnectAsync method. If that is a blocker I can downgrade back to 4.5.2 and use Thread tricks to get a similar effect.
27 lines
1.0 KiB
C#
27 lines
1.0 KiB
C#
//------------------------------------------------------------------------------
|
|
// <auto-generated>
|
|
// This code was generated by a tool.
|
|
// Runtime Version:4.0.30319.42000
|
|
//
|
|
// Changes to this file may cause incorrect behavior and will be lost if
|
|
// the code is regenerated.
|
|
// </auto-generated>
|
|
//------------------------------------------------------------------------------
|
|
|
|
namespace xunit.runner.wpf.Properties {
|
|
|
|
|
|
[global::System.Runtime.CompilerServices.CompilerGeneratedAttribute()]
|
|
[global::System.CodeDom.Compiler.GeneratedCodeAttribute("Microsoft.VisualStudio.Editors.SettingsDesigner.SettingsSingleFileGenerator", "14.0.0.0")]
|
|
internal sealed partial class Settings : global::System.Configuration.ApplicationSettingsBase {
|
|
|
|
private static Settings defaultInstance = ((Settings)(global::System.Configuration.ApplicationSettingsBase.Synchronized(new Settings())));
|
|
|
|
public static Settings Default {
|
|
get {
|
|
return defaultInstance;
|
|
}
|
|
}
|
|
}
|
|
}
|