I have been through tons of threads and am unable to find the correct answer for my question. I have created a very simple WCF service on my development machine using visual studio 2010. The service works correctly when using VS to host it. I have even had success creating a small c# application to consume this service. However I now need to move this service to IIS on my work's development server. I have tried following several guides online but nothing has worked so far. Any help would be greatly appreciated.
if you are able to execute your wcf service using WCFTestClient successfully and not on IIS
that means problem is in endpoint configuration. I suggest have a look once again endpoint suggestions.
Using Web Deploy to publish from Visual Studio to a remote web server requires additional installation of Web Deploy on the server http://www.iis.net/learn/install/installing-publishing-technologies/installing-and-configuring-web-deploy
Visual Studio generates an output log during the web deploy publish that may have additional information on why it is failing. Sometimes there are permission issues to work through as well http://blogs.iis.net/krolson/archive/2009/11/04/using-iis-manager-accounts-for-web-deployment-tool-msdeploy-delegation.aspx
You can also generate a Web Deploy Package with Visual Studio and manually deploy it to the server http://msdn.microsoft.com/en-us/library/dd465323(v=vs.110).aspx
Related
**Hi Guys I just Cloned my project from a repository.
I am getting this Similar error
The Web Application Project […] is configured to use IIS. The Web server […] could not be found.
I do have IIS Manager on my pc. one of the solution is to set True on my cs.proj file but when i do it auto imports a port number. when i try to run the application with that port number the application hangs(load forever).
What are possible ways to solve this error ?**
Just to register an answer for all getting into the same problem under the same scenario, as we discuss and resolve it from the question's comments:
Ps: as i said this solution works for this particular scenario, maybe anyone else has to apply a different approach!
In this case, try to follow the below link for other solutions!
The Web Application Project [...] is configured to use IIS. The Web server [...] could not be found.
Reset the IIS; (https://learn.microsoft.com/en-us/visualstudio/debugger/error-the-web-server-is-not-configured-correctly?view=vs-2019)
Publish the project;
Add it to IIS Server;
Run it using IIS Local (not the IIS Express)
I have a functioning API that I can launch from Visual Studio 2015, I can also clean and build it. It outputs a dll file with other supporting files but I don't understand how I take the build files and actually host them as an API.
How can I host my API 2 project externally?
Like most Microsoft web technologies, you'll most likely have to host them on a web server running IIS.
http://www.c-sharpcorner.com/UploadFile/2b481f/how-to-host-Asp-Net-web-api-on-iis-server/
Visual Studio has a wizard for publishing API services to IIS.
http://dotnetmentors.com/web-api/host-asp-net-web-api-in-iis-using-visual-studio-publish.aspx
If you don't have an IIS web server, you can host on the Microsoft Azure cloud platform which will provide an instance of IIS for you.
http://www.asp.net/web-api/overview/data/using-web-api-with-entity-framework/part-10
I got an ASP.NET project. I'm going to send the project to a server company where they will host it. How do I prepare it to be hosted? I assume I cant simply send the whole project to them. What are the steps to prepare the project to be readable in their server?
This is my first project, never done it before.
Used Visual Studio 2015, WebForm/ASP.NET.
It's going to be hosted via a server company, no clue about anything about their servers.
Also got a MS Access database in App_Data folder within the project.
PS: I found "Publish" by right-clicking the project in Visual Studio's 'Solution Explorer'. I've been checking out this link but it's really confusing.
Any help would be greatly appreciated.
When you publish an application, most of the time it will run just as it does when you debug it, but on the server. All the binaries are copied there, with the Web.config, and most like all you have in your application, but the source code will not be avaiable of course. You don't need to send the application to the company which will host your application, most likely they will give you the server address where your application will be published, they will create an account for you, with some permissions, and credentials. And of course, you can read more about IIS server, it will be pretty relevant to you, and you can configure yourself a server where you can publish your application, just to see how it works.
Set up your own application on your own IIS and experiment locally until you have all stuff in place. Then copy to you hosting environment.
Later on you can script this process to have full control over what you need in dev and prod respectively.
I have a web service project and simple test application. I can debug the web service from Visual Studio 2008. However, there exist a real client application, but it is on another machine. ASP.NET Development Server does not allow connections if they are not from localhost, or so it seems. Is there a way to debug a web service, if client application is on another machine?
Edit
The tool that I used is Trace Utility from Microsoft SOAP Toolkit. Further explanation can be found here (works on XP; see continuation story for Windows 7 solution). There was problem with it though. My remote client fetches the WSDL first, and then creates URL based on values in soap tags found at the end of WSDL. So client gets redirected to localhost, which is not good.
I found my problem though, but I'll leave the question open until I find the time to try debugging via IIS.
Install a virtual directory into the IIS on your local machine. If you don't have IIS, install it. Once IIS is installed and configured on your local machine, you should be able to use either the IP or create a dns alias for that IP to access the web service that way.
I'm using SoapUI basic version to fake the SOAP requests to the web service, which is running in debug mode in Visual Studio, from the local computer.
You can use IIS (or Cassini Web server) - for debugging, attach VS 2008 to correct process (for example w3p.exe(IIS6 or greater) or aspnet_wp.exe(IIS 5)).
In Visual Studio 2010 I have created a WebService (WCF) Application and a client to consume said service.
My 3 options as far as what servers to use for debugging are: Visual Studio Development Server, Local IIS Web Server, Custom Web Server.
I know I can't use the VS Development Server if I want my service to be accessible outside of localhost. So I installed IIS (Control Panel>Add/Remove Programs>Add/Remove Features). When I select this option in Visual Studio 2010 it doesn't seem to work. I'm not sure what options I have to setup so that other machines can run the client to consume this service.
By default VS set the Project URL to: http://localhost/MyService. Oh, and I'm working with .svc files (not .asmx) if that makes any difference.
Common problem when you intall IIS after the framework.
Go to your Windows\Ms.Net\Framework\<version> folder and execute aspnet_regiis.exe. It's a commandline tool.
To save having to install IIS you can configure a proxy - such as Fiddler - to redirect certain incoming traffic to localhost.
Because these new requests are "appearing" (via the redirect) from inside your machine, Cassini will respond.
The process is covered in this answer: https://stackoverflow.com/a/4428747/1016183 under "Option #2: Write a FiddlerScript rule"
You can right click on Project and do publish. This will generate the required files for your deploy.
In order to debug your app, you can use the Visual Studio built-in host or IIS.
In your project properties, under Web, you can select "Use Local IIS Server".