About 2 years ago I worked on a WCF app, using VS 2008. I was using BasicHttpBinding. I got it onto a Windows 2003 Server R2, and then other projects came up, demanding attention. Now I'm trying to get back at it, only now I want to use VS 2010 to write the client side of the app (it's going to be a WPF app). I'm getting an error, but before I get into that I just want to know; can a .NET 4.0 app work with a WCF service written using .NET 3.5?
In theory, since you are using the Basic binding, you should be able to use any version of .Net to connect to your service. BasicHttpBinding offers the most compatibility across versions, so you're on the right track.
WPF Calling WCF Using a BasicHttpBinding
http://msdn.microsoft.com/en-us/library/bb943481(v=vs.90).aspx
Related
Quick question
I am doing a Plural Sight tutorial on WCF and they are using the WCF Service Library (as opposed to application.)
When I go to Add new project there is no WCF Service Library. Not under any of the .NET versions.
I am using Visual Studio 2013 for Web Express.
Any one know how I can get it?
Thanks
You can find it under Templates WCF.
( Go to New Project->Installed-->Templates-->WCF)
We have a bunch of ASP.NET apps written in .NET 2.0 (with IIS6 ASP.NET version set to 2.0), visible via Virtual Directories within one website deployed to Windows Server 2003. Does anyone know whether we can set the ASP.NET version within IIS, of all of these to 4.0 without breaking the (.NET 2.0) applications - i.e. no other changes other than within IIS
Any official Microsoft link(s) stating this can be done, would be brilliant also
You should avoid such "big changes". ASP.NET 1.x, 2.0 and 4.0 applications should be separated and held in standalone application pools.
Besides, there are too many breaking changes in ASP.NET 4 compared to previous versions, you should carefully migrate when the time is right,
http://www.asp.net/learn/whitepapers/aspnet4/breaking-changes
I have a (very) simple WCF written in VB which I can build and publish locally to IIS. Works great.
What I need to do is (somehow) deploy it to a different server which does not have IIS. It's supposed to be run as a windows service.
I have no idea how to do this. All directions on MSDN seem to be for VS 2010 (we're using 2008).
Any help would be appreciated!
Thanks,
Jason
Check out the MSDN docs
How to: Host a WCF Service in a Managed Application
It definitely has a version for .NET framework 3.5 / VS 2008, and samples in VB.NET.
OR watch this screencast by Aaron Skonnard on Self-Hosting WCF Services - 10 minutes well spent !!
I have been reading documentation about the new features that IIS 7.5 offers regarding the auto start feature of WCF web services.
As far as I have understood, this feature is only available for WCF web services developed under .NET 4.0, but we were wondering if there could be any workaround or tweak in the configuration of a .NET 3.5 WCF web service to take advantage of this auto start feature of IIS. Now we cannot afford upgrading our web service to .NET 4.0.
Thanks in advance for your help.
Jose Antonio Arroba
This is a feature of ASP.NET 4.0 and not WCF, so an upgrade is necessary. Sorry to disappoint you. One more argument for the management to speed up the upgrade, because I am sure it's political and not technical. If it was technical you would already be happily running .NET 4.0.
I am planning to host the WCF services for one of my project on App Fabric. When i installed App Fabric it asked me to install the .Net Framework 4.0. I Can able to configure the WCF services written in 3.5 on App Fabric but i have to select the Asp.Net v4 as an App Pool. I feel the it using CLR 4.0 for the service.
Question is can i host my WCF 3.5 service on App Fabric as we are developing the solution in 3.5 and there is not much scope to migration to 4.0. Will is work?
The first release of Windows Server AppFabric has two parts:
AppFabric Caching Services, which can speed up access to frequently accessed information such as session data used by an ASP.NET application.
AppFabric Hosting Services, making it easier to run and manage services created with Windows Communication Foundation, especially those built using Windows Workflow Foundation.
Looks like you can not use hosting services in 3.5.
http://msdn.microsoft.com/en-us/library/ff637712.aspx
http://social.technet.microsoft.com/wiki/contents/articles/hosting-net-framework-3-x-services-in-appfabric.aspx
As far as caching goes it depends on the version, this article http://msdn.microsoft.com/en-us/library/ff381375.aspx#_Toc247686147 states:
NOTE: Beginning with the Beta2 version, the .NET framework requirements will change as follows. The Cache Service will require .NET 4.0 to be installed and Cache Clients developed using .NET 3.5 SP1 will be supported.
AppFabric only works from .net 4.0, see:
http://developers.de/blogs/damir_dobric/archive/2010/04/29/appfabric-and-net-framework-dependencies.aspx