-
Notifications
You must be signed in to change notification settings - Fork 353
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.
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
Use msbuild
from VS 2022 if available
#395
Conversation
e0e7859
to
190416c
Compare
- should ease local and TeamCity builds - make `%InstallDir%` unquoted (unlike `%vswhere%`) - shorten `%Path%` slightly - nits: - switch to 64bit `msbuild` - use script location more; no need to change directories
- follow up to aspnet#396 (unsure why new FxCop and "spelling" errors didn't fail that PR)
190416c
to
7ca7468
Compare
@wtgodbe I normally don't worry too much about this repo's build and test flakiness. In this case however, I seem to have changed timings enough for some incorrect assemblies to land in My efforts so far haven't worked and I may back out my latest (xUnit collection) commit. In the meantime, I'm going to try another thing or two. First, calling in the big guns… @halter73 @Tratcher could you please have a look at the logic in the |
- seems to resolve `Moq` assembly load issue
I forgot to mention: The issues related to |
Somewhat predictably, build #20230306.4 immediately after this PR validated on its first attempt for this iteration failed w/ lots of port reservation problems. Hopefully there's something in |
msbuild