I am using WCF with asp.net 4.0 (using Dynamic Data).
I need to tell my Client how many domains does he require to book. So, do i require a separate domain/sub-domain for WCF or just 1 domain for website and WCF would work.
FYI: We might acquire a hosting space at shared hosting servers like GoDaddy.com. I need to calculate the hosting cost of the application.
Thanks
You can host WCF in IIS, or you can host it in a separate program/service. If you're hosting it in IIS, you can create a .svc file and have it live alongside your other ASP.NET pages.
So it's entirely possible to have your WCF service live in the same domain as your ASP.NET app.
Related
I am a .NET developer, I created an ASP .NET web application which communicates with windows app clients and xamarin android clients. The web application in fact is a bunch of web services which upload data (images) to the disk of a web server, and manage SQL Server databases. The objective of the entire system is to create budgets for the building company of my brother's, he is a contractor.
I want to host the web application on a shared server, but my web application lacks a web page or user interface, and according to most of the hosting companies in the terms of use they say that files on their servers must be related to the website which one should host.
Are there hosting companies willing to host an application like mine?
You're looking for web application hosting, not website hosting. Azure App Services will do what you're looking for but that might be overkill. This also might be better answered in one of the other stack sites.
I'm researching on how integrate 2-way SSL in two IIS servers
ASP.Net web site is hosted in one server.
ASMX web services is hosted in another server.
They both run under Dot Net 3.5 in Windows Server 2003.
I am aware IIS needs to take the follow steps as part of 2-way SSL.
Install certificates through Certificates MMC.
Configure both web applications to require secured channel SSL.
But I cannot tell what steps need to take in my ASP.Net and ASMX application.
Does IIS handle 2-way SSL internally? (Provided the server is configured correctly)
Do I need custom coding to handle 2-way SSL in my application?
I found plenty of articles reference to WCF setup, which breaks down into two steps
Setup WCF configuration to use certificate explicitly.
Setup that certificates to IIS server.
However, I’m not finding anything relevant within ASMX context or within ASP.Net context.
Thanks in advance.
I' deploying two services, one of them is a website and the another is a WCF Service for desktop applications.
I have one web site called contoso2.azurewebsites.net and that place I place my web site, but also I would like to deploy my WCF service, the question is... I need to create another web site service to deploy in it? Or it can be in the same place?
I think you can. If you have an ASP.NET web application, you can add some .svc files for your WCF service. They will be deployed as part of your web site. Then you can use your website through http://contoso2.azurewebsites.net/ and use your web service through, let's say http://contoso2.azurewebsites.net/api/ProductService.svc
Combining your website and services into one application is possible, but you can also host them in two seperate sites within the same web role.
You basically have to:
Create a cspack with multiple sites
Map the internal IP address of the machine to a DNS of your choice in the hosts file when the role starts
More details and scripts on my blog: http://thomassmets.wordpress.com/2013/01/21/a-web-frontend-with-a-wcf-backend-in-azure/
The service has been debugged and is running in its own website.
We already have the SSL certificate and DNS configured for the application. It would save some work if we could host the service in the application.
Application is hosted and used behind our firewall. No public access at all . No cross domain security issues.
Application and service will be hosted on the same server even if in different websites. That's the plan for now anyway.
How do I do this? Or should I just consume the service from the website it’s currently hosted in?
I would keep the service as a separate ASP.NET application. It allows for more flexibility. But if you wanted to do it, simply copy the .svc file, along with all the service and data contracts to the ASP.NET application and modify web.config to add the <services> section. Or if those data and service contracts are in a separate class library all you need is to reference this class library.
I have an asp.net 3.5 site and I've just written some wcf services. It is ok to just drop the .svc file right alongside my .aspx files or should I move my .svc files onto a separate virtual directory and IP and call it something like services.mydomain.com.
Just wondering what best practices are. Maybe it doesn't make any difference? I have a client app that will update the database that my web site uses. It updates through an IIS hosted wcf service.
IMHO it would be better to isolate the web service into a separate virtual directory and application pool. In this case the client application and the web service don't share the same AppDomain and if one fails the other will continue serving requests.
In our project we tend to keep them in separate virtual directories. I like to regard the service as something that can be used by more than one client, and so I like the deployment and hosting of it separate from the client. Of course, if you just stick it in a separate virtual directory you can argue to what extent the hosting is separated, but at least it is separate on a logical level, and easily moved to separate physical hosting if necessary.
You definitely don't want to have them in the same place - not least because it makes it hard to configure the appropriate level of security. It also makes configuration simpler as they won't share a web.config.