Suggested Life Cycle for SSRS Web Proxy

Question

I am using the SQL Server Reporting Service web service api to render reports using the ReportExecutionService proxy in the asp.net web application.

My question is: should I create a new instance of the ReportExecutionService proxy every time I create a report, or use a singleton instance, the recommended approach? (e.g. for performance reasons, etc.).

Answer 1

What wcf bindings are you going to use? In general, you can reuse proxies, and in a single-user single-threaded application, this is a good idea.

singleton - ASP.NET - .

, ( = , , ASP.NET).