Timeline for Reset state or create new objects
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 20, 2019 at 17:57 | comment | added | Rob L | @DavidArno My company uses Visual Studio 2015 and there are no plans to upgrade. I don't pick the tools - I just use the ones placed before me. | |
| May 20, 2019 at 17:55 | vote | accept | Rob L | ||
| May 16, 2019 at 12:02 | comment | added | R. Schmitz |
Not by any stretch of the imagination an answer, but "Does this technique make sense? I'm used to a factory creating one instance of an object." - in my experience, too, it always felt cleaner to have a factory produce single instances instead of a collection. In your situation, I might create a new class CallComponentSet, very simple, just to hold that bunch of ICallComponents. Then you can still have a clean-seeming CallComponentSetFactory that only creates a single instance of something.
|
|
| May 16, 2019 at 11:49 | comment | added | R. Schmitz | @DavidArno I think if you download any current IDE and start a project, it will automatically use the newest stable version. Whatever the reason was, it was probably good enough to warrant the extra effort of specifically setting a lower version (instead of just starting developing as-is). | |
| May 16, 2019 at 7:13 | comment | added | David Arno | "I'm using C# 6.0 if it matters." Why are you using such an antiquated version of the language? C# 8 is in beta and C# 7 is coming up to two years old. v7.0 - v7.3 added some huge improvements to the language. So upgrade as soon as you can. | |
| May 15, 2019 at 22:08 | answer | added | whatsisname | timeline score: 3 | |
| May 15, 2019 at 19:42 | history | asked | Rob L | CC BY-SA 4.0 |