Stuck on an issue?
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.
Hard-to-diagnose "No metadata is generated"
See original GitHub issueIn relation to #165.
Even though I have --logLevel Verbose I cannot tell why the project is being skipped with Warning:No metadata is generated for XXX..
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (3 by maintainers)
Top Results From Across the Web
Hard-to-diagnose "No metadata is generated" error when ...
Title Hard-to-diagnose "No metadata is generated" error when code has no namespace Functional impact Friction when trying to reproduce a ...
Read more >Visual Studio 2019 Keeps Directing to MetaData Files ...
I instantiate an instance of Foo inside of Bar and call Foo.DoSomething() . If I hover over Foo.DoSomething() and click F12 (Go To...
Read more >sfdx force:source:push fails with lots (thousands) of errors
i started with a small package - no custom objects, a few custom fields, one custom setting, a few apex classes, one VF...
Read more >metadata - MetadataService mock class
I tried creating a mock class for a class that uses MetadataService but after too many attempts, I stll can't get it. Can...
Read more >Try the new System.Text.Json source generator - .NET Blog
Supports all serialization features, Yes, No, Yes ... After this metadata is generated, the serializer performs the actual serialization and ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ThadHouse in my case I was targeting multiple target frameworks. In case you have the same, you need to specify them in your docfx.json as described here: https://github.com/dotnet/docfx/issues/1254#issuecomment-294080535
Neither the TargetFramework nor the updated build tools requirement help this build on appveyor. Also tested the new logger function, and all it says is “Failed to parse file”, so its not very helpful.