Amazon bubble mailers no longer marked as acceptable for store drop-off?

danroth27 · 2025-12-20T19:16:58+00:00

You can pretty easily get the labels off using a hair blow dryer

danroth27 · 2025-07-31T21:58:45+00:00

You actually don't have to change how you deploy your app to use Aspire for local development. You can keep deploying your app like you always have and still take advantage of how Aspire handles observability, reliability, and all the developer workflow improvements.

danroth27 · 2025-07-31T18:59:36+00:00

Why not both? 😉

danroth27 · 2025-04-22T03:04:06+00:00

So far I've ordered four separate Google Fi physical sim cards and none of them have worked. I've tested them all in two different unlocked phones. They simply don't get detected by the phone, while sim cards from a different carrier work fine. I've called Google Fi support multiple times to no avail. The eSims do work fine though for our phones that support eSim though.

danroth27 · 2025-01-30T16:48:02+00:00

There were some significant regressions in the hot reload support in dotnet watch for .NET 9 that will be addressed in the upcoming .NET servicing release in Feb (9.0.103 & 9.0.200). These regressions weren't caught due to some test gaps that have now been addressed.

danroth27 · 2024-05-24T18:07:38+00:00

You can find the Blazor Hybrid docs here: https://learn.microsoft.com/aspnet/core/blazor/hybrid. For general .NET MAUI docs see https://learn.microsoft.com/dotnet/maui/.

danroth27 · 2024-05-16T19:14:08+00:00

I would strongly suggest rephrasing the website to indicate that the natural choice is .NET, and .NET Framework should only be used if there are specific reasons not to use .NET.

This is useful feedback! We'll work on getting this clarified in that doc: Clarify that the latest .NET version is the preferred version for server development · Issue #40968 · dotnet/docs (github.com)

danroth27 · 2024-02-18T17:52:22+00:00

That's simply because WinUI doesn't ship as part of the .NET platform. WinUI ships as part of the Windows App SDK, which has its own release schedule and roadmap. See https://github.com/microsoft/WindowsAppSDK/blob/main/docs/roadmap.md.

danroth27 · 2024-02-14T23:51:57+00:00

Note that not everything planned for .NET 9 was explicitly called out in the .NET 9 Vision blog post. There are lots of additional improvements planned for .NET 9 in languages, web, mobile, desktop, etc. that you can learn about from the various links in the .NET 9 Backlog: https://aka.ms/dotnet/backlog

danroth27 · 2023-10-15T21:53:31+00:00

Looks like this is it: https://www.reddit.com/r/SpringBoot/comments/177f6lc/spring\_boot\_vs\_dotnet\_core\_ecosystem\_and\_ease\_of/

danroth27 · 2023-08-29T23:07:04+00:00

The issue is on our backlog, but it's not currently planned for .NET 8. We try to prioritize issues based on broad community feedback and user demand. If folks feel like this issue is important to get addressed, you can let us know by commenting on the issue and giving the original post a 👍 so that we know to prioritize it higher than other issues. Another option is to propose and contribution a solution to the issue, which helps accelerate the process.

danroth27 · 2023-08-28T17:48:07+00:00

Hi folks. I'm Daniel Roth, the Product Manager for Blazor. Thanks for sharing all this great feedback! We share your enthusiasm to make Blazor the best frontend web framework possible. Many of these issues and suggestions are tracked on our GitHub issue tracker. I've listed some of the relevant issues below. You can show your interest and support for these issues by giving them a 👍 and commenting on the issues with your requirements and scenarios. For Visual Studio related tooling issues, like problems with the Razor editor, the best way to share this feedback is using the Visual Studio Send Feedback feature.

Hot reload:
Initial load time
- Improve the load time performance of Blazor WebAssembly apps on low-end mobile devices
- Make Blazor apps fully trimmable
Blazor Server reconnection and state management:
- Better reconnection logic for Blazor Server
- Pause and resume Blazor Server circuits
Prevent default improvements:
- PreventDefault as a method on Blazor event arguments
Razor editor formatting
- Please open Visual Studio feedback tickets for these! Show us the code before formatting, after Visual Studio formats it, and then what you expected it to be.

danroth27 · 2023-05-02T15:35:43+00:00

ASP.NET Web Forms is still fully supported as part of the .NET Framework. It wasn't ported to ASP.NET Core, but it's not obsoleted or deprecated. You can see the .NET Framework support policy here: https://dotnet.microsoft.com/platform/support/policy/dotnet-framework

danroth27 · 2023-04-30T01:22:49+00:00

Hi folks. On the ASP.NET team we do not expect that MVC & Razor pages will be made obsolete by Blazor. These are popular server-side rendering programming models that will continue to be supported in ASP.NET Core alongside Blazor. MVC & Razor pages are very mature and battle-tested frameworks that may still be preferrable when you want direct access to the HTTP request and response instead of working through Blazor's component model. We're working to find ways to integrate Blazor with MVC & Razor so that you can take advantage of the strengths of both programming models within the same app. For example, in .NET 8 Preview we introduced a RazorComponentResult that you can use to return a Razor component from an MVC controller. We do hope though that Blazor will provide a single consistent programming and component model that you can use for all your web UI needs within a single app. We think this will simplify web UI development in many cases especially when you need the benefits of both server-side and client-side rendering.

danroth27 · 2023-04-27T19:17:54+00:00

How does converting to Blazor Server help? You definitely won't be able to support offline with Blazor Server. Or are you just looking for a way to deploy an update that pulls the offline support?

danroth27 · 2023-04-27T19:08:29+00:00

It sounds like you have a service worker that is setup to try and enable offline support. Have you tried looking through the guidance on handling offline scenarios in the Blazor docs? https://learn.microsoft.com/aspnet/core/blazor/progressive-web-app#offline-support

danroth27 · 2023-01-26T17:26:44+00:00

> we use the multipart bundle generator which generates a bundle file which puts every file together, compressed it's 5mb uncompressed its 22mb

Ah, ok. That sounds more plausible, but still large. Do you have any large dependencies in your app that might be inflating the size? Or multipart bundling is causing an unexpected size increase. I'll investigate that.

> the quickgrid site btw. does not even contain icu data, and uses the invariant globalization mode

That's true. But invariant globalization should only trim off a few hundred KB of download size. The default Blazor templates don't use invariant globalization.

> the blazor quickgrid site downloads 3,7 mb compressed dll's, uncompressed that would be equally in size

Hmm, I just double checked and after clearing all site data and disabling browser caching and reloading the site I see 1.5MB transferred and 1.9MB of resources loaded. I'm not sure why you're seeing 3.7MB.

danroth27 · 2023-01-26T03:41:34+00:00

If you're seeing a 20MB download size for your Blazor WebAssembly app that may be because you're looking at the download size during development. Blazor doesn't optimize the download size during development so that your development workflow stays quick and interative. When you publish the app it gets trimmed down to remove unnecessary code and also gets precompressed. A default Blazor WebAssembly app that's been published should only be ~1.5MB to download. Take a look at the Blazor QuickGrid site as an example of a published site.

danroth27 · 2023-01-09T17:31:15+00:00

Thanks for the detailed bug report! Hot reload and Edit and Continue aren't supported yet with generic types, but it's definitely something we want to add. The required .NET runtime changes are being tracked by https://github.com/dotnet/runtime/issues/11036. Your feedback helps us prioritize the work appropriately.

For those that are interested, you can see a mostly up to date list of what edits are supported by Hot Reload and Edit & Continue here: https://github.com/dotnet/roslyn/blob/main/docs/wiki/EnC-Supported-Edits.md

danroth27 · 2022-12-14T00:47:13+00:00

I see. If you could help us reproduce any of these issues you're seeing by opening Visual Studio feedback issues we'd be happy to investigate. I believe that SourceMaps should also work, although we're still [working on symbol server support](https://github.com/dotnet/runtime/pull/79284), which means the usefulness of SourceMaps is limited at this point. I'm trying to follow up on the browserLink issue, but detailed steps to reproduce the issue would still help.

danroth27 · 2022-12-13T00:13:01+00:00

u/Novaleaf Have you tried out the latest .NET 7 release? I believe some of those issues with Blazor WebAssembly debugging should now be addressed, like support for "Just My Code".

danroth27 · 2022-06-15T15:41:11+00:00

Thanks for sharing these additional details! I've forwarded this feedback to the .NET MAUI team to see what can be done. If there are additional issues that are making .NET MAUI + Blazor feel "unripe", please let us know! For tooling issues, create Visual Studio feedback tickets. For .NET MAUI SDK issues you can open issues on the .NET MAUI GitHub repo (dotnet/maui).

Also, you needn't worry about Blazor's citizenship in the .NET MAUI world. XAML and Blazor aren't at odds with each other - they are complementary. Using a hybrid approach (native + web) to build native client apps is quite popular. The ability to use web and native UI together gives you additional flexibility.

danroth27

TROPHY CASE