Isn't suggesting an overarching design change kind of counterproductive to what the OP is trying to accomplish?
Testability needs shouldn't dictate basic design principles. Yes, you should write GOOD code that IS testable, but no, you shouldn't just mark all your classes as public. That's kind of silly. ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Thu, Oct 8, 2009 at 4:01 AM, Processor Devil <[email protected]> wrote: > Store your classes as public in DLL library. Then you can call them as much > as you wish, you just need to add reference to the library :) > > 2009/10/7 alex <[email protected]> >> >> >> I am coming from eclipse world and java. >> In java you have collection of classes and eclipse (IDE) allows you to >> call >> static main() methods of each class seperately (kind of quick test) >> >> now i am working in c sharp and visual studio i figured out that it is >> not really possible to do it -- each >> project has one entry point so it is hard to have this flexibility >> >> effectively is i have >> >> class A { public static void Main() { a = new A(); a.runcode(); }} >> class B { public static void Main() { b = new B(); b.runcode(); }} >> .... >> class Z { public static void Main() { z = new Z(); z.runcode(); }} >> >> >> I would like to run either an instance of A or instance of B or >> instance of >> something else from IDE for quick testing >> >> >> how can i retain the ability to run each class in the project >> on its own -- it is great and convenient for quick test of whether >> a class is working and to do bottom line design of the programs >> >> many thanks >> >> alex > >
