WPF 客户端与 ASMX 服务通信时性能会受到巨大影响，为什么？

发布于 2024-11-26 07:16:14 字数 795 浏览 2 评论 0 原文

我有一个 WPF 桌面应用程序 ( .NET 4.0 )，它正在与使用 .NET 2.0 编写的现有 asmx 服务进行通信
这是我们用来访问服务的代码

 Stopwatch s = new System.Diagnostics.Stopwatch();
    s.Start();             
    APMService svc = new APMService();
    UserInfoExtended[] Users = svc.FindAllUsers(LicenseKey);
    s.Stop();
   TimeSpan ts = s.Elapsed;
   string elapsedTime = String.Format("{0:00}:{1:00}:{2:00}.{3:00}",
                     ts.Hours, ts.Minutes, ts.Seconds,
                     ts.Milliseconds / 10);
    MessageBox.Show("WS CALL" + " :  " + elapsedTime);
return Users;

现在，当我第一次运行此代码（它连接到按钮单击）时，大约需要 19 秒。当我再次单击该按钮时，只需要不到一秒钟的时间。这是 100% 重现。令人困惑的是，我针对 Web 服务 (.NET 2.0) 编写了一个控制台客户端，每次只需要不到一秒的时间。我在这里缺少什么。
这是 WPF 的事情吗？它与 asmx 服务的（反）序列化器交互的方式。该服务位于 .NET 2.0 上的事实是否导致了问题。
欢迎任何建议谢谢

原文

I have a WPF desktop application ( .NET 4.0 ) that is talking to an existing asmx service that was written using .NET 2.0
Here is the code we are using to access the service

 Stopwatch s = new System.Diagnostics.Stopwatch();
    s.Start();             
    APMService svc = new APMService();
    UserInfoExtended[] Users = svc.FindAllUsers(LicenseKey);
    s.Stop();
   TimeSpan ts = s.Elapsed;
   string elapsedTime = String.Format("{0:00}:{1:00}:{2:00}.{3:00}",
                     ts.Hours, ts.Minutes, ts.Seconds,
                     ts.Milliseconds / 10);
    MessageBox.Show("WS CALL" + " :  " + elapsedTime);
return Users;

Ok now when I run this code for the first time ( its hooked up to a button click ) it takes about 19 seconds. When I click the button again it takes less than one second. This is 100% repro. What makes this baffling is I wrote a console client against the webservice ( .NET 2.0 ) and it takes less than one second every time. what am I missing here.
Is this a WPF thing? the way it interacts with the (de)serializer for the asmx service . Is the fact that the service is on .NET 2.0 causing an issue.
Any suggestions welcome
Thanks