I am using AppFabric to implement caching. While configuring an application A using IIS Manager, I have imported the application in it. But after that, there is no Mange WCF and WF link in the IIS Manager. What do I do?
AppFabric consists of two main features : AppFabric Hosting and AppFabric Caching.
AppFabric Hosting help you to deploy and manage workflows (WF) or WCF services. Yes, it includes an extension of the Internet Information Services management tool that enables us to monitor the performance of services and workflow.
AppFabric Caching in a in-memory distributed cache. It can be used in any application. Windows PowerShell is the exclusive management tool for this feature (no IIS). However you find find here a custom tool on codeplex.
AppFabric caching service is configured during installation and cache clients only need a few config to use it. This post from Scott can help you. This other SO post can help you.
Related
It seems NServiceBus is moving from configuration to Code. What are the additional benefits of hosting using NServiceBus.Host.exe vs hosting an endpoint yourself?
Not sure what configuration via code has to do with hosting?
The NServiceBus Host offered features to make it easier to host your endpoints. Since then we have made a lot of this stuff easier or the features have been added to specific packages. So at the moment, it's as easy to host it yourself. And you'd have more control over setup, etc. For example the host has its own configuration and the endpoint itself as well. Some users have issues with assembly mappings that need to be in both places, etc.
So if you want to know how you can host yourself, there's documentation on that:
General hosting
Self hosting sample
Windows Service Hosting
Web Application Hosting
Service Fabric Hosting
Shared Hosting in Azure
and much more on our documentation website.
I have few WCF services, deployed at IIS, which are consumed by some android devices. I'm have to move all my databases and services to Azure. I googled to find out how to deploy WCF at Azure, and found a concept of WebRole and Azure Cloud Service project. See THIS SO POST
But at the same time, I just tried creating a new webapp in Azure and simply published my WCF services project there, and it worked fine. (I tested with client).
My Question is,
What is the difference between the methods mentioned in the post I linked, and the way I deployed? I'm concerned, because I'm expecting high amount of requests.
Is it okay to deploy my already created/ready services the way I did?
What is preferred?
Both (WebApp and Web role) will work for your scenario.
The main difference between this two way is that Web role allows you to connect to it through remote desktop.
You can keep using WebApp and configure Auto Scaling (based on CPU usage or at a specific time).
I have a WCF service that we created. Are there any steps that you need to do to convert it to be able to run on AppFabric? In the past when I have created services for AppFabric I have used the AppFabric Item type in Visual Studio.
Short answer, no. You need to install App Fabric on IIS, and you can configure anything there. Nothing special needs to be done on the C#/WCF side. However, you are able to adjust the config file of your project to alter the App Fabric settings, just as you would for IIS.
My head hurts so much I think I need a bottle of aspirin...
I've created a WCF service and, with help of others from this site and the department I work in, the WCF service is running as a service on my development machine. Tested it with a console app and it works.
But, it's not supposed to be on my development machine. It needs to be on a different server.
This is difficult because the server it is supposed to reside on DOES NOT have Visual Studio installed on it.
So I cannot run the VS 2008 Command Prompt with installutil to run the WCF service as a service on that server.
Broadly speaking, you've got three options, all of which are described on MSDN:
Host the service under IIS
Self-host the service in any managed .NET application
Host the WCF service under a Windows Service
Which one is right for you depends on what your service is for, how it'll be consumed, how scalable and secure you need the set-up to be, and a dozen other things besides. Without knowing a bit more about what your service does and how it'll be used in your organisation, it's difficult to make a recommendation.
IIS hosting is easy to set up and is the way to go if you want to leverage all of the industrial-strength hosting functionality that a full-blown web server offers.
Self-hosting is quick and easy - you can knock out a WCF-hosting console app in two minutes flat - but is the clunky solution. You of course have to run the host application as a particular Windows user. Perhaps not ideal?
Hosting under a Windows service is the middle ground. It gives you that always-available functionality without having to be logged in as a specific user, but doesn't offer the configurability and scalability of the IIS solution. It takes a bit more effort than belting out a quick console app, but not much.
The server that the windows service will reside on will have the .NET Framework. INSTALLUTIL is located in the Microsoft.NET\Framework(version number) folder in the Windows directory.
For example, C:\Windows\Microsoft.NET\Framework\v2.0.50727.
No need to write a console app to host your service now (unless you want to).
You can also host your WCF service under IIS, check this out: MSDN - How to: Host a WCF Service in IIS. It really is just a five minute job :)
I plan to start developing with WCF this weekend. Before i get too far along, I'd like to know what I need from my web host? What does our server need to run to enable WCF? Is it standard ASP.NET 3.5 SP1 stuff? Does the host need to do anything to our IIS configuration?
I'm currently hosting our ASP.NET apps, company website, etc. with a third party hosting service. Due to our size, cost, etc. we are using a shared hosting plan and have somewhat limited access to chanign IIS. I'm hoping we don't have any problems that would limit our ability to use WCF.
If you want to host your WCF service in IIS, you need IIS6 (Win Server 2003) or preferably IIS7 (Win Server 2008), the .NET 3.0 (or preferably: .NET 3.5 SP1) framework, and the ability to create virtual directories in IIS (so yes, you need at least some degree of IIS configurability).
That's it! :-)
Marc
You have several options:
You can host in IIS6+ using ASP.NET: simplest, offers integration with ASP.NET runtime (can be disabled to reduce overhead if not needed, imposes requirements on endpoint URLs, restricted to HTTP[S] as transport, all the benefits of IIS worker process management
You can host in IIS7+ using Windows Activation Services (WAS): more advanced, complete control over endpoint URL, can use any transport (TCPIP, HTTP[S], MSMQ, NamedPipes), all the benefits of IIS worker process management
You can host in a custom Windows Service: all the power of WAS except worker process management and you must write your own windows service and you have
For more information, check out this section of the MSDN documentation.