The 2nd Monitor

Duga

00:00

RELOAD! There are 4190 unanswered questions (90.8637% answered)

Hosch250

@EBrown You around?

I'm available to re-explain how we do our DTO's.

Captain Obvious

0

Q: Coin flip in C not working

So I'm programming a coin flip in C, however it seems the random part of it isn't working because it just keeps showing the same answer again and again. Here's the code: #include <stdio.h> #include <stdlib.h> int main() { int a,b = rand() % 100; again: printf("Start program?\n1:Yes\...

c random

EBrown

@Hosch250 Sorta, at dinner but feel free to fire away. I'll read it as I get the chance.

Hosch250

00:38

Left for a little, and then got locked out.

We are using Mediatr, so that affects our structure some.

We have a P... project that is our DB model. We are using EF with explicit migrations.

That project has a bunch of stuff that shouldn't be in it, but we are getting it cleaned up.

That project is in a folder with two other projects. E.BusinessLogic.Messages (E.BL.Messages [E isn't the full name]) and E.BL.MessageHandlers

E.BL.Messages has the DTOs and the Mediator messages. E.BL.MessageHandlers has the message handlers.

So, the message handlers ctor-inject the relevant DB tables with a custom IGenericRepository<T> and transforms them into the appropriate DTO.

We have mapper classes that are helpful here too.

Then, we have our UI project G...

And equivalent G.BL.Messages and G.BL.MessageHandlers projects.

G.BL.Messages has the ViewModels and more messages, and G.BL.MessageHandlers has the message handlers.

These message handlers usually use Mediator to get the DTO object from the table, then map the DTO to the VM, which is customized to the view; most of the time, it is just identical to the DTO.

And the DTO is mostly just the same as the table, but has everything loaded into memory.

So, if I want a FooVM, I do _mediator.Send(new FooMessage()).Result.

That calls FooMessageHandlers `Handle method in G.BL.MessageHandlers, which is roughly:

public TResult Handle(TMessage)
{
     var dto = _mediator.Send(new FooDTOMessage());
     // map dto to vm and return
}

Then FooDTOMessageHandler, we would do the same, except from the DBO to the DTO.

EBrown

That seems like a lot of overhead for something that simple.

Hosch250

Yeah, tell me about it.

Then, when you want to save, you have to go all the way back up.

But then, we aren't really that simple. We have N widgets that you can stick on a page all together.

Basically, we are a build-your-own-internal-promotional-webpage company.

I think one of our clients has one public webpage using our stuff, or something.

We probably have 100+ tables and 20+ widgets.

Most of our widgets have customizable settings, too.

EBrown

00:57

Yeah I built a thing like that except more abstract for a project for a previous group with less overhead, but it was with duck-typing.

Hosch250

Almost done rewriting the settings for a widget.

It was scary. There were 0 unit tests to start.

Now, I have just about all the logic under test.

This started as a fall-back project.

Next up: redoing the user-side of the widget.

Then, this provides data for a third side that gives our client's employees points that are worth money they buy from us.

Then, they can redeem them for things.

There aren't any tests for the main widget or that. The whole thing is unmaintainable.

And it is our biggest widget, and we are getting more feature requests left and right because it is mainly used by our biggest client.

Most of the people there are impressed with how well-rounded my skills are.

They basically hired me to do back-end work. I got assigned to this widget, and I'm getting tons of front-end work, plus UI design, plus testing above and beyond my own work.

I learned the core EF stuff pretty well. That is, migrations and creating tables and stuff.

Learning SQL. I know the core commands, but queries I can't do in Linq are harder.

Like, I had to write a query to find a user that might be the 16k'th user and rank them based on all the other users.

Their main SQL guy had to help me get the core stuff down, and we ended up creating a bunch of temp tables and using a cursor.

Linq was too slow because we had to return all the users to the server and do the iteration there because TakeWhile doesn't work in Linq-to-Entities, nor do assignments.

EBrown

01:13

I usually use LINQ-to-SQL until performance becomes an issue.

Hosch250

It was a serious issue. Pages were timing out.

EBrown

I believe it.

Duga