Update on Plans for .NET Architecture Samples, Repos, and Organization

[jamesmontemagno]

The .NET Architecture organization was created to showcase reference apps & e-books for several .NET technologies spanning web, mobile, desktop, migration, and cloud native. Teams across Microsoft and the .NET community continued to maintain, update, and infuse new technologies into these reference apps as frameworks and technologies continued to progress. .NET continues to move forward, and we want you to have the most relevant and up-to-date architecture references that move at the same pace. To accomplish this, we're announcing a change to the dotnet-architecture organization that will roll out over several stages.

1. Transition to eShop: eShopOnContainers is our most popular reference application for cloud-native development and has been updated and transformed in the new eShop repository in the dotnet organization (and the Azure variant, eShopOnAzure). The .NET team will be maintaining and managing community contributions moving forward and will be kept up to date in the future. We'll be using this reference application as a test bed for new features, performance, and more as new features and version of .NET advance.
2. Consolidation of Reference Applications: eShop also has been updated to incorporate architecture reference apps for .NET MAUI, ASP.NET Core, and Blazor. This means that eShopOnWeb, eshop-mobile-client, and eShopOnBlazor are redundant. Each of these reference applications has been updated to .NET 8, which will be their final updates and will be archived in the future. eShop will be the new home for these reference applications.
3. Archiving Inactive Repositories: Due to inactivity and reference architectures being found in other samples, the following repositories will be archived in the near future: eShopModernizing, grpc-for-wcf-developers, and simple-feed-reader.
4. Having discussed eShopOnDapr with the team it will also be archived as it is out of date and newer samples can be found on official sources including: https://dapr.io and https://github.com/dapr. Additionally, be sure to see the Azure Container Apps Landing Zone with Dapr support.
5. E-book Updates: Existing e-books for samples upgraded to .NET 8 have been updated based on current documentation. E-books for eShopOnContainers will be updated in the future to reference the new eShop reference application.
6. We also recommend the Reliable Web App patterns guidance for building web apps with enterprise app patterns.

We look forward to seeing the continued innovation in the .NET space and as it relates to reference architecture. If you have any feedback on the plan, feel free to comment on this issue.

[CESARDELATORRE]

Sounds great! 👍

[jorsang1]

Thanks for the update and all the effort in maintaining this for and with the community.
What are the plans for eShopOnDapr, though?
Looks like there is not that much activity on that project.
Thanks!

[jamesmontemagno]

@jorsang1 I am working with the Dapr team on some details on what they would like to do as it needs some serious updates at this point as well. We may decide to move it if they want to keep it going.

[Paul-N]

Sad to hear that eShopOnWeb will not be maintaining anymore, it was a good and small reference project for studying how to create a simple Clean Arch monolith app. eShop is huge and promoting too many techs, hard to explore quickly. I think we need something simple to get started with Clean Archs on modern ASP.NET

[EugeneKrapivin]

Awesome to hear the continued investment into this reference technology solution :)

Question: Where would we find the updated books (net8) for the eShop solution?

[Naz786]

Hey, Thanks for the update. As a junior software developer who's now mid-level and working in the .NET full stack space, it's not always easy to structure ones career. Especially when you are not the one in charge of the technology being used by your organisation. The reference app is such a good way to balance that out and remain on top of .net technology, even when not directly exposed to the latest technologies at your day job. Although I haven't properly analysed the codebase, I have set up the project. It did take a while addressing all those reference and dependency errors but some googling and persistence helped me out. Thanks again for the email. God bless the .NET community. Regards, Nazaqat Mohammed 😊🇵🇸

…

On Tue, 7 May 2024, 7:19 pm James Montemagno, ***@***.***> wrote: The .NET Architecture organization was created to showcase reference apps & e-books for several .NET technologies spanning web, mobile, desktop, migration, and cloud native. Teams across Microsoft and the .NET community continued to maintain, update, and infuse new technologies into these reference apps as frameworks and technologies continued to progress. .NET continues to move forward, and we want you to have the most relevant and up-to-date architecture references that move at the same pace. To accomplish this, we're announcing a change to the *dotnet-architecture* organization that will roll out over several stages. 1. *Transition to eShop:* eShopOnContainers <https://github.com/dotnet-architecture/eShopOnContainers> is our most popular reference application for cloud-native development and has been updated and transformed in the new eShop <https://github.com/dotnet/eShop> repository in the *dotnet* organization. The .NET team will be maintaining and managing community contributions moving forward. We'll be using this reference application as a test bed for new features, performance, and more as new features and version of .NET advance. 2. *Consolidation of Reference Applications:* eShop <https://github.com/dotnet/eShop> also has been updated to incorporate architecture reference apps for .NET MAUI, ASP.NET Core, and Blazor. This means that eShopOnWeb <https://github.com/dotnet-architecture/eShopOnWeb>, eshop-mobile-client <https://github.com/dotnet-architecture/eshop-mobile-client>, and eShopOnBlazor <https://github.com/dotnet-architecture/eShopOnBlazor> are redundant. Each of these reference applications has been updated to .NET 8, which will be their final updates and will be archived in the future. eShop <https://github.com/dotnet/eShop> will be the new home for these reference applications. 3. *Archiving Inactive Repositories:* Due to inactivity and reference architectures being found in other samples, the following repositories will be archived in the near future: eShopModernizing <https://github.com/dotnet-architecture/eShopModernizing>, grpc-for-wcf-developers <https://github.com/dotnet-architecture/grpc-for-wcf-developers>, and simple-feed-reader <https://github.com/dotnet-architecture/simple-feed-reader>. 4. *E-book Updates:* Existing e-books for samples upgraded to .NET 8 have been updated based on current documentation. E-books for eShopOnContainers will be updated in the future to reference the new eShop reference application. We look forward to seeing the continued innovation in the .NET space and as it relates to reference architecture. If you have any feedback on the plan, feel free to comment on this issue. — Reply to this email directly, view it on GitHub <#38>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACICTQFRNU5PL67HW6TBXCDZBELJZAVCNFSM6AAAAABHLQBC3CVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4DGOJVGI3DCNA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[jamesmontemagno]

@Paul-N working with some community folks on taking this sample and having it maintained outside of the org by community folks. Heard and we will continue to invest in new samples and references over time as things evolve.

@EugeneKrapivin We will post on the .NET website, but also on docs: https://learn.microsoft.com/en-us/dotnet/architecture/

[jamesmontemagno]

@jorsang1 for eShopOnDapr we are also going to archive as it is out of date and the team will be working on supporting samples. These will live archived and can be taken on by the community if desired.