or you can put everything in one class, and use the #region keyword to separate code. above you code, use "#region Method" and at the end, use #endregion.
On Mon, Feb 23, 2009 at 12:54 AM, dexter <[email protected]> wrote: > > Use n-tier archiecture in that case. Write either one or more classes. > Only one class can solve the whole thing. > > On Feb 20, 2:41 pm, graphicsxp <[email protected]> wrote: > > Hi, > > > > In this case I would have one different service per namespace, am I > > right ? I only want to have one service to which the client can > > connect. > > > > On 20 fév, 02:52, Gunawan Hadikusumo <[email protected]> > > wrote: > > > > > Use namespace,Mate. Example you have 100 common function, 30 of them > > > are for graphics, 70 of them are for I/0 stuff so just seperate them > > > into 2 namespace : utility.graphic and utility.io > > > .simple is that. > > > > > On 2/20/09, graphicsxp <[email protected]> wrote: > > > > > > Hi, > > > > > > I have a service that exposes a number of methods in the service > > > > contract. Potentially there could be hundreds of functions. So the > > > > interface for the service contract and the service contract itself > > > > could become enormous. Is there a way or good practice to follow in > > > > this kind of situation ? how can I split the interface into different > > > > files ? > > > > > > Thanks >
