VS2013 hosting on existing azure virtual machine - visual-studio-2010

When you start a New Project in VS 2013, you can choose to host the project on an Azure Virtual Machine.
The problem is that it seems you can ONLY CREATE a NEW ONE and not host it on an existing virtual machine you might already have.
Or at least, I cannot find the way to do so and cannot find anything on the net that shows me how.
QUESTION:
How can I use my existing Azure Virtual Machine to host an MVC application developed from my desktop??

If I understand what you're after, you can simply install and configure IIS, create a virtual and point it to the file system path where you have your production code (you can simply upload it to the server). You would then simply open up the appropriate ports in the Azure interface to allow external access if desired. You're basically just setting up an IIS site that can host your application then uploading the app to the server using something like FTP or web deployment.
-matt

Related

how to set up visual studio for a remote project

Can Visual studio 2019 be used as a local IDE for a solution running on a remote server? specifically i want to create a node.js application on a remote server hosted / provided by my ISP using Vstudio that's running on my local windows machine. I'd like the builds to run on the remote server. Is this possible?
To date, I have been connecting via ssh and just using VIM to create my apps. But I see that VStudio is free and has a lot of support for different types of apps so wanted to give a try.
I launched VStudio and created a new node.js application. Gave it a name (it was pointing to a local folder)
But then when I tried to do was go under Tools -> options ->Cross platform-> connection manager.
I successfully added a connection to my remote server. I know the connection worked because it detected that the remote server is running Ubuntu.
I must be still missing a step because when I try to build, instead of running the build against the remote server, it tries to build locally.
Maybe I can't do this. Maybe I need a local dev environment... build local and then copy the js files over to the target machine.
But jut thought I'd check
Thanks.

How to Develop on a Mac and Test on IIS

I'm using a Mac for web development, and have a business requirement to use IIS for my web server. I'd like to be able to test my code in IIS before committing and deploying my code to the production server.
I know I could run a VM (I've used Parallels, VMWare Fusion and Virtual Box in the past). The downside is that this uses memory & processor power from my Mac.
Is there an easy way to watch my development folder and automatically copy new/changed files from the Mac to the test server running IIS? Are there any issues around file owner/permissions on Windows for these files? I know IIS can be persnickety sometimes about serving files if the permissions are incorrect.
Basically, I want to avoid running Windows/IIS on the Mac. So what are my options?

Build definition to deploy to remote private server

I have recently learned about Visual Studio Team Services continuous integration and I would like to add a build-step in my build definition to deploy the website files to a remote development server. Similar to what the Azure Web App Deployment does but to my own hosting server. I have figured a way to do this using the Windows Machine File Copy or using a custom PowerShell script, but the problem is, I have to open up my server's ports for SMB to get this working.
Is there a list of IP addresses I could white-list that Visual Studio Team Services uses? From 4 build tests, I managed to get four IP addresses:
- 13.80.13.96
- 40.114.244.33
- 40.114.240.144
- 104.47.152.33
This does not look very promising.
I may be complicating things, so is there a better way of doing this securely?
SMB shouldn't factor into it. The Windows Machine File Copy task uses WinRM. For security, make sure you use HTTPS and valid certificates in place.
There is no list of valid IP address ranges for the hosted build agents that I'm aware of.
You can also add a "Command Line" task to use MSDeploy to publish the website if your private server run with IIS. (Set the "Tool" area in "Command Line" task to "C:\Program Files (x86)\IIS\Microsoft Web Deploy V3\msdeploy.exe" if you are using Hosted Build Agent.)
Some reference links:
Using MSDeploy to publish your site
(MSDeploy) Deploying Contents of a Folder to a Remote IIS Server

How do I run (debug) WCF REST Service application on local IIS7 server

As the question says, I have a problem running the web app on local IIS.
Here is my situation:
WIndows over Oracle VM VirtualBox running on Linux Ubuntu.
Bridged Adapter so that Windows box gets local IP from my router.
Visual Studio 2010 + sp
WCF REST Service application plugin for project template
The application runs when using visual studio development server (on localhost).
Target framework is v4.0
What I need is that the application runs on IP instead on localhost (so I can consume it on remote computer in LAN), so I configured IIS7.
Here is IIS configuration:
I created a website with target framework v.4.0
I binded the site to my local IP on port 80
Path to the site is /inetpub/wwwroot iisstart.htm as default document
IIS runs ok. If I open "http://my_local_ip" I get the welcome logo.
The problem is in visual studio.
When I go to project properties "Web" section and select local IIS over vsd server is where I get lost. If I set "Project URL" to "http://my_local_ip/some_name" visual studio complains that it cannot find IIS server and so it was unable to create the virtual directory. I tried manually adding virtual directory in IIS manager, but no effect. If I use "http://localhost/some_name" as the "Project URL" the virtual directory gets created, but it makes no sense does it?
Could some one please enlighten me?
If I use "http://localhost/some_name" as the "Project URL" the virtual directory gets created, but it makes no sense does it?
I think you are mixing two different things here. When you ask VS to use localhost as the IIS Server for your project, it will connect to the local IIS to perform configuration tasks. If you ask VS to use "my_local_ip" you are telling VS that you IIS Server is remote, and therefore VS will use remote administration to configure IIS (VS can't know that my_local_ip is the local computer).
But remote IIS admin isn't enabled on a default WinServer box. Furthermore, it would require some additionnal network config. You should therefore tell vs to use the local server.
In fact, IIS site bindings and VS deployment parameters are too completely different things. So, deploy your site on http://localhost/your_site.
However, I don't really like the prospect of using VS debugging deploy to deploy a real app. The directory will contain all your project files... You should:
create your site on IIS manager and setup a virtual directory.
Either
ask VS to publish the site to a directory (your virtual directory)
ask VS to publish a WebDeploy package, then ask IIS manager to import the package.

Debugging ASP.NET MVC project in VS2010 and accessing on networked computers

I'm wondering if it's possible to allow users on my local network to connect to an ASP.NET MVC 3 app I'm running through VS2010 on my local PC. The purpose is to let others test during some rapid application development without deploying to a server.
By default, the port seems to be blocked. Is there a setting in VS2010 or IIS Express that I can change to allow access to it?
By default VS sets localhost bindings in applicationhost.config file (%userprofile%\documents\iisexpress\config\applicationhost.config), so you cannot access it from other machines.
To access your site from other machines,
you need to update your site bindings (in applicationhost.config file) and add a site binding with your machinename
Run VS as administrator
If firewall is blocking your port, unblock it
Following link may help you
Configure IIS Express for external access to VS2010 project

Resources