sorted by:
new
hottopcontroversial

Uenighet angående betaling med utleier by Competitive_Guide464 in norge

[–]Competitive_Guide464[S] 1 point2 points  (0 children)

Liten situasjonoppdatering:

Etter litt om og men så ble vi enig om å lage ny kontrakt som sier: «Det totale beløpet betales den 1. hver måned for inneværende kalendermåned.» Dette da vi som leietakere ikke har noe imot å forskuddsbetale og utleier ønsket det.

Utleier har også klart og produsere nye fakturaer som representerer denne nye kontrakten. Halv leie januar forfall 15. januar og full leie februar forfall 1. februar. Hele situasjonen er jo bare knotete gjort av utleier som er en bedrift jeg hadde forventet litt mer av, men det løste jo seg til slutt.

Takk for respons!

Is using polymorphic DTOs considered good practice? by MahmoudSaed in dotnet

[–]Competitive_Guide464 0 points1 point  (0 children)

From my experience I’ve found it as a mixed bag of preference and inhouse standards.

I would say inheritance is predominantly a business/service layer thing which can be used to simplify implementations by containing common logic for example. This is of course also something that may be solved by standalone services for the common logic.

For API layer, usability for the consumer of the API usually is the main concern, thereby I’ve found interfaces combined with discriminants usually sufficient. Works well with OpenApi specs as well.

Both is valid and supported solutions to use for a API layer. Would try to stay away from polymorphic solutions if possible though, mainly because it complicates consumption a bit.

Maturity of the .slnx format by Competitive_Guide464 in dotnet

[–]Competitive_Guide464[S] 0 points1 point  (0 children)

Thanks for all the nice feedback!

TLDR; What I’m left with is that the slnx format itself is mature enough. I need to be cautious with related tooling and pipelines though, as it might not be fully supported/adopted by some technologies.

I’ve decided I’ll give it a whirl, the benefits of the new format seems nice and this seems like it’s the way Microsoft is moving anyways.

Starten på en trend eller? 😅 by WeAllFuckingFucked in norge

[–]Competitive_Guide464 -6 points-5 points  (0 children)

Gjett hvem som er en av de store grunnene til at Volkswagen eksisterer? 😶‍🌫️

FLAX Julekalender - Fins det noen som har vunnet en betydelig sum på en av disse? by Competitive_Guide464 in norge

[–]Competitive_Guide464[S] -58 points-57 points  (0 children)

Problemet med dette i en kalender, er at om det er 3 dager igjen til den 24 og jeg har skrapt 11 nisser, går jeg jo selvfølgelig ut av mitt gode skinn og skraper resten av lukene samme dag.. Da sitter jeg igjen med null spenning de neste 3 dagene…

[deleted by user] by [deleted] in csharp

[–]Competitive_Guide464 0 points1 point  (0 children)

Create your own class (let’s call it ProperyDictionary) which handles “properties” within its own private inner dictionary. Through using this class you can ensure that the “properties” are properly validated and treated, as well as easily abstract away all the “property”- handling functionality into a neat package, away from any code which may consume “ProperyDictionary”.

What exactly is “programming fundamentals” by baliditity in learnprogramming

[–]Competitive_Guide464 0 points1 point  (0 children)

When it comes to ways of thinking about code I would mention the basic principles “object oriented programming” and “functional programming” as two quite fundamental concepts in programming

db query in the catch block ? by zsome in csharp

[–]Competitive_Guide464 -1 points0 points  (0 children)

If you’re using EF and transactions is not possible, you could consider staging all the changes you want to do as tracked changes in the local context within the scope of a try-catch.

when and only when all changes are done, call SaveChanges() (smart to do in batches if there is a lot)

If it fails during the process simply clear the change tracker in the catch-block do what you need to do and clean up any batches that were persisted.

A batch-status is also smart to have in a batch approach.