Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

workaround for AppContext.BaseDirectory being null on some platforms #293

Merged
merged 1 commit into from
Jul 3, 2019
Merged

workaround for AppContext.BaseDirectory being null on some platforms #293

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion src/WireMock.Net/Owin/AspNetCoreSelfHost.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,18 @@ public AspNetCoreSelfHost([NotNull] IWireMockMiddlewareOptions options, [NotNull

public Task StartAsync()
{
_host = new WebHostBuilder()
var builder = new WebHostBuilder();

// Workaround for https://github.com/WireMock-Net/WireMock.Net/issues/292
// On some platforms, AppContext.BaseDirectory is null, which causes WebHostBuilder to fail if ContentRoot is not
// specified (even though we don't actually use that base path mechanism, since we have our own way of configuring
// a filesystem handler).
if (string.IsNullOrEmpty(AppContext.BaseDirectory))
{
builder.UseContentRoot(System.IO.Directory.GetCurrentDirectory());
}

_host = builder
.ConfigureServices(services =>
{
services.AddSingleton(_options.FileSystemHandler);
Expand Down