Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DisableImplicitNamespaceImports=false doesn't disable DisableImplicitNamespaceImports_DotNet.
See original GitHub issueWhen settings DisableImplicitNamespaceImports=false, DisableImplicitNamespaceImports_DotNet is not set to any value:
https://github.com/dotnet/sdk/blob/2c4782668099b5cf4a6b7d2a8fe26d1665798f6d/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.GenerateImplicitNamespaceImports.targets#L22
So this condition ‘$(DisableImplicitNamespaceImports_DotNet)’!=‘true’ in https://github.com/dotnet/sdk/blob/2c4782668099b5cf4a6b7d2a8fe26d1665798f6d/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.Sdk.DefaultItems.props#L86 is true and the implicit namespaces are still generated. So the only way to disable them is to set both properties to true explicitly.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
As part of the changes in rc.1 the sub-level properties were removed so this doesn’t apply anymore.
Reassigning to you @rafikiassumani-msft to ensure this is handled appropriately.
@safern @DamianEdwards is this issue still applicable❔