Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / October 2006

Tip: Looking for answers? Try searching our database.

XmlSerializers.dll and faster startup

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Oleg.Ogurok@gmail.com - 23 Oct 2006 15:36 GMT
Hi there,

I have a small console app that makes a call to XML Webservices. The
app runs from a login script. Because of the web service call, it takes

about 15-20 seconds for the app to complete. Most of the delay is at
startup time where SOAP serializers are initialized, e.g. when I
instantiate a proxy class. The actuall calls to XML services are fast.

Is there a way to speed it up? I tried compiling the app in Release
mode with MyApp.XmlSerializers.dll generated but didn't notice any
performance gain.

Please advise,

-Oleg.
John Saunders - 24 Oct 2006 18:06 GMT
> Hi there,
>
[quoted text clipped - 8 lines]
> mode with MyApp.XmlSerializers.dll generated but didn't notice any
> performance gain.

Is the XML simple enough that you can call the web service directly? That
is, don't use the proxy class.

John

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.