All geek questions in one place

Temporarily Facading asmx Web Service with WCF Service

I have an application, which is an asmx web service written in .NET 2.0, with some business logic and a repository located beneath it.

The plan is that this web service will serve as an API for applications that need data that it stores and retrieves.

In the long run, I know that the web service is likely to be replaced by the WCF service when the .NET 2.0 code base is reorganized and becomes the .NET 4 code base.

To reduce the impact on API consumers, I am considering whether to abandon the WCF service as a facade over the asmx service. This will remain in place, and the .NET 2.0 code will be reorganized. When there is no .NET 2.0 code left, the asmx service will disappear, and the WCF service will talk to business logic without the asmx service.

My questions

What overhead may occur?

Is there a better solution to this problem?

+3
source share
2 answers

I read your question as "can I reference the .Net 2.0 component from the .NET Net WCF service"

This link confirms

.NET Framework 4 , .NET Framework 1.1, 2.0, 3.0 3.5. , , .NET Framework, .NET Framework 4.

+1

/ . , .

, WCF , BasicHttpBinding. , :

  • WCF ( ).
  • , , .

EDIT: , WCF. , .

+2

Source: https://habr.com/ru/post/1793900/

More articles:


All Articles