Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sample Update Tracking Issue - complete list #5495

Closed
guardrex opened this issue Feb 17, 2018 · 24 comments
Closed

Sample Update Tracking Issue - complete list #5495

guardrex opened this issue Feb 17, 2018 · 24 comments

Comments

@guardrex
Copy link
Collaborator

guardrex commented Feb 17, 2018

Last Updated: 4/18/21

Doesn't include migration topic samples.

Current
Version
Topic + Notes
🟢 5.0, 3.1 Blazor Samples
🟢 2.1 client-side/libman/index.md
🔴 1.1 client-side/spa-services.md
🔴 2.0 common/samples/WebApplication1
🔴 2.0 common/samples/WebApplication1DotNetCore2.0App
🔴 5.0, 2.2 data\ef-mvc\intro.md
🔴 5.0, 3.0, 2.1, 2.0 data\ef-rp\intro.md
🟢 3.1 entity-framework-6.md
🔴 3.0, 2.2 fundamentals/metapackage-app.md
🔴 3.1, 2.2 fundamentals\app-state.md
🔴 3.1, 2.2 fundamentals\change-tokens.md
🔴 3.1, 2.2 fundamentals\configuration\index.md
🔴 3.1, 2.2 fundamentals\configuration\options.md
🔴 3.1, 2.2 fundamentals\dependency-injection.md
🔴 3.1, 2.2 fundamentals\environments.md
🔴 5.0, 2.2 fundamentals\error-handling.md
🔴 3.1, 2.2 fundamentals\file-providers.md
🔴 2.2 fundamentals\host\generic-host.md
🔴 3.1, 2.2 fundamentals\host\hosted-services.md
🔴 3.0, 2.2, 2.1, net2.0 fundamentals\host\platform-specific-configuration.md
🔴 3.1, 2.2 fundamentals\http-requests.md
🟢 3.1, 2.1 fundamentals\localization.md
🔴 3.1, 3.0, 2.2 fundamentals\logging\index.md
🔴 3.1, 2.2 fundamentals\logging\loggermessage.md
🔴 2.0 fundamentals/metapackage/samples/Metapackage.All.Example.csproj
🔴 3.1, 2.2 fundamentals\middleware\extensibility.md
🟢 3.1 fundamentals\middleware\extensibility-third-party-container.md
🟢 3.1 fundamentals\middleware\request-response.md
🔴 1.0 fundamentals\owin.md
🔴 3.1, 2.2 fundamentals\routing.md
🔴 3.1, 2.2 fundamentals\servers\httpsys.md
🔴 5.0, 3.1, 2.2 fundamentals\servers\kestrel.md
🔴 3.0 fundamentals\startup.md
🟢 3.1 fundamentals\static-files.md
🔴 3.0 fundamentals/target-aspnetcore.md
🔴 3.1, 2.2 fundamentals\url-rewriting.md
🔴 2.2, 1.1 websockets.md
🔴 3.0 grpc/authn-and-authz.md
🔴 2.1, 2.0 host-and-deploy/docker/visual-studio-tools-for-docker.md
🔴 5.0, 3.1, 2.2 host-and-deploy/health-checks.md
🔴 3.1, 3.0, 2.2 host-and-deploy\windows-service.md
🟢 5.0, 3.1 includes/scaffoldTFM.md
🔴 3.0, 2.2 mvc\advanced\app-parts.md
🔴 3.1, 3.0, 2.1 mvc\advanced\custom-model-binding.md
🔴 3.0, 2.2 mvc/compatibility-version.md
🟢 3.1 mvc/controllers/application-model.md
🔴 3.1, 2.2 mvc/controllers/areas.md
🔴 3.1, 2.2 mvc\controllers\dependency-injection.md
🔴 3.1, 2.2 mvc/controllers/filters.md
🟢 3.1, 2.1 mvc/controllers/routing/samples/2.x
🔴 3.0, 2.2 mvc\controllers\testing.md
🔴 3.1, 2.2 mvc\models\file-uploads.md
🔴 3.0, 2.2 mvc/models/model-binding.md
🔴 3.0, 2.2 mvc/models/validation.md
🔴 1.0 mvc\views\dependency-injection.md
🔴 2.2 mvc\views\partial.md
🔴 3.1, 2.0 mvc/views/razor.md
🔴 1.1 mvc\views\tag-helpers\authoring.md
🟢 2.1 mvc\views\tag-helpers\built-in\samples
🟢 2.1 mvc/views/tag-helpers/th-components.md
🔴 2.2 mvc\views\view-components.md
🔴 1.0 mvc\views\working-with-forms.md
🔴 3.1, 2.2 performance\caching\distributed.md
🔴 3.0, 2.2, 2.1 performance\caching\memory.md
🔴 3.1, 2.2 performance\caching\middleware.md
🔴 3.0, 2.2 performance\caching\response.md
🔴 2.2 performance/objectPool.md
🔴 3.0 performance/performance-best-practices.md
🔴 3.0, 2.2 performance\response-compression.md
🟢 3.1, 2.1 razor-pages\filter.md RC package present
🔴 3.0, 2.0 razor-pages\index.md
🔴 3.1, 2.2 razor-pages\razor-pages-conventions.md
🟢 2.1 razor-pages\sdk.md
🔴 2.2, 2.0 razor-pages\ui-class.md
🔴 2.0, 1.0 security\anti-request-forgery.md
🟢 3.1, 2.1 security/app-secrets.md
🔴 5.0 security/anti-request-forgery.md
🔴 1.1 security\authentication\2fa.md
🔴 3.0, 2.2, 2.1 security\authentication\accconfirm.md
🔴 3.0, 2.2 security\authentication\add-user-data.md
🔴 3.1, 2.2 security\authentication\cookie.md
🟢 2.1 security\authentication\identity-configuration.md
🔴 1.1 security\authentication\identity-custom-storage-providers.md
🔴 5.0, 3.1, 2.2 security\authentication\identity.md
🔴 3.0, 2.1 security\authentication\scaffold-identity.md
🔴 3.1, 2.2 security\authentication\social\additional-claims.md
🟢 3.1 security/authorization/simple
🔴 3.0, 2.2 security\authorization\policies.md
🔴 3.1, 2.2 security\authorization\razor-pages-authorization.md
🔴 3.0, 2.0, 1.1 security\authorization\resourcedbased.md
🔴 3.0, 2.2 security\authorization\secure-data.md
🔴 3.1, 2.2 security\cors.md
🟢 2.1 security/gdpr.md
🟢 3.1, 2.1 security/ip-safelist.md
🟢 3.1 security\key-vault-configuration.md
🟢 3.1 security/same-site.md
🟢 2.1 signalr/authn-and-authz.md
🔴 3.1, 2.2 signalr/background-service.md
🟢 2.1 signalr/dotnet-client.md
🟢 2.1 signalr/groups.md
🟢 2.1 signalr/hubcontext.md
🟢 2.1 signalr/hubs.md
🟢 3.1, 2.1 signalr/javascript-client.md
🔴 3.0, 2.2, 2.1 signalr/streaming.md
🔴 3.1, 2.2 test\integration-tests.md
🟢 3.1 test\razor-pages-tests.md
🔴 2.0 tutorials/dotnet-watch.md
🔴 3.0, 2.2 tutorials/first-mongo-app.md
🔴 2.0 tutorials/first-mvc-app-xplat.md
🔴 5.0, 3.1, 2.2, 2.0 tutorials/first-mvc-app.md
🔴 5.0, 3.1, 3.0, 2.2 tutorials\first-web-api.md
🟢 3.1 tutorials/grpc.md (GrpcGreeter, GrpcGreeterClient)
🔴 5.0, 3.1, 2.2, 2.1, 2.0 tutorials/razor-pages/razor-pages-start.md
🔴 3.0, 2.1 tutorials/signalr-typescript-webpack.md
🟢 5.0, 3.1 tutorials/signalr-blazor.md
🔴 3.0, 2.1, 2.0 tutorials/web-api-help-pages-using-swagger.md RC packages present
🟢 3.1, 2.1 web-api/action-return-types.md
🔴 2.2 web-api/advanced/conventions.md
🔴 3.1, 2.2 web-api/advanced/custom-formatters.md
🔴 5.0, 3.0, 2.2 web-api/advanced/formatting.md
🔴 3.0, 2.2, 2.1 web-api/handle-errors/samples/2.x
🟢 3.1 web-api/http-repl.md
🔴 3.0, 2.2, 2.1 web-api/index.md
🔴 3.1, 2.2 web-api/jsonpatch.md
🟢 5.0 web-api/route-to-code.md
@user135711
Copy link
Contributor

user135711 commented May 11, 2018

On the in memory Caching sample, please add an explanation of how cache dependencies work. I've been trying to figure it out from the source code and debugger, and the Docs don't provide sufficient explanation:

    using (var entry = _cache.CreateEntry(CacheKeys.Parent))
    {
        // expire this entry if the dependant entry expires.
        entry.Value = DateTime.Now;
        entry.RegisterPostEvictionCallback(DependentEvictionCallback, this);

        _cache.Set(CacheKeys.Child,
            DateTime.Now,
            new CancellationChangeToken(cts.Token));
    }

How does the child token above communicate to the parent token to evict and what is the purpose of disposing of the parent token? Is this a hack where the parent eviction only occurs because the already marked as expired parent gets evicted when the child cancellation triggers a remove expired entries search? Second suggestion add to sample app a compilable version of this dependent cache entries construction because it makes more sense: aspnet/Caching#48

@vsaranea
Copy link

I am struggling to figure out how to improve the performance of my shiny new Razor Pages/Page Model based app. I have some hefty partial page renders (sidebar icons based on heavy DB calls), which I want to cache (per-model).

I've tried using the tag helper, but I can't get the example working as expected.

Is there any ETA for the 2.1 release (with the attached docs drop), or better yet - a way to preview the docs as they are being written by Luke?

@guardrex
Copy link
Collaborator Author

Is there any ETA for the 2.1 release

The only ETA I'm aware of was given by Scott Hunter at the //Build conference when he said that they were aiming for sometime around the end of this month.

with the attached docs drop

The 2.1 docs are under continuous release now. They're rolling out almost daily. However, samples (this issue) will not be updated until 2.1 releases. We won't have 1.x, 2.0, and 2.1 samples ... only 1.x and 2.x (2.x will be 2.0 prior to 2.1 release; 2.x will become 2.1 after the 2.1 release). We don't want to break users using the latest stable release (2.0) until 2.1 actually hits the street.

@Rick-Anderson Rick-Anderson removed the 2.1 label Jul 12, 2019
@guardrex guardrex removed 2.2 labels Sep 15, 2019
@guardrex guardrex removed their assignment Sep 28, 2019
@Rick-Anderson Rick-Anderson changed the title Sample Update Tracking Issue - master Sample Update Tracking Issue - complete list May 5, 2020
@bradygaster
Copy link
Member

@guardrex is this issue still current? If not, can you close? Also - apologies if i send a few pings your way from some open issues, i'm trying to do a survey of some of the long-standing open issues to address some of them this week. Reach out if i'm hitting you up too much from GitHub. :)

@guardrex
Copy link
Collaborator Author

guardrex commented Sep 20, 2021

@bradygaster ... That depends. What normally happens on this issue is that at several points in the past, perhaps once a year, I actually canvas every sample app on the repo 😅 and update this issue (the last update of this was April 18 of this year). Then, we usually hit several of the ...... er ..... more disturbing cases lol ... like 2.x samples 🙈😄 lingering for popular topics.

It's best to ask @Rick-Anderson if he wants to proceed with this process. I don't mind performing another update of this issue in early 2022 if he/you would like to keep using this. This issue is the only overview of where everything stands with sample apps. I fear without it that we'd have no clear knowledge of what's going on. However, it may have outlived its usefulness. I yield to @Rick-Anderson and you to close if that seems best. Otherwise, I'll seek to update this in 22Q1 and ping everyone for a look at the result of my canvas.

@bradygaster
Copy link
Member

I'd love to do a survey like that with you. Have you seen the fantastic improvements to the Orleans samples' visibility Reuben made? I think something like that for SignalR and for the broader ASP.NET would be fantastic.

@Rick-Anderson
Copy link
Contributor

@guardrex should we close?

@guardrex
Copy link
Collaborator Author

I think so. I don't have time to tend to this further, and it isn't relevant for Blazor, as I've adopted a ❌ NO SAMPLES!™ ❌ (where possible) approach 😄. This tracking issue was helpful in the old days 👴 to update a bunch of samples release-to-release for topics that I worked on regularly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

12 participants