I created Virtual machine in Azure, i set up server, installed web deploy 3.6, management service
But if i want to publish my website to this server i am still getting this error
You could check this blog.
Please ensure web deploy service is listening. Also, you need open port 8172 on Windows Firewall and Azure NSG.
Related
I am trying to deploy a .net core c# app to an IIS running on Windows Server 2016. I created a publish profile. I click on Validate Connection button and get the following error, that I need to install Web Deploy and that Web Management Service should be started:
I did install Web Deploy 3.6 and the Web Management Service is definitely running.
Here is my profile. The Site Name is AppPool\WebSiteName. User name is the same as I logged in on the server with.
What am I missing?
Figured out the problem. The Server entry needs to have the protocol. So http://winserver instead of just the name of the box.
I looked into Azure cloud solutions and came up with below question regarding developing web app locally.
It seems like, if you develop Cloud Service, you can run locally with Azure emulator, if you develop Azure Fabric Cluster, you can run your cluster locally.
However, if you develop Wep app (part of App service) and you want to debug your app locally, you can either connect remotely your debugger to running web app or run the web app on your local iis.
Issue is, debug on azure emulator or running on local cluster seems to illustrate running the app on cloud better than develop on your local iis.
Am i missing something, or the development experience on App service lacks the option to run locally on "cloud like" environment(excluding the option of remote debug)?
Thanks a lot!
There is no emulator for App Service because at its core it is just an IIS farm (the Windows App Service at least).
We run apps locally on IIS Express + SQL Server 2016 Developer edition, and that corresponds quite well. Of course if we wanted we could set up an IIS farm locally and use that, but I think that's unnecessary.
You can get a bit closer to actual environment if you use the App Service Linux offering, as there you will run everything on Docker containers. So you debug on local Docker and then run it in prod on Docker.
I would also recommend you to check out deployment slots on App Service, as a staging deployment slot can help you find problems that occur in the cloud environment before you swap it into production.
In my personal experience developing apps for App Service, problems in the production environment were not caused because the environment was very different, but because we overlooked something with the database, made a mistake in a Web.config transform etc.
I have WCF web service for connecting to a SQL Server database on a server and to return data in JSON format.
I can run this web service on my laptop from Visual Studio 2013 correctly when I am connected to the network what server is in it, with this url :
http://localhost:51220/Service1.svc/checkLogin?name=username&pass=password
I want to publish this web service and put it on a server (where the SQL Server database is installed). To access the web service from the internet, a url like this will be used:
http://serveraddress:51220/Service1.svc/checkLogin?name=username&pass=password
Now, how can I publish this web service from my laptop to the server? What configurations should be set in the publish settings?
And after publish, I have 3 files: web.config, service.svc and Sample.dll, what can I do with them? :)
I am very amateur on make binary from WCF web service.
You should host the service in the IIS, a simple tutorial can be found here:http://www.codeproject.com/Articles/550796/A-Beginners-Tutorial-on-How-to-Host-a-WCF-Service
I have no prior experience working in the .NET stack. Not sure if this is a common requirement. I have developed a simple .NET web service which accesses the COM library provided by a label printer SDK to send print jobs to the printer connected to my machine.
I need to distribute the web service to clients so that it can be hosted on their machines locally. Set up should be minimum - something like an installer which will do the needful to deploy the web service locally.
I assume that any windows machine comes with .NET bundled.
I understand that IIS is the windows equivalent of apache-tomcat. Does is it come bundled with all windows machines? If it does, I figure I can write some scripts to deploy the web service to IIS using the ".deploy" file generated by Visual Studio.
Are there any betters way of doing this ?
So my question is :
How do I distribute a web service that should be be hosted and run locally on the client's machine without forcing the user to download and install a web server and deploy the package?
Edit:
So, I gather IIS is not supported by home editions.
I made a site using VS10 Ultimate [ASP.NET] and when I build & run it runs the severer locally, while I want to test it for security issues via Linux.
How can I run it globally ?
Thank you!
Your development machine probably has IIS installed. Copy the code or the compiled code to the web root of this installation. If you want to put it on another computer, then that will need to have IIS, relevant version of .Net installed.
It would also help if you can setup your local DNS to resolve the name for your computer within the LAN setup so that you can reache the machine using a name rather than the IP.
This will allow you to test the security issues that are client side. For Server side security issues, you will need to create a server in your LAN that is configured similar to the actual server where you would be hosting your site.
You need to set up the site in IIS Server installed in your Windows machine to run it locally
See the links to learn more:
http://www.beansoftware.com/ASP.NET-Tutorials/Set-Up-IIS-ASP.NET.aspx
http://support.microsoft.com/kb/323972
You need an ASP.NET hosting service.