I have a solution consist of 2 projects:
- MVC
- WCF
I'm using the visual studio online "I used a TFS on separated VM too but same problem".
Issue: I successfully deployed only the MVC but the wcf not working!!
Request: I hope to find an answer for how to deploy this solution on windows azure website with remotely Database!!
I believe that the continuous delivery to azure template will only deploy a single application. You would need to create a custom ContiniousDeliveryToAzure.xaml to deploy more than one site in a single build.
Or you can put each project into its own build.
If you have a shared component then you should publish it with Nuget and consume it with both other projects.
Related
I am trying to get an Azure App Service to recognize my Web Job - meaning to show it in the portal under "Web Jobs" in the App Service. And to also run it on the schedule defined with a TimerTrigger attribute.
It is a .NET Core 2.2 Console Application with multiple web job classes in it. The App Service it runs within is a separate project and web site. I am able to publish it from Visual Studio and it shows as it should under Web Jobs in the Web App. But if I delete it and try the publish from Octopus to the same place WITHOUT doing the VS 2017 publish first, it won't show up.
My issue is that in a new environment, the Web Job does not get created when I use Octopus to deploy the Web Job files as described here:
http://blog.amitapple.com/post/74215124623/deploy-azure-webjobs
by setting the physical path in my Octopus package deployment:
App_Data\jobs\continuous\myjob
This is the same path as when I publish from Visual Studio 2017.
Related to this question, but there seems to be a step missing since the files are in the right place, but the web job does not appear in the portal.
How to deploy azure webjob using Octopus
Is there some additional ssetup or registration step for the Web Job to run or should the App Service just recognize the web job is there when the files appear in the correct place? Restarting the app service does not help.
Since you have a web app along with a web job, I would follow the steps outlined at https://octopus.com/docs/deployment-examples/azure-deployments/deploying-a-package-to-an-azure-web-app/deploying-web-jobs. You can build your project using .nuspec to get your .npkg and push/upload the package to Octopus.
Hope that helps.
I am new to sharepoint so please bear with me! I have completed a provider hosted application that we will be hosting on premise! One of our requirements is that all apps are ran through TeamCity for build and Octopus for deployment and we use GIT for Source control. I have figured out how to get team city to build my MVC portion of the provider hosted app and got octopus to deploy it, my problem is now how to get he SharePoint part of the app to be automated like that. WHat I mean is now I have to click on publish in visual studio and have it create a .app file and I then have to give that to our operations guys who then upload it to our internal app catalog! is there a way to get TeamCity to create the .App file and then have Octopus deploy it to the Sharepoint Catalog?
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.
I created a SharePoint Application Page. I chose Deploy as a Farm Solution and was able to make the application page work and get deployed on the local (development) SharePoint server. But apparently I cannot deploy (publish) a Farm Solution to a remote (users) server. My requirement is that I need to implement SharePoint Application Pages and deploy them to a remote server. But my problem is that if I choose Farm Solution, I can implement Application Pages but cannot publish to a remote server. But when I choose Sandbox solution I don't have the option to create application pages, the template says Application Page (Farm Solution only). What am I missing here? Why is the type of page related to the deployment target?
I am using Visual Studio 2012 and SharePoint 2013.
You likely need to package it up and deploy from the remote server using powershell: http://patrickboom.wordpress.com/2010/05/31/using-powershell-to-deploy-sharepoint-solutions-wsp-2/
Every example I've seen on how to deploy an MVC application to Windows Azure is using the Visual Studio Publish tool, my problem is that my application is deployed with a custom msbuild file (.proj).
I cannot change the way it is deployed, so is there a way to deploy to azure without publishing? Something like copying the directory result of my custom build to some azure directory.
Thanks for letting us know that it is for Windows Azure Web Role. You can use Automated Build and Deployment with Windows Azure SDK 1.6 blog to deploy directly from ccproj file. Even if it is written with SDK 1.6, you sure can use exact details with SDK 1.7 as well.
You can also take a look at Using MSBuild to deploy to multiple Windows Azure environments blog as well.