`dotnet new corebot -n TestBot` creates project at TestBot/CoreBot
See original GitHub issueVersion
Bot Framework Echo Bot (v4.15.0)
Describe the bug
When creating a new bot using dotnet new corebot
, the -n
argument should be used as the name of the project.
This works correctly for echobot, but not for corebot.
Instead of creating the project using the specified name, it creates a folder and then puts the project into a “CoreBot” subfolder.
To Reproduce
Steps to reproduce the behavior:
- Run
dotnet new corebot -n TestBot
Expected behavior
Bot project should be at TestBot
, but is at TestBot/CoreBot
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
dotnet new <TEMPLATE> - .NET CLI
The dotnet new command creates new .NET projects based on the specified template.
Read more >Creating .Net Core Projects with the CLI - Harry Bellamy
Create the Console App Project. We can first script the console app using dotnet new like so: dotnet new console -n MyNewConsoleApp.
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
Hey @Swimburger
Thanks for raising this issue. I believe this is expected. The documentation needs a little clarification.
When running
dotnet new corebot -n TestBot
only the parent folder receives the bot name. i.e. the folder output isTestBot/CoreBot
I opened an issue for this Create a bot with the Bot Framework SDK doc here: https://github.com/MicrosoftDocs/bot-docs/issues/2184
investigating this.