Deployed bot created via File -> New project -> VSIX template fails to run in Azure

[sgellock]

Tool

Name: VSIX
Version: 4.0.6
OS: Windows

Describe the bug

Deployed bot created via File -> New project -> VSIX template fails to run when published to AppService due to missing "production" endpoint configuration in .bot file

Additional context

Both the Echo and the Basic bot VSIX templates include a .bot file along with startup code that attempts to load this file and confirm proper configuration for the target host environment, however the documentation for deploying bots makes no mention of this file and what to do with it resulting in a non-functional app once deployed.

[bug]

[andrewchungxam]

Hi @sgellock any luck getting past this issue?

[sgellock]

We plan to have this addressed, with an updated VSIX template published no later than 12/15 From: andrewchungxam <[email protected]> Reply-To: Microsoft/BotBuilder-Samples <[email protected]> Date: Wednesday, November 21, 2018 at 11:27 AM To: Microsoft/BotBuilder-Samples <[email protected]> Cc: Scott Gellock <[email protected]>, Mention <[email protected]> Subject: Re: [Microsoft/BotBuilder-Samples] Deployed bot created via File -> New project -> VSIX template fails to run in Azure (#955) Hi @sgellock<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsgellock&data=02%7C01%7Cscott.gellock%40microsoft.com%7Cf0eb01c58a4248129fc508d64fe75e68%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636784252468407006&sdata=q8TyD5iKojepUo8SCqf5mNRt9PFs4NUFR%2BLSw3H%2F1io%3D&reserved=0> any luck getting past this issue? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FBotBuilder-Samples%2Fissues%2F955%23issuecomment-440783011&data=02%7C01%7Cscott.gellock%40microsoft.com%7Cf0eb01c58a4248129fc508d64fe75e68%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636784252468407006&sdata=pXwS5wErNyBCSRBtxVEtJWJe%2BcWEOte9B8u9bp7YuNk%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAsxdyxqG0Hx8E-YE2L-8eo_REQLpbnhks5uxakdgaJpZM4Ynu8d&data=02%7C01%7Cscott.gellock%40microsoft.com%7Cf0eb01c58a4248129fc508d64fe75e68%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636784252468417020&sdata=EH8%2Bptn5cNe1YsgpY%2F1ghIyLtnh4BkgupZUcJtC69jQ%3D&reserved=0>.

[cleemullins]

This has been (mostly) resolved, with more improvements coming. The latest VSIX has been published to the Visual Studio Marketplace.

This will get better (significantly) once the configuration validation code is merged in and integrated. That code will validate, as part of the Visual Studio publish process, that the .bot file is properly setup.

In the immediate term, the "production" endpoint is now part of the .bot file, and needs to be filled out by the developer.

[cleemullins]

We've turned the crank of the VSIX files in 4.2, and will do so again in 4.3. Pushing this to 4.3, as the root problems are not yet resolved.

[jengstro2]

Is this the same not-so-nice experience what I had after renaming the sample project file from BasicBot -> WhatEveryIWant (csproj). After renaming the sample project -> publish -> nothing happens / freezes over. Local debug environment works. Is there some nice dependencies on those Azure deployment files -> towards the BasicBot.DLL name?

[gabog]

Closing, we are moving the infrasctructure deployments to ARM templates.