Hi Dee,
I agree with Nicholas... don't save the WSDL in VSS. Sourcesafe is for code
that you generate. You aren't generating the WSDL.
Do you save the DLLs into VSS? I don't.
When I deliver a build, I copy all of the build files into a "buildXX"
directory somewhere (e.g. c:/productname/drops/Build461 would contain the
461st build of the product). This directory can, and should, contain the
WSDL file, as generated on the BUILD machine, not as stored in VSS. If you
want to store your builds in VSS at that time, that is your perogative.
However, during development, I wouldn't store generated output in a source
code control system.
--- Nick Malik
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:%2****************@TK2MSFTNGP12.phx.gbl...
Dee,
I am curious, why are you saving the WDSL files in source safe? These
should be generated automatically for you from the web service. If
anything, you just have to fire up the web service, and then you can get
it anytime you want.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"Dee" <da************@hotmail.com> wrote in message
news:20**************************@posting.google.c om...I dont have much experience with wsdl's, but I am currently producing
asmx web services, for c# dot net projects.
All the project files are stored in souresafe, including the wsdl
files.
Each time I update a project I must build and run the particular web
service then manually open and save the wsdl.
This must be done before the wsdl can be checked into ss.
What I want to know is does anyone know of an automatic way of saving
the wsdl file on build.
Either in the dot net framework, or a simple program to carry this out
each time?
Any info is appreciated.
Thanks
Dee
