anderslaub
anderslaub
> @anderslaub Can you modify your PR to target the `develop` branch? Thanks! @Shane32 I've changed PR to target `develop` and did a merge local to fix the failing tests....
@Shane32 Pragmatically; it works, so.. Another question, `server:develop` referenced `6.0.0-preview-612` I've made signed nugets from `graphql-dotnet:develop` for now just called `7.0.0-strongname` and referenced these instead - all the projects that...
https://github.com/graphql-dotnet/graphql-dotnet/blob/2ff8a9ac649215965437c95577afdab1f70d9111/src/Directory.Build.props#L4 this is called 7.0.0-preview
and the reference in `server:develop` is https://github.com/graphql-dotnet/server/blob/240e112f329e3eec13254e59d58180a815700ede/Directory.Build.props#L31 6.0.0-preview-612
Sure okay, then I just wonder why the test projects on `server:develop` doesn't build. But I leave it for now and wait for the releases. Btw; do you think there...
> > Sure okay, then I just wonder why the test projects on `server:develop` doesn't build. But I leave it for now and wait for the releases. > > Btw;...
@Shane32 Done - or almost done at least.. I just made GraphQl.Harness + Tests override SignAssembly to mitigate the cyclic dependency with `server`. Since it's just examples, there really seems...
@Shane32 That was easy :) I've merged in `graphql-dotnet:remove_asyncex` to make tests pass. Meaning this now includes #3278
@Shane32 merged in #3281
Moving the existing solution to a "Legacy" layer is really the Strangler pattern. I've tried to come up with a general high-level "recipe" but it is hard - or rather...