I am not getting a way to deployment of war files on WSO2 Enterprise Integrator 6.2 while running it on Developer Studio.
Yes, I am agree with #Dinu94. I had to install WSO2 Developer studio 3.8.0 to get it worked with Web application.
Thanks for your reply.
Related
I am trying to download WSO2 Developer studio, ask me to enter my credentials and nothings happens. I am using macOS. How can I download WSO2 Developer studio?
You can find releases of Developer Studio here
Trying to enable snapshot debugging on an Azure app service. The option to enable the snapshot debugger is not showing up in Visual Studio 2017. Did install the Snapshot Debugger Extension. Upgraded the Insights SDK on the deployed app service to the latest version (2.4.1).
The Visual Studio version I use is VS 2017 Enterprise 15.5.2.
Is this because snapshot debugging is only available for sites? Early blog posts about this feature seem to suggest this, but I'm not sure this is still the case.
The app service I try to snapshot debug is a Web API (.NET framework version 4.6.1).
Any suggestions about steps I'm missing here?
Unfortunately ASP.NET API apps are not currently covered.
The Snapshot Debugger was made available in Visual Studio 2017 Enterprise version 15.5 and greater. VS2017 supported ASP.NET (4.6.1+) and ASP.NET Core (2.0+) running in Azure App Services, however, it currently covers Web UI scenarios.
FYI: VS2019 supports several more Azure scenarios (VM,VMSS,AKS).
I'm trying to publish my web application on Visual Studio 2013 to a remote server operating on Windows Server 2012 R2. I have been following the steps here to install Web Deploy.
I installed the Recommended Server Configuration for Web Hosting Providers and added the role "Management Services" for IIS 8 but I still couldn't find the Deploy option when right-clicking my website.
What could I possibly be missing?
It turned out that i had installed web deploy 3.6 on top of 3.5, removing 3.6 fixed the problem and now Deploy shows in the menu.
I am very new to the visual studio online. It part of POC. I was try to deploy the web application in the Azure. I could successfully deploy the web application in the azure website. Later I have created and Azure Virtual Machine (VM) and try to deploy the application to VM. But I could not. I have read through some of the blogs but not able to figure out how deploy to the VM using Visual Studio Online. I was able to publish the application to the Azure VM using Visual Studio 2015. But failed to deploy via Visual Studio Online.
I am using Build definitions . Please help me to configure the deployment in Azure VM using VSO.
Please check if using DevOps Projects in Azure helps you with your requirement:
Deploy your ASP.NET app to Azure virtual machines by using Azure DevOps Projects: https://learn.microsoft.com/en-us/azure/devops-project/azure-devops-project-vms
Depending on the type of application you're building, you may choose one of the Build Tasks mentioned in the catalog. And then, proceed with the deployment using a suitable Release task. The above tutorial uses the Azure Resource Group Deployment task.
Hope this helps!
We are using Visual Studio 2010 to publish to IIS using Web Deploy. I have now upgraded to Web Deploy 2.0 on the client, and the server (by uninstalling the old version and installing the new version).
From Visual Studio, it still seams to be creating web deploy 1.0 packages. This is where I am confused. How does Visual Studio integrate with Web Deploy? How do I get Visual Studio to create Web Deploy 2.0 packages?
Thanks for your post.
I just found a doc might help, it illustrates the installation and enabling of web deploy:
http://weblogs.asp.net/scottgu/archive/2010/09/13/automating-deployment-with-microsoft-web-deploy.aspx
Moreover, I think web deploy is more relevant to ASP.Net, and if you can post another thread at:
http://forums.asp.net/26.aspx?Configuration+and+Deployment
I believe you can get more useful information.
Hope this can help.
I got it working. The batch file that was being generated by web deploy was checking for v1.1 in the registry. Editing it to check for v2 works on a server that only has v2 installed.
After installing the Visual Studio service pack, I see now that the batch file is different, and no longer does a registry check so works with web deploy clients 1 and 2.