r/learncsharp

▲ 8 r/learncsharp+1 crossposts

Solution projects many or 1?

Hi everyone,

I’m learning ASP.NET MVC and I want to create a new practice project where I can experiment with DevExpress controls.

I already have an existing solution where I have created a Web API project. Now I’m thinking of adding a new ASP.NET MVC project with DevExpress in order to practice the UI part.

My question is:

Would it be better to add this new MVC + DevExpress project inside the same solution, or should I create a completely separate solution for it?

My concern is mainly about debugging and running multiple projects at the same time. For example, if both projects are in the same solution, can I run/debug them separately or together without issues, using different ports?

I’m still learning, so I’d like to hear what is considered good practice in real-world development.

Thanks in advance!.

reddit.com
u/Ok_Hunter6411 — 4 days ago
▲ 130 r/learncsharp+2 crossposts

I made a free 100-minute C# course (100 concepts, beginner to advanced), and it's chapter-marked so you can jump around

Hey folks, finally finished something I've wanted to make for ages: one free video that runs through 100 core C# concepts in 100 minutes, from "what is C#" all the way to async/await, LINQ and design patterns.

I tried to make it the opposite of those 12-hour courses you start and never finish: 101 short lessons, each chapter-marked so you can skip straight to whatever you need.

It covers the basics, OOP, collections, LINQ, file stuff (CSV/JSON/XML), generics, delegates, async/await, pattern matching, plus the practical things like unit testing, Git, NuGet and design patterns.

Totally free on YouTube

▶️ https://www.youtube.com/watch?v=yVeFlmihyGQ&themeRefresh=1

Edit: Replaced the shortened URL with the original link

u/ervistrupja — 8 days ago
▲ 2 r/learncsharp+2 crossposts

Creating a Log Application

Hi everyone,

I’m a junior .NET developer and I’m currently designing a small internal application called LogHub.

The goal of LogHub is to collect and monitor logs from different internal applications/services. For now, I’m starting with the database design and then I plan to build the application in Visual Studio using .NET Core. The first version may also use DevExpress, but later I might move it to a more minimal/simple UI.

So far, I have designed these main tables:

- Users

- Applications

- Logs

- Alerts

- AlertNotifications

- Aggregations

The basic idea is:

- Applications store the systems/services that send logs.

- Logs store the raw log entries.

- Alerts are created when a log or group of logs needs attention.

- Logs have an optional AlertId FK, so a log can be connected to an alert.

- AlertNotifications store where/how an alert was sent.

- Aggregations will store summary/statistics data for dashboard usage.

This is meant to be an internal monitoring/logging tool, not a public product.

My questions are:

  1. Does this database design make sense for a first version?

  2. Would you change anything in the table structure?

  3. Is .NET Core a good choice for this type of internal tool?

  4. Would you recommend starting with DevExpress UI, or keeping the first version minimal?

  5. Any advice on how to structure the Visual Studio solution for this kind of project?

I’m mainly trying to learn good architecture and database design while building something useful.

Thanks in advance!

reddit.com
u/Ok_Hunter6411 — 13 days ago

Is using ai to write my code cheating?

I’m trying to make a short little turn based text game to learn c# but I find myself using ai for literally every little thing, is this bad?

reddit.com
u/Impressive_Diamond26 — 14 days ago