No executable found for library with references
See original GitHub issueSteps to reproduce
- Given the environment like below, create a solution
HelloWorld
- Add a library project
HelloWorld.Avalonia
with some views to test the designer - Add an executable project
HelloWorld.Desktop
which referencesHelloWorld.Avalonia
- Build the entire solution
- Open a view of
HelloWorld.Avalonia
in the designer
Expected behavior
After selecting HelloWorld.Desktop
as executable project the designer should work.
Actual behavior
The designer does not load and logs an error:
[Error] No executable found
.
Tested versions (all affected)
- .NET Core 3.1 and .NET 5.0
- Avalonia 0.9.12 and 0.10.0-rc1
Environment
- Windows 10 Pro (19042.685)
- Visual Studio 2019 Community (16.8.3)
- Avalonia for Visual Studio 0.9.12.0
Workaround
Add a package reference to Avalonia to all your executable projects. The designer doesn’t find transient references.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Qt Creator - C++ Library, No executable found?
A library [usually] needs to be invoked from an executable - The dialog box you are seeing is asking you to specify an...
Read more >Executable Not Found ,Xcode | Apple Developer Forums
Once I deleted the references to the non-existent files and added the new files, Xcode then expectedly complained that the old enum didn't...
Read more >No executable found for solver 'ipopt
I first installed the latest version of ipopt through command line into my Pyomo environment and got the "No executable found for solver ......
Read more >"No executable found" for Python script edit
Scenario 1: Fresh Ubuntu 20.04 System for reference Install ROS2 Foxy. ... tester" to run executable: "No executable found" error appears.
Read more >target_link_libraries — CMake 3.27.3 Documentation
The named <target> must have been created by a command such as add_executable() or add_library() and must not be an ALIAS target. If...
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 FreeTop 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
Top GitHub Comments
This recently started happening to me after updating Visual Studio 22 to 17.7.0.
@maxkatz6 I had a similar problem on my project. That the designer was forced my Avalonia control class library to use one (D) of 4 executable program projects (A,B,C,D) in solution, and because of this project D due to some thing wrong when my colleague check-in, the csproj file have not checked-in, so I could not be compiled the project D. Then, so my library got the same behavior because it was forced to use the project D. After my colleague checked-in the csproj file of project D, project D can be compiled, and this problem disappears. But it’s strange, there are 4 executable program projects in my solution, why the designer force the class library to use that project D which can’t be compiled?