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.
New tooling leaves a mess under obj, causing duplicate attribute problems
See original GitHub issueThe current dotnet build tooling seems to leave files such as obj/{configuration}/{platform}/dotnet-compile.assemblyinfo.cs. This can break some existing builds, for example in dapper we use out-of-project file references:
"compile": [
"../Dapper/**/*.cs"
],
This worked fine previously, but now creates things like:
error CS0579: Duplicate 'System.Reflection.AssemblyInformationalVersionAttribute' attribute
(because of course it finds the file for each platform and/or configuration)
We can fix this by adding:
"compileExclude": [
"../Dapper/obj/"
],
But; this seems pretty horrible. I’m not saying the setup is perfect here, but it seems like maybe the tooling should default to ignoring files that it almost certainly created (for a different purpose, and unless it knows that it really wants it for what it is currently doing). Or alternatively: don’t leave such things behind ;p
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (4 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
This is still a problem in RTM (Preview 2 tooling).
This is still a problem in RC2.