Might not be much of an issue, we'll see...
Arguably it's a semver-breaking change to switch the TFMs like that, but I don't think Jeremy has been that strict about those -- and with the ever-shifting platform, being strict about it means a lot of work.
If we can possibly get away with that anyway.
So I don't think there's much point in letting Alba target netstandard2.1
I’ll have some time this weekend to go over the Nuget mechanics, then get this published if you two think it’s ready
Now I just need to have some more packages start to support .NET Core 3.0 :P
@rytmis @jmezach And it’s up: https://jeremydmiller.com/2019/09/29/alba-3-1-supercharges-your-asp-net-core-http-contract-testing/
Thanks for all your work on this one.
It's failing with "bad request - invalid hostname"
Here is my SUT setup code:
public async Task Test_Logging()
{
var builder = BusinessRulesEngine.Web.Program.CreateWebHostBuilder(new string[] { });
using (var system = new SystemUnderTest(builder, typeof(Startup).Assembly))
{
await system.Scenario(_ =>
{
_.Get.Url("/home/TestLogging");
_.ContentShouldBe("");
_.StatusCodeShouldBeOk();
});
}
}
thoughts on why it doesn't like the hostname?
@jeremydmiller
had mixed runtime refs between app and test projects.
added these to test.csproj
<TargetLatestRuntimePatch >true</TargetLatestRuntimePatch >
Not an issue w/ AspNetCore 3.0 I believe
yeah 2.2
i was also getting the multiple version warning during assembly binding
all better now
not sure about the docs. I'll look again.
now i'm getting authorization failures, but that I understand. I've not done anything to set an auth header for my test request.
pretty sure it's working
For 3.0, they changed things for Nuget references for AspNetCore yet again. Alba just targets netcoreapp3.0 and the references will float based on the runtime version now. Should soften up the exact problems you saw
