470,810 Members | 1,444 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,810 developers. It's quick & easy.

400+ web references in a project

I have a project that contains 400+ web references. When I go to do a new
build, I need to update all the web references to pick up any changes in the
web services they reference.

I select the top one, and shift-select the bottom one... then click
"update." Visual studio goes through every web reference in turn, doing an
update for each one. It also appears to spawn a background thread (or pool
of threads) for each update. When Visual studio says it's done with the
updates, it's not nearly done because the background threads are still
working hard to complete the updates. 100% cpu, and memory climbs up to
700mb or so.

So I wait, about two hours.

Then it's done and I can finally do the build.

Is htere anything I can do to speed up this process? I have to update every
web service... no choice there.

-Mark
Jan 25 '06 #1
4 1001
Oh, and one more thing. The only thing in this project is all these web
references... No actual code. Then we use the resulting DLL in a separate
project.

-Mark
Jan 27 '06 #2
You could alwayd create a script and manually call WSDL.exe.
--
Dale Preston
MCAD C#
MCSE, MCDBA
"marked23" wrote:
Oh, and one more thing. The only thing in this project is all these web
references... No actual code. Then we use the resulting DLL in a separate
project.

-Mark

Jan 29 '06 #3
I havn't done something like that before. Would such a script produce an
identical result? I mean, would the files be the same so that I could go
back to the IDE and compile?... and the project would never know the
difference?

"Dale" wrote:
You could alwayd create a script and manually call WSDL.exe.
--
Dale Preston
MCAD C#
MCSE, MCDBA
"marked23" wrote:
Oh, and one more thing. The only thing in this project is all these web
references... No actual code. Then we use the resulting DLL in a separate
project.

-Mark

Feb 8 '06 #4
There are several options for the scripting, everything from a simple
VBScript application up to a separate C# applicaton. You could create a text
file with all of the URLs to run WSDL against, or you could create a database
or XML file. Or even write an application to search for the URL in the
existing proxy class, and then use that URL to get WSDL.exe to get the
updated reference. All you have to do is replace the existing Reference.cs
files with the proxy class generated by WSDL.exe.

Then, as long as the web service interface hasn't had elements deleted
(interfaces can be added to but existing interface elements should never be
modified or deleted - hopefully), you should be able to compile your existing
code with the new proxy classes just fine.

I suggest looking up WSDL.exe in MSDN Library to see how to call the
application and specify namespaces and output files, etc. to make the output
proxy classes match your application framework.
--
Dale Preston
MCAD C#
MCSE, MCDBA
"marked23" wrote:
I havn't done something like that before. Would such a script produce an
identical result? I mean, would the files be the same so that I could go
back to the IDE and compile?... and the project would never know the
difference?

"Dale" wrote:
You could alwayd create a script and manually call WSDL.exe.
--
Dale Preston
MCAD C#
MCSE, MCDBA
"marked23" wrote:
Oh, and one more thing. The only thing in this project is all these web
references... No actual code. Then we use the resulting DLL in a separate
project.

-Mark

Feb 9 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by bccbccbcc | last post: by
5 posts views Thread by Dan C Douglas | last post: by
1 post views Thread by Elias | last post: by
reply views Thread by mihailmihai484 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.