Hot answers tagged

3

By making MyEditor a Singleton, you have decided that there must not ever be more than one editor window. The big question is, is that decision backed by a requirement for the application. If there is no such requirement, it is just a matter of time before someone comes up with a nice idea that requires the creation of 2 editor windows and then your nice ...


2

It really depends on what it is you are trying to accomplish by having the pages being able to reference each other. I would tend to be concerned about a separation of concerns with pages eventually being spaghetti coded together, with page A reaching over into window B which reaches over to page C which reaches back to page A, etc. If the use cases are ...


2

There are a few ways to slice this. From a client's standpoint, feature flags can raise some concerns. Is the system well-tested in various combinations of feature flags? Are all of the endpoints (both UI elements and request endpoints) protected against usage when the feature flag is set to a disabled state? When you introduce a third-party to manage those ...


2

Even if you know for sure that there will never be the need fore more than one MyEditor windows - the question you should ask yourself here is: Does this simplify the code? - Or does it complicate things for no real benefit? For example, if Instance might be accessed from different places in the code, or maybe nowhere, and you don't know beforehand if or in ...


1

Seems like an overview of .net and not just C# is missing. The .net framework is too interesting (at a technical level) to narrow it to just one of it's languages. If you want to read a compelling history of it maybe try The early history of F# by Don Syme (he is the one that added generics to .net many years ago and also the designer of F#)


Only top voted, non community-wiki answers of a minimum length are eligible