-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Use default VC toolset #9332
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 default VC toolset #9332
Conversation
dougbu
commented
Apr 12, 2019
- aspnet/AspNetCore-Internal#2246
- aspnet/AspNetCore-Internal#2246
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on what the VS error tells me and what @jkotalik suggested, this should be ok.
@javiercn can you try that locally to make sure it works? We won't get validation on CI with this change. |
From @javiercn
Aka I'll test it shortly. |
@jkotalik You're such a I'll test it once its merged |
This the only thing I got working locally. I also think it's the only way this will work on CI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it works, 🆗 but what about Installers\Windows\AspNetCoreModule-Setup//.vcxproj ?
src/Servers/IIS/AspNetCoreModuleV2/AspNetCore/AspNetCore.vcxproj
Outdated
Show resolved
Hide resolved
@dougbu this is what was generated when using the Property Pages in VC++ tooling. I agree it is horrible and I can simplify it, but it is auto generated. |
🆙 📅 |
This is blocking people so if this passes, I'm merging btw. |
gah communication errors <_< |