Can I publish a bot, created using bot framework .NET core template, using bot composer - botframework

I have created a bot using Template in VS 2019. I Can deploy it using Azure CLI and Directly publishing from Visual Studio to Azure. I just want to know can i deploy it using Bot framework composer or not. As I am trying to open a bot using composer but it is not letting me open it.

If you created the bot using a template from VS, then you cannot publish from Composer. Bots created outside of Composer are not compatible and therefore you will not be able to open it, nor publish it.

Related

Can't open Bot Framework Composer from Azure Portal on Linux Mint 20.2

I have installed the Bot Framework Composer on Linux Mint 20.2. I have created an Azure Bot in the Azure portal and want to open it with the Composer. When I click on the link Open in Composer in the portal, nothing happens. If I copy the link provided into a browser tab, the browser doesn't know what to do with it. What do I need to do to make this work?

host MS Bot Framework Composer c# project in self-hosted service

In v3 we had option to host c# project in Windows Service. I can't found any examples of it.
How we can do same with MS BOT Composer c# project?
This is the thread you will want to keep an eye on. Please feel free to add input and suggestions there.

.BOT file not getting deployed to Azure Bot Service v4

Using Azure Bot Service with C# Bot Builder SDK v4 v4.0.7 (the GA version released September 2018).
I'm using the BOT file to store configuration settings for a GenericService and so have changed the BOT file from the default that was provided with the Azure template.
Changes were made via MSBOT CLI.
When running locally via the emulator, the bot code sees modified local BOT file and all is good.
However, the BOT is never deployed to Azure and therefore the Azure service does not see my changes (it is stuck with the default BOT file). I've deployed via Visual Studio publish and GitHub CI.
I had to manually upload the file using Visual Studio Cloud Explorer and the bot was then able to use the modified version and all is good.
Question is why is the BOT file not deployed with the rest of the bot code and how can I make sure it is deployed. Not sure if this is a bug or not?
I believe this is the fix to deploy the .bot file. In Visual Studio,
Right click on the .bot file
Click Properties
Under file properties, verify that "Copy to Output Directory" option says Copy Always.
Here's a screencap:

Bot framework HTTP status code InternalServerError

I try to integrate bot framework with UWP application using direct line, but I have this error. I used a web chat to test, it still shows me the same error. But if I use a Bot emulator to test it, it works. I already set my published bot to Always On on Azure, but still have same issue:
Go to your Azure portal to create a Bot service, and then copy your original code (that you program in Visual Studio), and paste it to the website editor, then click SAVE, now test your bot again, I think it can work

How do I deploy an existing web app project to Azure using Visual Studio but no Azure Emulator?

I have an existing project with three web apps (two web API and a front end). I would like to deploy to Azure all three with a single click of Publish using the Publish Web wizard.
I installed the Azure SDK and tried to create a new Cloud Service, but this install the VMs and the storage emulator, that I don't need at all and slows down my PC.
I tried with Azure Resource Group to add to an existing project, but the Deploy button remains disabled, like it failed to connect to the web site project.
What is the recommended way to do this?
I am using Visual Studio 2015
Thx.
You do not need to install the emulator for the deployment to work, just download the parts you need from http://www.microsoft.com/en-us/download/details.aspx?id=48178 (assuming you want SDK 2.7).
It's not really clear from your question if you want to deploy a Cloud Service or a Web App. If you want to deploy a Cloud Service, you can add all 3 projects as roles and they will all be published within a single deployment (just one click to Publish). But, if what you want is to deploy them as web apps, you will need to do it in 3 different apps, which means 3 clicks to publish.

Resources