Errors when compiling "Getting Started - FuncUI" example
See original GitHub issueThe following compile errors happen when I try to build the example code on Getting Started - FuncUI. The only difference is I’m trying this from a Visual Studio F# console project instead of the command line.
Error FS0193 The module/namespace 'Avalonia.Controls' from compilation unit 'Avalonia.Controls' did not contain the namespace, module or type 'ItemsRepeater' FuncUISample C:\Users\***\source\repos\FuncUISample\FuncUISample\FSC 1 N/A
Error FS0039 The value, namespace, type or module 'DockPanel' is not defined. FuncUISample C:\Users\***source\repos\FuncUISample\FuncUISample\Program.fs 16 N/A```
Issue Analytics
- State:
- Created 5 months ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How C++ Works: Understanding Compilation
The article will explain how a C++ compiler works with some of the basic language constructs, answer some common questions that are related...
Read more >How can I force a compile error in C++?
during template processing), use static_assert (a C++11 feature). Look into static_assert . To force a compiler error (GCC, Clang style):
Read more >I'm getting compile errors in the standard library. What's up?
I'm trying to compile an unspecified piece of software, and I'm getting errors in the standard headers such as stdio.h . The errors...
Read more >Understanding and fixing compiler and linker errors
How to fix common compiler and linker errors in C++.
Read more >fsprojects/Avalonia.FuncUI: Develop cross-plattform GUI ...
FuncUI mostly consists of: Virtual DOM; View DSL; Component model. Resources. Getting started. Documentation.
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
That fixed it
Works for me after adding 2 lines (they are in the docs, guess they were marked as unused before):