I have .net core web application developed in VS 2019 already running in Azure. I installed the VS 2019 in a new system and opened the solution. When I am trying to publish (may be after a simple code change) the application using Visual Studio. The window that is coming up having 3 options to publish. Regarding these options, what is the difference, and when to use what?
Below is the screenshot, options highlighted in red. Create New is for complete new deployment, as per my understanding. However, I'm not able to clearly get, "select Existing" versus "import profile" and when to use what?
Can you download the publish profile from the azure portal for the service in question and reimport it?
The window that is coming up having 3 options to publish. Regarding these options, what is the difference, and when to use what?
1.Create New option enables us to create a new App Service, create or use an existing App Service plan (Hosting Plan) and Resource group within your specific subscription, like below.
If you do not have any existing App Services that you create through Azure portal or VS etc, you can use this option to create a new one before you publish your project.
2.Select Existing option enables us to search and select existing App Services from specific subscription and Resource group.
If you'd like to publish your project to an existing App Service, you can use this option.
3.Import Profile... option provides a way to import publish settings that we got from Azure portal as below and then deploy our app.
Sometimes, developer does not sign in with same account (create Azure App Service etc resources using this account) in Visual Studio, to deploy app to an existing App Service, we can use this option and import a publish settings file.
Related
We have developed an web application using the angular 6 and uploading it manually using the adamos --> "Add application" option in administration Page.
We want to automate the process of building & deploying the application to the adamos.
Currently we are using Azure devOps, for building the angular App and creating a dist folder. Now how do i automate the process of uploading my web app in adamos.
Please let me know, any possibility is there now?
Thanks
Not knowing the Azure devOps you usually use the CLI provided by Cumulocity (via npm) for build & deploy. That is usually also the approach for other CI like Jenkins.
The deploy process itself is just containing REST calls (like the UI also does). So that part you could do also easily without the CLI tool.
I've "setup" AI through the context menu in VS 2017 when selecting the "Configure Application Insights" option. It doesn't set up like ASP.NET sites. it didn't add AI dll's and there isn't a ApplicationInsights.config
But it does state I've connected to the AI i created in Azure. yet i don't see the instrumentation Key anywhere. Also When I rum the WCF service noting gets logged. is there a specific way we need to set up AI for this? I couldn't find articles on how to do this. The only files that were generated was in the Connected Services AI folder and ConnectedService.json
I figured out the issue, of TFS for some reason it didn't allow checkout of project file so it created the files but couldn't add it to the project. I checkout the project manually and delete the files. Then added AI and it worked as expected.
I have a web app (.Net 4.6.2) running on an Azure App Service with Application Insights. I'm using SQL Azure as a back end. When Application Insights logs sql dependencies, the command text isn't included, just the server name and the database name shows up under 'Command'
I've uninstalled and reinstalled the extension and seem to have exhausted online sources. Can anybody suggest where else I look for a solution?
Is this how you install the extension? (Just double checking) And you tried removing/adding back the extension?
Also - does you application refer to SDK in source code already? (via nuget)
I am trying to create Team projects using REST APIs. I have followed the Link:
I am able to create the project just like we can using the web portal.
I am trying to create a project which has SharePoint and Reporting integration, which is not in case of web portal and REST API as far as I know.
Need suggestion on ways of achieving the same with automation.
It doesn't support to create a team project using API with Reporting service and Sharepoint site. The only way is using Visual Studio/Team Explorer to create.
Maybe you could run the tfpt addprojectreports command in your code to configure reports for your new team project of TFS 2015. And use tfpt addprojectportal command to configure Sharepoint in your code. To use these command, you need to install TFS Power Tool.
I've studied the link below:
Storefront Source Code Getting Started.
According to the "Configuring content connection string" Section, I realized that the need to be placed physical address of "cms-content" of admin.
but We've deployed web applications(admin and storefront) to dedicated server.
So for a configuration with these conditions I read the link below:
Deploy web applications to dedicated server
But this link is not yet clear how the "ContentConnectionString" was initialized.
ContentConnectionString storefront setting pointed to place where themes files stored and has default value ~/App_Data/cms-content.
VC platform, with installed module vc-content allows to manage themes files from manager UI and have similar setting CmsContentConnectionString.
If storefront and platform have installed on same Azure apps or dedicated server this both settings should pointed to same physical place and have follow valuesprovider=LocalStorage;rootPath=~\App_Data\cms-content in platform Web.config and provider=LocalStorage;rootPath={ vc-platform physical path}\App_Data\cms-content in storefront Web.config.
For case when VC platform and storefront have separated installation need to use azure blob storage provider=AzureBlobStorage;rootPath=cms-content;DefaultEndpointsProtocol=https;AccountName=yourAccountName;AccountKey=yourAccountKey to share themes files between storefront and platform.
We strongly recommend use store and change your theme in GitHub repository and use CI (continuous integrations tasks) for update themes on production and use admin UI theme management only for emergency fixes or other not historical changes.