Publish web application into azure web app using visual studio online - asp.net

I have created following Virtual Applications and Directories in the azure portal Click here to view the image
And using visual studio online I can build and deploy the site into root folder but I couldn't figure it out how to deploy into a virtual directory I have created earlier.
Click here to view the image
Any one have experience on this ? Appreciate your thoughts.

The Azure Web App Deployment task can't deploy a virtual application as it uses Publish-AzureWebSiteProject which can't handle virtual applications.
You can check the poweshell script which uses WebDeploy to deploy a virtual application at website:https://github.com/Microsoft/vso-agent-tasks/issues/624

Related

ASP.NET Web Forms Application Folder not deployed to AWS Elastic Beanstalk Application

The ASP.NET Web Forms Application that I've designed, contains a folder where the excel sheets that I require for the web reside. I've deployed the Web Application to AWS using the AWS Toolkit in the VS 2017, and could successfully get the application running over the Web. But, when I did something on the web (like Upload) which makes use of that folder, it resulted in exceptions and when I look at them through Log files later, I discovered that the Folders weren't even uploaded in the deploy process. Is there any way I could get the folder deployed as well?
Please ensure that the folder is included in your project before publishing. In Solution explorer, click on the Show All Files icon
And once the folder is displayed in the Solution Explorer, right click the folder and then Include in Project

TFS 2017 Release definition. WinRM - IIS Web App Management task. Create application under "Default web site"

I am working on a release definition which will deploy a website to a test IIS server (Windows server 2012, IIS 8).
I would like to use the IIS Web App Management task to create and configure an application or virtual directory under "Default Web Site/Scott"
When I specify "Default Web Site/Scott" or "Default Web Site\Scott" as the Website, the task fails due to the name attribute.
The Scott application will be created alongside many existing applications underneath the Default Web Site parent. I don't mind if it shares the app pool.
Can I use the WinRM task? If not, are there any alternatives apart from writing Powershell?
In the WinRM - IIS Web App Management task, there is also a Parameters for IIS Application configuration you could simply configure to deploy the IIS Web Applications. However this is not available wit TFS for now:
The Visual Studio Team Services accounts that are using the
preview tasks wiz. IIS Web Application Deployment or SQL Server Database Deployment, should move to this extension. All
future enhancements to the IIS Web App Deployment task or to the SQL Server Database Deployment task will be provided in this
extension.
Source Link
For now you have to directly deploy a Web Application to the IIS Server with IIS Web App Deploy task which using Web Deploy. You could add a environment variable IIS Web Application Name and use this as the website name, such as:
The “IIS Web Application Name” parameter is the IIS path where you want to deploy your web application. This can include a value such as Default Web Site/Contoso.web_deploy, this is specified in the Deploy IIS App task under Deployment | Website Name.
For more detail steps, you could take a look at below two nice blogs:
Working with Web Deploy and Release Management
End to End Walkthrough: Deploying Web Applications Using Team Build
and Release Management

How to publish ASP.Net website to remote machine?

I am trying to publish the ASP.Net site in IIS to a remote machine.
Presently I am publishing the site local file system and copying that folder to remote machine using mstsc tool.
Is there any way I can directly publish to remote machine?
Sure there is,
You have to make sure web deployment service is running on your server. You can check these articles to find out how to install the web deployment. Here or here.
Once your web deployment service is running and configured you need to configure your publishing settings. In Visual Studio right click on your solution project, choose Publish and select the Web deploy or Web deploy package as your publish method setting. Good article describing web deployment scenarios can be found here.
Hope that helps you.

How to only deploy changed project files in Windows Azure?

I am working on a web project in ASP.NET which is integrated with Salesforce. I have published my web project in Windows Azure. Now I have some changes in particular files and I want to deploy these changes only rather than complete project.
If you are using Web Deploy from within Visual studio, it will automatically only deploy the changed files in a differential manner. Alternatively, if you are using Azure VM's or a Cloud Service (which is actually VM's), you can connect to the machine(s) using RDP and update select files manually. You can get the RDP information to the machine from the Azure Portal.
http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-log-on-windows-server/

asp.net website deploymnet on client

I have completed building a website for a client.Now i want to deploy this website on the server, So that client can access the website like a normal website. what is the best way to do it.
I am using C#,asp.net 3.5, Ms Access.
Thanks
Do you want to protect the source code as well?
YES
Install the Web Deployment Project for Visual Studio (there is on for VS2008 and other for VS2010)
Add that project to your solution
Add a Web Setup project to your solution
Tell the Web Setup project that to load the Deploy project as source
Build the Solution
You will have in the Web Setup folder a setup.exe and Website.msi ready to be installed in any client machine (client needs to have IIS)
NO
Add a Web Setup project to your solution
Tell the Web Setup project that to load the Web Site project as source
Build the Solution
You will have in the Web Setup folder a setup.exe and Website.msi ready to be installed in any client machine (client needs to have IIS)
All 3 projects, Web Site + Deploy project + Setup Project

Resources