> How many DLLs are there in the project? Is there any interop DLLs? I
> suggest you may create a new web service project, then add all class and
> modules in your original project, compile it and test again. Can this fix
> the problem?
>
> Luke
2 in the test web service. When we add the others from our main app
there are maybe 5 additional. I'm not following what you're
suggesting. The dll's from our main application aren't used by the
test application, so there are no references to add or anything like
that. Just the act of copying unrelated dll's to the bin directory of
the web service seems to have a major impact on performance. Any other
ideas?
Tim - 11 Sep 2004 05:27 GMT
TOTAL guess...if it's working quickly on the local SQL server, but slowing
down on the connection through the network you may want to check to see if
the web service doing some kind of autentication with the domain that is
causing it to slow down. There may be issues converting from 2003 security
authentication to 2000 security autentication. For kicks, if you can you
may want to try putting the SQL DB on a 2003 machine to see if it plays
nicer together.
I was reading this article
http://msdn.microsoft.com/msdnmag/issues/03/06/WindowsServer2003/default.aspx
and it mentions about running IIS 6.0 in 5.0 protection mode. "If desired,
you can run it in the three IIS 5.0 protection levels as well." You might
try that to see if that simulates IIS 5.0 on a 2003 box. That might help
identify if it's a IIS 6.0 issue.
Tim
> > How many DLLs are there in the project? Is there any interop DLLs? I
> > suggest you may create a new web service project, then add all class and
[quoted text clipped - 10 lines]
> the web service seems to have a major impact on performance. Any other
> ideas?
[MSFT] - 13 Sep 2004 08:52 GMT
Thank for Tim's suggestion. Plus, the delay may also occur inner the
assembly. At runtime, ASP.NET will load classes from assemblies in BIN
folder. For example, when a client request. webform1.aspx, ASP.NET will
load class "Webform1" from the DLLs. Therefore, after you copy the DLLs to
the test project's BIN folder. They are also scaned by the ASP.NET. This is
why I suggest to rebuild your original project to see if this a problem in
the assembly. You may also consider Tim's suggestion, to check if this a
security issue.
Luke
Yan-Hong Huang[MSFT] - 15 Sep 2004 10:28 GMT
Hello Petes,
I was reviewing this issue thread. Do you still have any more concerns on
it? If there is any question, please feel free to post here and we will
follow up.
Thanks very much.
Best regards,
Yanhong Huang
Microsoft Community Support
Get Secure! ?C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
-http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.as
p&SD=msdn
This posting is provided "AS IS" with no warranties, and confers no rights.