.NET Megathread 3.5: await GetGoodPosts()

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > The Cavern of COBOL > .NET Megathread 3.5: await GetGoodPosts()

Sagacity: May 2, 2003; Hopefully my epitaph will be funnier than my custom title.

Essential posted:

What do you guys use for installing and updating distributed/commercial applications? Not huge scale commercial, but installed across 1000's of computers around the world and able to update to the latest version.

There's also WinSparkle and Squirrel.

# ¿ Jul 3, 2014 09:26

Adbot: ADBOT LOVES YOU

# ¿ May 2, 2024 19:35

Sagacity: May 2, 2003; Hopefully my epitaph will be funnier than my custom title.

Mr Shiny Pants posted:

something like Akka persistence makes the whole object - relational impedance mismatch go away. CQRS is also neat.

It gives you a different set of problems, though. It's good to have immutable events, but you will never escape the fact that sometimes you designed your events in the wrong way.

# ¿ Aug 8, 2014 15:04

Sagacity: May 2, 2003; Hopefully my epitaph will be funnier than my custom title.

ORMs are kinda nice in that they allow you to do some complex querying using higher-level query syntax, but that's honestly about it. They infiltrate the design of your domain and once you're at any kind of scale at all you'll be looking at a ORM profiling tool to figure out why the hell it's generating N+1 queries. Not to mention the fact that usually you can only map your domain in one way whereas you may want to have different mappings depending on the type of query.

# ¿ Sep 25, 2014 10:15

Sagacity: May 2, 2003; Hopefully my epitaph will be funnier than my custom title.

Please note that unit testing also doesn't necessarily mean that you need to test ALL the details. I've seen people write tests on the level of

code:

  client.Name = "Test";
  Assert.Equals("Test", client.Name);

Not completely of course, but you get the gist. It's perfectly fine to test a big chunk of your code (a unit, if you will) in one go so that it implicity tests a lot of the details. The main thing is to avoid touching all sorts of dependencies outside of this unit and that's why you typically isolate database and filesystem access if you're testing business logic, for instance.

# ¿ Dec 16, 2014 16:45

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > The Cavern of COBOL > .NET Megathread 3.5: await GetGoodPosts()