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:
Related
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.
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
I have an existing Web API project published as a 'API App' on Azure. I recently added a "staging" deployment slot that I'd like to publish future versions of the API App before Swapping over to production. However, if I try to create a new publish profile in VS 2015 (or 2017), all my Web Apps are listed except the API App - so there is no way to select the existing deployment. Put this another way, if I delete the publish profile I have no way to publish the project using the Publish wizard (unless I download the publish profile from Azure, but I still have no way to change the deployment slot - that I know of).
I can see my API App in Cloud Explorer OK.
Any ideas?
I think you should be able to go to "deployment slots" in your web app click on a staging slot and then on the right side you will have your staging blade and then ou can download publish profile that is specific to staging slot:
According to your first screenshot, we could find that there are multiple resource groups in current subscription, but you just check the API App in resource group InergySystemsMain, please make sure if the API App belongs to other resource group.
Besides, as RAS said, we could download publish profile of Azure app service from Azure portal to local, and then we could import this publish profile file in Visual Studio.
I am following a series of instructions to deploy a mobile backend using Azure Mobile Services.
As part of that workflow I get to download a personalized backend app which downloads as Visual studio solution.
It builds fine and the next step is to publish it to Azure.
Instead of seeing the choice below (Microsoft Azure App Service) I am seeing 2 different choices
Microsoft Azure Web Apps, or
Microsoft Azure API Apps (Preview).
So, I chose the closest option (Web Apps) provided and it logs me into Azure and in a box which reports existing web apps I see none.
Yet I've deployed a mobile app in the Azure portal earlier.
In some of what I've been reading online it mentions a Publisher profile. I am just a bit stumped by not getting the "Microsoft Azure App Service" choice when I go to publish my backend to the cloud.
Here is the tutorial/guide which I am following (January 2016).
Perhaps the VS/Azure integration has changed since then or maybe I've more configuration steps missing.
Azure .NET mobile backend using Azure Mobile Services
Any guidance would be hugely welcome.
At this stage I am stuck as far as what I need to do to get my mobile backend published to Azure.
You have got an older version of the Azure SDK installed. The latest version of the Azure SDK provides the Azure App Service publish dialog.
I think I've solved this for now.
I was able to download a publish profile from the Azure Console which I could import within the "publish" dialog in VS2015.
I now have the mobile app up and running in Azure.
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.