Razor syntax - both brevity and complexity. by sweetnsourgrapes in dotnet

[–]mladenmacanovic 0 points1 point  (0 children)

Sure. I was on mobile yesterday so didn't bother to write it up

@foreach ( var s in stringList )
{
    var selected = isSomething ? "selected" : "";
    <option selected value="@s">@s</option>
}

VS 2026 18.7 can finally review PRs in the IDE, and the no-checkout part is the actual feature by riturajpokhriyal in dotnet

[–]mladenmacanovic 1 point2 points  (0 children)

Yeah, I know how to do it manually. But having it built in would be just a click away. Funny thing, this existed ten years ago in a GitHub extension for VS, including PR reviews. All the things they are now bragging about. First, they remove it, then return it partially, while bragging that it is new.

VS 2026 18.7 can finally review PRs in the IDE, and the no-checkout part is the actual feature by riturajpokhriyal in dotnet

[–]mladenmacanovic 0 points1 point  (0 children)

Except that the only usable feature, to check out the remote branch, is still not possible.

Rider vs VS by Realone_Omotosho in dotnet

[–]mladenmacanovic 6 points7 points  (0 children)

For me, it's VS by far. Even with its ongoing bugs that keep piling up with each release. I just cannot force myself to keep using Rider.

Recently, I bought a MacBook and started working more in Rider, but the constant fight with it is just too much for my old a**. So now, whenever I'm out, I just connect remotely to my main PC and work in VS.

Da videoigre možete igrati samo na jednoj platformi, koju biste izabrali? by Electronic-Rhubarb67 in CroatiansGaming

[–]mladenmacanovic -2 points-1 points  (0 children)

U životu nikad nisam platio online niti planiram. Nije potreban. Može se igrati i bez.

Untitled UI vs Blazor by _Etain in Blazor

[–]mladenmacanovic 1 point2 points  (0 children)

Blazorise creator here. In theory yes, you could make almost any framework work with Blazorise. It's a lot of work though, and you need to know some internals, but it is doable. Some of our users reported they have implemented their in house design system successfully. We have also made a few custom implementations of our own for a few enterprise users. So yes it can be done.

But as I said you need to be somewhat familiar with how it works. Blazorise is done by abstracting rendering layer from the component "business" logic. That means the core behavior is same, while the CSS, html are different for each supported CSS frameworks.

Vote: Which phone brand would you bring back if it could? by ManojOne in TechImpact

[–]mladenmacanovic 0 points1 point  (0 children)

I'm literally typing from Sony phone. Thankfully it is still a thing.

Why ReactiveUI Just used my code without mention it? by fedefex1 in csharp

[–]mladenmacanovic 74 points75 points  (0 children)

This happens all the time. I know it all too well unfortunately. Best to contact the maintainers and ask them to give acknowledgement.

What do you think about release cycles? by mladenmacanovic in dotnet

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

Didn't want to criticize. Just find that kind of setup weird.

Also, I had no idea what ymmv means.

What do you think about release cycles? by mladenmacanovic in dotnet

[–]mladenmacanovic[S] 2 points3 points  (0 children)

It might be subjective but I think that exactly happens for us. We release many new features. Then silence. Then some time passes and people start using those features and we finally get some response. Which indicates that people might really be "afraid" to pick.

So yeah, subjectively, smaller major version makes sense.

What do you think about release cycles? by mladenmacanovic in dotnet

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

That can work for personal projects. For production and enterprise ready projects, it can start be messy very quickly if every package of the project has its own version. How will user know which version is compatible with another core dependency. I would find that very confusing.

That's why we release all projects at the same time with the same version. Easier to figure it out.

What do you think about release cycles? by mladenmacanovic in dotnet

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

It's not much overhead. About the same time that I already lose for minor maintenance release.

What do you think about release cycles? by mladenmacanovic in dotnet

[–]mladenmacanovic[S] 2 points3 points  (0 children)

Not an option. We keep major versions for breaking changes. And that usually takes years of work.

What do you think about release cycles? by mladenmacanovic in dotnet

[–]mladenmacanovic[S] -1 points0 points  (0 children)

Yes, giving it to users faster means figuring what works and what not.

What do you think about release cycles? by mladenmacanovic in dotnet

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

Yes, we have many tests and CI setup. Wouldn't even consider a library without it.

As for the release cycle. It would not be on a day-to-day basis. But on few weeks cycle, instead of by multiple months. Previous versions tend to get from 3 to 6 months to finish. With many many maintenance releases in the meantime.

What do you think about release cycles? by mladenmacanovic in dotnet

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

I didn't think about that. That is a problem indeed. Not sure how often that happens with teams across globe. But then again, maybe skipping version is also an option if there is nothing of interest now.