WebServices

SourceControl

[RainMaker]

I have a WebService with about 70 or so functions. I am working on this WebService amoung about 7 other people and we all use sourcecontrol. Some of us are responsible for about 7-20 functions in this webService. It makes things hard because in SourceControl you can only check out the implementation by one person. What I would like to do is keep this in one webservice but split the functions into separate files so that each of us can be working off of just our separate files. I have looked on google and can't find a whole lot. If anyone has any suggestions I will take them.

[Ocean10000]

If its in the development phase why don't you each create a new class (1 class per developer) for the functions you are responsible for, and just have the webservice create those classes and call the related functions in the classes. Basicly the webservice would just be a wraper around 7 or so class's that the developers built. There are some draw backs to this.

1. One possible problem is where one function is needed by another developer ands that is in somone elses control in another class.
2. Extra work just managing the 7 or so class's instead of one file.
3. Depending on the class, Database resources or other resources, trying to manage them between the separate classes might make things a little more complicated then if they are all in one class (webservice).

I hope this helps this was just off the top of my head at 7:30am.

[RainMaker]

Well I had considered that as a possibility, but I really wouldn't worry about those drawbacks but the creation and destruction of new/old functions. You still have to check out the main asmx file in order to do so. Which is my main concern. I guess I was wondering if there was a way to create a custom class that just knows it's from the same webservice that you can apply the [WebMethod] Attribute to it's member functions. I would think there should be a way. I haven't develed in the syntax at all with it though. I should really hammer at taht awhile. But I am still taking suggestions. Thank you very much.

[TheNige]

If the functions are private (i.e. not accessible via the webservice) then you can easliy split them up into seperate class files.

To split the actual functions that are accessed via the webservice into seperate files you would need to create individual .asmx files and put the function in them. That way you could check them out individually...but in the end product after development you may not want this so you'd have to add them back into one main asmx file.

[RainMaker]

So you are saying that There is no real way to separate the [WebMethod]'s into Separate files while still preserving only one "WebService"? or preserving the "end result unless at the end of development I manually put them all back into the same .asmx file?