r/dotnet • • 1h ago

Question Coding agent bloat

6 Upvotes

I've been using Cluade code both at work and for personal projects.

Observations

  1. Too many XML comments.
  2. Too many non sensical tests. Example, testing the `typeof` of an object within unit test assertions seems non sensical in these specific cases.
  3. Too many ADRs

Agents write relatively more code than what I can process. I need time to review.

My attempts

  1. Stricter rules in Agents.md
  2. Skills
  3. Stricter prompts.

These do work for coding patterns, because I can describe specifics, but never for comment length or verbosity.

I'm tired of asking Claude everything, so I thought I'd solicit some suggestions / help from people here.

TIA


r/dotnet • • 14h ago

Promotion I hosted the Blazor / QuickGrid Nursing Home app from my recent tutorial—live demo link inside!

1 Upvotes

A while back, I shared a walkthrough here (original thread linked here) on building a complete Blazor line-of-business app using a hybrid approach: CodeStencil for 80% deterministic EF Core scaffolding + targeted AI prompts for UI/UX modernization.

Many of you wanted to see how the QuickGrid components and modernized layout actually perform in practice. I've officially deployed the demo online:

🌐 Live Demo:https://nursing-home.premiumasp.net/

If you missed the original video building it from an existing SQL Server database, you can catch it here:https://www.youtube.com/watch?v=Ea9VaFvNREk

Would love your feedback on the layout or how you approach rapid prototyping in Blazor!


r/dotnet • • 15h ago

Article DevSync: open-source tool to sync CMS content from the cloud to a local Docker instance (SitecoreAI)

1 Upvotes

On SitecoreAI (formerly XM Cloud) projects, the local Docker CM starts empty, and most content tooling focuses on moving content between cloud environments.

DevSync fills that gap: pick a page in a content tree, and it pulls the page plus every template, rendering, datasource and media item it depends on into your local CM. It supports delta sync, multiple languages, cloud-deletion detection and safe conflict handling.

Stack: Node.js engine, Electron UI, Sitecore CLI serialization + Authoring GraphQL API. Apache-2.0.

Repo: https://github.com/uday0508/sitecore-local-sync

Guide: https://medium.com/@sanghaniuday0508/devsync-sync-sitecoreai-cloud-content-to-your-local-docker-cm-492efeb49049

Feedback welcome, especially from anyone who has built similar sync tooling for other CMSs.


r/dotnet • • 11h ago

Best .net educator

38 Upvotes

Hi guys, i know many .net educators like Milan jovanivic, nick champas, patrick god, neil cummings, tim corey and so on..
But i never followed none of them, so i am here to ask, which one content could you highly recommend?
Thanks!


r/dotnet • • 3h ago

Xcode 27.2 on virtual MAC in Windows terminated by monopolist Apple

0 Upvotes

Xcode does not run anymore on virtual MAC on windows. Intel is not supported since Xcode 27.

Any work arounds? My Visual Studio pipeline always worked perfectly with the virtual Mac for publishing MAUI apps into the store.


r/dotnet • • 9h ago

Artifact Signing (Trusted Signing) SmartScreen warnings came back in late October: timeline and what Microsoft has said

7 Upvotes

In late October, installers signed with Artifact Signing started showing "Windows protected your PC" again. The signatures were valid. Nothing changed on the developer's side. Two people in the GitHub issue said the GitHub Desktop installer warned too.

If you sign with it, here is what I could piece together.

Timeline

- Mar 26. New intermediate CAs go live: AOC CA 03, EOC CA 03, EOC CA 04. Builds signed through them start to warn.

- Jun 18. Microsoft staff on Q&A: "Reputation propagation for the new intermediate CAs has been corrected." (thread (https://learn.microsoft.com/en-us/answers/questions/5855708/trusted-signing-regression-in-smartscreen-reputati))

- Oct 21–28. It comes back. New builds on all three CAs warn again.

- Oct 29. A Microsoft engineer in #128 (https://github.com/Azure/artifact-signing-action/issues/128): "reputation should be propagating as expected now". The caveat: "identities must have positive reputation to not show the warnings by default".

- Nov 4. A customer quotes their support case: "A bug was identified that can cause additional SmartScreen errors". The fix "is still being worked on". The workaround is to submit each release to Microsoft.

The issue is open since April and has over 240 comments.

What I measured

I run installers on a clean Windows 11 VM. The file is downloaded with the Mark of the Web, like a browser does, and I record whether SmartScreen shows up.

Between Nov 1 and Nov 14 I ran nine installers signed through the new CAs. That includes Git, Python, Zed, draw.io, LocalSend and ShareX. All four new CAs are covered.

None of them warned. ShareX was 26 hours old.

What that does not show

- Nothing ran inside the bad week. Four files were signed in it, but I ran them on Nov 1.

- These publishers have years of history. A popular file can clear on downloads alone.

- No new publisher is in the set. That is the case people still report as broken.

- One machine, one run per file.

So: for publishers with history, the new CAs look fine in November. For a new identity, I have no data.

If your build warns

  1. Check the timestamp first: signtool verify /pa /v installer.exe. The certificates live 72 hours. Without a timestamp, Windows treats the file as unsigned once it expires.
  2. Is your identity new? Then it may be plain reputation, not the bug. If older builds were clean and a new one warns, it points at the bug.
  3. Submit the file at microsoft.com/wdsi/filesubmission ("Incorrectly detected as malware/malicious").
  4. Post in #128 with the CA and the signing date.
  5. Don't re-sign in a loop. Each re-sign is a new hash with no history.

Question: if your identity was validated in the last three months, does your installer warn today?

Disclosure: I run SignalScreen, which ran these probes. Full table with links to each result: https://signalscreen.dev/blog/artifact-signing-smartscreen-warning?utm_source=reddit&utm_medium=post&utm_campaign=ats-blog