Publishing bot to Azure fails - "No directory ComposerDialogs/generated + csproj not found"

Describe the bug

I have a working bot created in BFC and want to publish it to Azure. Setting up the publishing profile did work, along with automatic provisioning of all required Azure ressources conducted by BFC. But when selecting the bot and pressing Publish selected bots, I immediately receive the error shown in the first screenshot below. When I manually create the folders ComposerDialogs/generated in the according program files app folder, the first error is solved. But then another one occurs -> see second screenshot and pased stack trace in context section below.

Version

Version: 2.0.0-nightly.242720.c3b8105 Electron: 8.2.4 Chrome: 80.0.3987.165 NodeJS: 12.13.0 V8: 8.0.426.27-electron.0

Browser

• Electron distribution
• Chrome
• Safari
• Firefox
• Edge

OS

• macOS
• Windows
• Ubuntu

To Reproduce

Steps to reproduce the behavior:

1. Go to ‘…’
2. Click on ‘…’
3. Scroll down to ‘…’
4. See error

Expected behavior

Publishing a bot should succeed. Indeed it does succeed, when using the latest stable version 1.4 of BFC.

Screenshots

First error (I could solve)

Second error

Additional context

Error log of second error

---
"Accepted for publishing..."
---

---
"Abs settings incomplete, skip linking bot with webapp ..."
---

---
"appPasswordHint incomplete, return ..."
---

---
"Building the bot app..."
---

---
"Build succeeded!"
---

---
"start publish luis"
---

---
"Assigning to luis app id: <SOMEGUID>"
---

---
"Assigning to luis app id: <SOMEGUID>"
---

---
"Luis Publish Success! ..."
---

---
"{\"stack\":\"Error: Command failed: dotnet publish \\\"Microsoft.BotFramework.Composer.WebApp.csproj\\\" -c release -o \\\"bin\\\\release\\\\publishTarget\\\" -v q --self-contained true -r win-x64\\n\\n    at ChildProcess.exithandler (child_process.js:308:12)\\n    at ChildProcess.emit (events.js:210:5)\\n    at maybeClose (internal/child_process.js:1021:16)\\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)\",\"message\":\"Command failed: dotnet publish \\\"Microsoft.BotFramework.Composer.WebApp.csproj\\\" -c release -o \\\"bin\\\\release\\\\publishTarget\\\" -v q --self-contained true -r win-x64\\n\",\"killed\":false,\"code\":1,\"signal\":null,\"cmd\":\"dotnet publish \\\"Microsoft.BotFramework.Composer.WebApp.csproj\\\" -c release -o \\\"bin\\\\release\\\\publishTarget\\\" -v q --self-contained true -r win-x64\",\"stdout\":\"Microsoft (R) Build Engine version 16.4.0+e901037fe for .NET Core\\r\\nCopyright (C) Microsoft Corporation. All rights reserved.\\r\\n\\r\\nMSBUILD : error MSB1009: Project file does not exist.\\r\\nSwitch: Microsoft.BotFramework.Composer.WebApp.csproj\\r\\n\",\"stderr\":\"\"}"
---

---
"Error - Command failed: dotnet publish \"Microsoft.BotFramework.Composer.WebApp.csproj\" -c release -o \"bin\\release\\publishTarget\" -v q --self-contained true -r win-x64\n"
---

[dmvtech]

Created a new bot and was able to publish successfully. With:

Version:  2.0.0-nightly.242720.c3b8105
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0

So, might have to do with creating bot in previous version.

[peta]

I can reproduce this. I’m not 100% sure, but my bot might have been created with 1.4.0 release. @peta Do you know if yours was created with a nightly build or with 1.4.0?

Unfortunately I don’t know with what version it has been created with. I did not create the initial bot project myself. Only reviewed it and extended the language recognition definitions.

However, I just updated to the latest nightly build (2.0.0-nightly.243997.543d0b4), opened the bot project and was prompted to upgrade it (save as copy) so that it is compatible with the latest nightly version. And guess what? I can now successfully build and publish the bot using the same publishing profile. 🎉👍

Publishing for me works with this nightly version:

Version: 2.0.0-nightly.243997.543d0b4 Electron: 8.2.4 Chrome: 80.0.3987.165 NodeJS: 12.13.0 V8: 8.0.426.27-electron.0

I think this issue here can be closed. Thanking everybody of you for your quick support and dedication. 🥇