aloisdg

I improve @Jaex's idea a little bit. My problem with his solution is the error thrown by the solution explorer. It is not very clean.

So you have a file Client.cs with your class as partial:

public partial class Client {
    // your awesome code comes here
}

In another file ClientKeys.cs with your class as partial, you will add your keys:

vasanthk

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

davidfowl

$/
  artifacts/
  build/
  docs/
  lib/
  packages/
  samples/
  src/
 tests/