WCF: Implement an Asynchronous Service Operation - .NET 3.5 vs. 4.0 - wcf

Here is an introduction to "Implement an Asynchronous Service Operation" and I wanted to test to handle the request synchronously. I've created a project with .NET 3.5 (VS 2008) and does not work. As my last idea, I converted the project to .NET 4.0 (VS 2010) and now works.
Does anybody know, why does it not work with 3.5?

Related

Running .NET 2.0 apps with an IIS ASP.NET version of 4.0

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

How can I work with Entity Framework 4.2 in .net framework 3.5 for SharePoint 2010?

I know that SharePoint 2010 uses .net 3.5 and since .net 2 (3.5 with sp1) has different CLR than .net 4, what is the best practice to use Entity Framework 4 (4.2) with it?
Is the web service (WCF service) the only solution for it?
If not, what is the best ORM similar to EF from simplicity and productivity prospective is recommended to use to connect to MS SQL Server? (may support oracle later)?
Is the web service (WCF service) the only solution for it?
Yes. You have to do cross process call because your main process is .NET 3.5 and you need another process running .NET 4.0.
What is the best ORM similar to EF from simplicity and productivity prospective is recommended to use to connect to MS SQL Server? (may support oracle later)?
Other alternatives are for example NHibernate or LLBGen Pro. Both are supported in .NET 3.5. You can also try Linq-To-Sql or SubSonic.

Can .NET 4 app call a .NET 3.5 WCF service?

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

Use of auto start feature of IIS 7.5 with .NET 3.5 WCF service

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.

Can I use WCF on Visual Studio 2005?

I am about to start a project which consumes third party web services. Because of a legacy system, I am told that I can only use Visual Studio 2005/.NET 2.0. (Though I would have preferred Visual Studio 2008 on .NET 3.5)
My understanding is that WCF was released with .NET 3.0. So is there any possibility to use WCF on Visual Studio 2005 by using just the WCF assemblies of .NET 3.0? I will then try to convince them that it is just like using external framework which doesn't disturb anything.
You can read here the steps how to setup WCF in VS 2005
http://blogs.msdn.com/jmeier/archive/2007/10/15/how-to-create-a-hello-world-wcf-service-using-visual-studio.aspx
or
Download WCF templates for VS 2005
http://blog.stevienova.com/2007/02/25/net-30-wpfwcf-templates-for-vs2005/
and install .net framework 3.0
Here are some useful links for WCF Extensions and for other useful information.
http://social.msdn.microsoft.com/forums/en-US/wcf/thread/b297421e-5030-47e2-96e1-6d1d9920c9c7/
http://forums.asp.net/t/1331127.aspx
Good Luck!
try this: http://www.zdnet.co.uk/downloads/developer-tools/2007/08/21/the-visual-studio-2005-extensions-fornet-framework-30-wcf-and-wpf-november-2006-ctp-3-39328336/
I hope this helps!