I have an application that is moving over from WCF Http to named pipes since everything is on the same machine. Those in charge have decided not to reference the DLLs directly, so that's not an alternative. I'm okay moving over to a tcp connection instead, though I don't know that it gives us any direct performance benefits over http on the same machine. The production host is going to be a IIS 7 server, not a WAS or other service. My machine has IIS 5.1, Cassini, and IIS Express.
I've tried the following:
Virtual Box running windows 7 on my XP machine. The installer craps out.
Named Pipes on Cassini, not supported.
Named Pipes on IIS Express, not supported.
Googling the hell out of the solution, nothing useful found.
What is the best/recommended way to develop WCF NetNamedPipes on XP that does not have IIS 7?
On XP, the WCF binding to named pipes works well for a service which is custom-hosted in a Windows Service process. But if you don't want to build a custom host you are out of luck: the only protocol supported for hosting in IIS5/6 is HTTP.
WCF service hosting in IIS for protocols other than HTTP depends on WAS, which requires IIS7. This constraint applies equally to the TCP binding, so that is not a workaround as you suggest.
It sounds as if your application is intended to be IIS-hosted in production. If this is a given, I think you have no alternative but to change to a new development platform which supports the target environment.
Related
I'm Brazilian, and I apologize for my English, which is very bad
I've been facing a problem for some time, and I'm tired of looking for a solution in Portuguese.
I created a WCF service to be consumed by Android, hosted on a computer that I have at home with Windows server and iis installed, configured all the correct port releases for the application to work on the phone, but it has the following error in the execution: System.Reflection .TargetInvocationException
So I decided to host the WCF service on an external server, I used the number service. I just uploaded the files to it and changed the address references in the application to communicate with the WCF, and then it worked, so I guess some configuration that has to be done in IIS or in Windows itself, I'm waiting for some help. Thank you
I work as a C# developer and we have many .NET web services that we use. I am doing some at home development and want to do something similar. I have a database (SQL Server 2012) on a home PC running Windows Server 2012 with IIS 8 installed. I have created a WCF web service in Visual Studio (C#) and it compiles to a .svc file. This just facilitates data exchange between my SQL Server Database and the application I am writing.
I am unfamiliar with how to host the WCF service so that the Windows Form application that I am writing that will be installed on many non-local machines can access it. I figured a WCF service would be the best choice for accessing my database for the WinForm application over the internet.
I also have a domain with a basic Windows package on 1&1.com leftover from a previous project if that helps.
Can anyone give me some steps to get my WCF service hosted so it can be accessed over the internet? Please ask if I forgot to list any needed information.
Two common ways are to host your WCF service from IIS, or to self host it yourself from within a simple wrapper program that acts as a TCP server.
See http://msdn.microsoft.com/en-us/library/ee939285.aspx
The simplest way is to setup IIS and just publish your services like you would a web application; your service will exposed over http/https. Use an appropriate binding like wsHttpBinding or BasicHttpBinding depending on your security needs. Read up to understand the different bindings and what each does and does not support.
In order to host WCF via IIS, at least on Windows Server 2003 and 2008, make sure you follow the install steps, such as adding .NET 3.5.1 / WCF options on older platforms. I believe Server 2012 includes it within .NET 4 framework, but I haven't yet done it on 2012.
Google "WCF hosting IIS" for steps / setup guides.
There are also hosting providers that specifically provide WCF hosting solutions, though I'm pretty sure your current provider, since it supports IIS, should do fine.
I'm having problems when publishing services on IIS.
First, I will describe my scenario.
At the moment I have an WPF app in C#.
Also I have a web site (published in IIS through HTTPS) that need to communicate with the c# application, therefore I decide to publish the methods I needed through a REST web service also through https:
WebServiceHost serviceHost = new WebServiceHost(typeof(QESWebService), new Uri("https:xxx/WS/");
When I tested it on Windows 7 there were no problem. Everything works fine.
But now, when I try the application in Windows XP, it is not working! I cannot launch the application because the port 443(for the web service https) is already in use.
I cannot find a solution different to dont use https on one of the sides, but I really need it, What can I do?
Thanks in advance
If you already have a web application/service running on the IIS using SSL then you need to change some configuration settings
Here is an article about Multiple SSL Web Applications on Port 443
So as the question goes, I have hosted a ASP.NET and C# website in IIS in my Windows 7 Ultimate OS. Not I need to be able to access the same site from ubuntu which is actually a virtualized OS running under VMWare.
I am able to access the website in my Windows 7 pc without any problems. But inside the Ununtu there seems no way to do the same.
I searched many forums for the same, no luck! Disabled the Firewall(Actually) to make sure no security issues arise but still not able to do the required thing.
This is the error :
Server not found
Firefox can't find the server at www.google.com.
Check the address for typing errors such as
ww.example.com instead of
www.example.com
If you are unable to load any pages, check your computer's network
connection.
If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.
Any ideas?
the vm can access the host machine? if you use NAT connection mode seems cannot communicate with the host. Try Bridge instead?
I know (Windows Activation Service) WAS is advertised as part of Windows 2008/Vista/7 but since it appears under .NET 3.5 framework components in Control Panel Windows Components, I was wondering if anyone knows/has managed to run in under Windows 2003 as well.
I'm trying to host a WCF server in WAS under Windows 2003 (written in .NET C#)
Alternatively, does anyone know of any good open source application servers out there that can be used to host .NET servers? (TomCat for .NET?!)
WAS is a part of IIS7, which is available on Vista and Win Server 2008 and up only.
On Win Server 2003, you can either host your WCF service in IIS - which limits you to just http (basicHttp or wsHttp), or - my preferred way - you can host your WCF service yourself.
Typically, you would host your WCF service in a console app for testing/debugging purposes, and then put it inside a Windows NT Service for production - this runs around the clock, with no one logged in, and it supports ALL the WCF bindings (not just http, but also Net.TCP, NetNamedPipe, MSMQ and so on).
Marc
You can always roll your own WCF host. I've used this concept as an example.
http://www.codeproject.com/KB/WCF/generic_wcf_host.aspx
You can host a WCF service in IIS on Windows 2003, if you use basichttpbinding or wshttpbinding.
You could also host a WCF service as a windows service on windows 2003.
WAS is not available on Windows 2003.