-
Notifications
You must be signed in to change notification settings - Fork 754
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
MsBuild Extended support for net.sdk project type system (targeting desktop framework, not core) #1223
Conversation
…s if sdk.props and sdk.targets are manually imported (advanced scenarios)
…ave any corresponding feature file
When executing the Specs tests there is a problem:
I would say, the version of MSBuild we use in the Specs project is to old. |
…proj to prevent build error
…on of Microsoft.Build to support parsing of itemgroup remove and update
I've updated the test projects to use the already used nuget package for msbuild instead of .net 4.0 references. |
Seems like we are running into the following MSBuild Issue. |
…e only if net.sdk style projects will be used. currently, many projects are moving codebehind files into a different location using AfterUpdateFeatureFilesInProject Target
…ent fail of build
@SabotageAndi hopefully I'm ready with the PR for review 😎 |
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.
looks good. we should also document the experimental settings at https://specflow.org/documentation/Generate-Tests-from-MsBuild/
This pull request extends support for net.sdk project system when MSBuild Generation is used
As this integration is experimental, you have to enable it via the following MSBuild property
Types of changes
Checklist: