I guess your point is beyond the use of interfaces. Since interfaces is a contract and it will only allow public methods, shouldn't you be using just a class or, maybe abstract class?
On Thu, Nov 5, 2009 at 9:27 PM, rbr <[email protected]> wrote: > > I have a problem that I am looking for a clean way to solve. > Currently, we provide interfaces as public apis for our internal > customers to consume. However, we may build and deploy an entire > interface that may take several iterations to fully conplete. For > example, say we have an IBankingSvc that has a save, selectbyid, > select by name and a delete method. We auto-gen the interface and > implement the underlying code for the save and selectbyid methods in > our first iteration. When we deploy this code for consumption by our > internal clients, we currently use XML comments to indicate the > selectbyname and delete methods are not yet implemented. > > Not suprisingly, this is not always sufficient for the consumers of > our API. Is there a nice way to mark these methods say, with an > attribute, that would either hide these methods or clearly mark them > as not implemented? I am not familiar with a way to accomplish this > and would greatly appreciate a more graceful sulution. > > Thanks in advance for any ideas or suggestions. > > rbr -- Atenciosamente, Paulo Roberto S. Pellucci
