Attempting to run a NetStandard class library that's been turned into a console app shows an error about "RunCommand" missing
See original GitHub issuePorted from https://github.com/dotnet/roslyn-project-system/issues/1309
- Create a new C# .NetStandard library.
- Open properties pages and change the Application type to Console Application.
- Add a static Main method to the class.
- F5
---------------------------
Microsoft Visual Studio
---------------------------
Unable to run your project. The "RunCommand" property is not defined.
---------------------------
OK
---------------------------
Issue Analytics
- State:
- Created 7 years ago
- Reactions:12
- Comments:21 (11 by maintainers)
Top Results From Across the Web
visual studio 2017 - Console App (.Net Standard) not listed
[EDIT] I have attempted to run devenv /installvstemplates but the devenv command is not found. I found it located here: C:\Program Files (x86)\ ......
Read more >C# console app template generates top-level statements
The .NET 6+ project template for C# console apps uses top-level statements. Understand what changed and how to use existing learning ...
Read more >Cannot debug net6.0-macos Apps - Developer Community
When I hit debug, the following error is shown in the Terminal: Possible reasons for this include: * You misspelled a built-in dotnet...
Read more >Grpc internal error. I am using WinHttpHandler as was mentio
gRPC is an open-source RPC framework that is created and used by Google. ... When i try to run in on local it...
Read more >Multi-Targeting and Porting a .NET Library to .NET Core 2.0
I've been holding off porting any of my full frameworks to .NET Core. With the latest .NET Core 2.0 and .NET Standard 2.0...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
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
Relatedly, ASP NET non-core works so long as
RunComand
property is defined and a few other things like this:Obviously use whatever port and IIS bitness you want
(Improved thanks to @rainersigwald)
Any news on this? How can we go around it?