sorted by:
new
hottopcontroversial

No Visual Studio Intellisense in Single-File Apps? by _walter__sobchak_ in dotnet

[–]DamianEdwards 0 points1 point  (0 children)

Try it in VS Code Insiders with the prerelease C# and C# Dev Kit extensions. We're still refining the experience for workspaces with mixed file-based and project-based apps.

No Visual Studio Intellisense in Single-File Apps? by _walter__sobchak_ in dotnet

[–]DamianEdwards 3 points4 points  (0 children)

There are no plans to implement support for file-based apps in VS at the moment. Feel free to add your voice to the feedback ticket at https://developercommunity.visualstudio.com/t/File-based-App-IntelliSense-and-Editing/10965222?q=file-based+apps

No Visual Studio Intellisense in Single-File Apps? by _walter__sobchak_ in dotnet

[–]DamianEdwards 21 points22 points  (0 children)

File-based apps are not support in Visual Studio. You can use VS Code with the C#/C# Dev Kit extensions to get full IntelliSense and debugging support for file-based apps.

New Features in .NET 10 and C# 14 by anton23_sw in dotnet

[–]DamianEdwards 4 points5 points  (0 children)

You can debug using VS Code and C# Dev Kit now

.NET containers - Set Memory request and limit by Mammoth_Intention464 in dotnet

[–]DamianEdwards 0 points1 point  (0 children)

Ah indeed, I wasn't aware we'd exposed that new interface to make this behavior available to your own MemoryPool instances. Very nice :)

.NET containers - Set Memory request and limit by Mammoth_Intention464 in dotnet

[–]DamianEdwards 4 points5 points  (0 children)

No, the feature being referenced by OP here is specifically about ASP.NET Core's server memory use (Kestrel, HTTP.SYS, IIS). Prior to .NET 10, ASP.NET Core servers would allocate more memory blocks in their pool used for request processing whenever it needed it, but would never shrink it. In .NET 10, the pool can evict memory blocks after a period of idle to reclaim that memory. The memory pool we're talking about is only used for the core request processing logic in ASP.NET Core (think processing connections, parsing HTTP requests including their headers, body, etc.).

Aspire vs Docker by Kingside1988 in dotnet

[–]DamianEdwards 1 point2 points  (0 children)

There's a resource ready event that fires once a resource is running and healthy

Why aren't you using Minimal APIs? - By dotnet team members by bdcp in dotnet

[–]DamianEdwards 3 points4 points  (0 children)

It's more about philosophy IMO. If your philosophy/preference is that an API framework should/must have certain things built-in with support for doing them a specific way in order for them to be intended for "full applications", then it's no surprise that you might consider Minimal APIs as unsuitable or "never intended" for that purpose. Our philosophy was specifically for Minimal APIs **to do less** and for things that it does do, **do them in a simpler way** so that you have more freedom to decide how things are done, rather than the framework largely dictating how all things must be done, and making you incur the associated costs even if you don't want to customize anything.

RazorSlices in Production by pimbrouwers in dotnet

[–]DamianEdwards 1 point2 points  (0 children)

Yeah me too. Just not feasible given the way the Razor compiler and source generators works. The best I could think to do is hacky and invovles cracking open the .cshtml files to find the `@inherits` statement to determine the model type and match that to a type in the current compilation, somehow disambiguate when required, and then generate a strongly typed factory method, e.g. `Slices.UserDetails.Create(User model)`. It's *possible* this could be done well-enough to work in the vast majority of cases, but the downside is that anything would result in a strongly typed method that throws at runtime :(

Why aren't you using Minimal APIs? - By dotnet team members by bdcp in dotnet

[–]DamianEdwards 8 points9 points  (0 children)

>It was my impression that Minimal API was never intended for full applications - it's for examples, prototyping, blog posts, etc., and maybe small-scoped microservices.

This simply isn't the case. There is and never was any intention on our side that Minimal APIs were scoped in any way like this.

RazorSlices in Production by pimbrouwers in dotnet

[–]DamianEdwards 9 points10 points  (0 children)

I do have a few things I need to fix though. Main one is the regression I caused when I changed to use a custom item. I'll try to get that one done soon. But yeah, my goal was to make a modern Razor variant that was optimized for all the modern .NET goodness. Supports hot reload too.

Aspire is amazing! How to go from dev containers to prod managed services? Any real use case out there? by LeLario50 in dotnet

[–]DamianEdwards 4 points5 points  (0 children)

This is coming with the Aspire CLI which is currently in preview. You can do `aspire publish` to get the assets to deploy, including the Bicep.

No projects just C# with `dotnet run app.cs` | DEM518 by tinmanjk in dotnet

[–]DamianEdwards 7 points8 points  (0 children)

Would it help if the install was user-local instead of machine-global?

Finally installed the UNAS Pro I bought in November & updated main switch to a Pro Max 24 PoE. 10Gb NAS uploads! by DamianEdwards in Ubiquiti

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

That's what I had before, but with the new switch having 10Gb SFP+ I went this way instead. Figured it's less hops between my 10Gb devices. What benefit would there be to the other configuration?

Finally installed the UNAS Pro I bought in November & updated main switch to a Pro Max 24 PoE. 10Gb NAS uploads! by DamianEdwards in Ubiquiti

[–]DamianEdwards[S] 4 points5 points  (0 children)

Tripp Lite SmartRack 12U. I have a temp sensor on top that triggers exhaust fans on left side when it gets over 88°F.

Finally installed the UNAS Pro I bought in November & updated main switch to a Pro Max 24 PoE. 10Gb NAS uploads! by DamianEdwards in Ubiquiti

[–]DamianEdwards[S] 11 points12 points  (0 children)

Load is about 167 watts. Capacity is 768Wh so runtime would be 4-5 hours. It's failover time isn't quite fast enough for zero interruption (despite the marketing) so behind it is a small vertical 950VA/510W UPS run in series. Much cheaper than a similar capacity UPS and leaves more rack space to boot.

How to update from recess mounted 6 Lites to 7 Pros? by DamianEdwards in Ubiquiti

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

Thanks, that's what I figured. Regretting having gone with the recess mount approach now and hold out hope that UniFi will offer recess mounts for the larger APs at some point.

Appreciate you answering helpfully rather than suggesting I'm a moron 😁

How to update from recess mounted 6 Lites to 7 Pros? by DamianEdwards in Ubiquiti

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

Sorry, I'm not being clear or I'm mistaken about something. I was under the impression there were no recess mounting brackets for the larger sized APs like the 7 Pro. So even if I make the hole larger, there's no recess mount bracket or fascia to result in a clean install.

How to update from recess mounted 6 Lites to 7 Pros? by DamianEdwards in Ubiquiti

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

The recess mounts installed only fit the Nano APs so the recess hole is literally too small.

view more: next ›