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.
HTML Report Not Loading Correctly for NuGet CLI Install Option
See original GitHub issueSteps:
appinspector analyze -s /path/to/some/code
Expected:
Formatted Report
Result:
Result is not formatted and is missing all images.
Version:
ApplicationInspector.CLI 1.2.49+c4843d26aa
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Installing NuGet client tools
Guidance on installing client tools, the dotnet and nuget command-line interfaces (CLI), and the Package Manager for Visual Studio.
Read more >How can I fix the Microsoft Visual Studio error
Try devenv /setup on the Visual Studio Command Prompt with ... (Tizen Project type package did not load correctly) with Visual Studio 2017....
Read more >Entity Framework not displaying inside NuGet Package ...
I tried to install EF manually via Package Manager Console as well. I am connected with the Internet,but still is not giving any...
Read more >Not able to render Code Coverage results ...
I have a classic build pipeline in Azure DevOps for that builds and run tests for a .Net Core 3.1 app. I am...
Read more >NuGet packages in the Package Registry
Publish NuGet packages in your project's Package Registry. Then, install the packages whenever you need to use them as a dependency.
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
See comments in #266 which indicates the problem is seen when installing the CLI from nuget but not when downloading and building and running. The solution for the path must work for both. Unclear where the defect was introduced but will be addressing so works either way asap/today.
Looking at the Pack command and config options control of output structure doesn’t look available 😦. I had hoped only for an intermediate solution using that approach to get it working again asap until I complete the work in #241 to aggregate all html dependencies into one file. The output file when run by default is placed in the users directory for some reason. Would have expected maybe …dotnet\tools where appinspector.exe lands. I could search subdirectories to find the html folder and set the path in the index.html etc. files but I’ll work on completing #241 instead today and have partial implementation already.