Sayedur Rahaman

.NET Core MVC - The Complete Guide 2024 [E-commerce] [.NET8] Course Build real world e-commerce application using ASP .NET Core MVC, Entity Framework Core and ASP .NET Core Identity. This is a Beginner to Advanced level course on .NET 8 that will take you from basics all the way to advance mode. This course is for anyone who is new to ASP.NET Core or who is familiar with ASP.NET and wants to take the first stab at understanding what is different in ASP.NET Core. From there we would be building multiple projects to understand all concepts in .NET 8 as we will deploy our final application on Azure as well as IIS. Throughout this course, we would understand the evolution of ASP.NET Core, and then we would take a look at the modified files and folder structure. - We would then take a look at new concepts in ASP.NET Core - We would build a small Razor application with CRUD operations using Entity framework for integration with the database. - We would build our Bulky Book website where we will learn advanced topics in ASP.NET MVC Core - Finally, we will deploy our Bulky Book website on Microsoft Azure and IIS. Get this course now: https://lnkd.in/gvEV6w_2 #webdevelopment #onlinecourses

২

Mastering the Unit of Work Pattern in C# for Modern Applications Should we use UOW always? Well.. we should in my project now, but actually, it's not always the best way to go. In this post I've analyzed the pros and cons of using the UOW to get to that conclusion. Interesting approaches that say to remove the UOW especially if using EF and why should we keep it, nevertheless.. like and follow :) #SoftwareDesign #Arhcitecture #BestPractise

৩

🔥 📢 New Article alert "Mastering Coroutine Scopes in Kotlin: A Beginner’s Guide (Part 5)" 📢 🔥 https://lnkd.in/dv-dnzYt #backtocoding #kotlin #android #programming #techinterviews #KotlinInterviewPrep #kotlindevelopers #coroutines #kotlincoroutines

১

Introduction\Basics of Task Management in Bitrix | Bitrix24 | Lesson-7 https://lnkd.in/eHvStNYh #bitrix #bitrix24

১

🚀 Multiple PHP version Install and Switch to PHP Version🚀 🔗 Telegram: https://t.me/bytexionl 📧 Email: [email protected] 🔗 Watch Our Service Video: https://lnkd.in/gYGQjhH8 Are you looking to switch your PHP version to match your project requirements? Whether you're a developer, sysadmin, or just getting started with PHP, this tutorial will walk you through the process step by step. In this video, we'll show you how to easily switch between different PHP versions on your server or local environment. 🔧 What You'll Learn: Why you might need to switch PHP versions. How to check your current PHP version. Installing multiple PHP versions on your system. Switching between PHP versions using command-line tools. Updating your web server to use the new PHP version. 🖥 System Requirements: A working installation of Ubuntu/Debian/Cent OS or other Linux distributions. Basic command-line knowledge. Administrative access to your server or local environment. 📜 Commands & Resources: Commands used in the video: https://lnkd.in/gv8WZicY... Official PHP Documentation# https://lnkd.in/dWcFHvDV PHP Version Management Tools: link to tools like update-alternatives, phpbrew, or brew for macOS users Thank you for watching, and happy coding! 🎉 #PHP #PHPTutorial #SwitchPHPVersion #WebDevelopment #Programming #ServerAdministration

১

REST API Design 🔗 Understanding RESTful Architecture: The Core Principles and Methods REST (Representational State Transfer) is a fundamental architecture for designing networked applications. Here are the key principles that make REST so powerful: 1. Principles: REST is built on principles like a Layered System, Client-Server separation, Statelessness, Uniform Interface, Cachability, and Code on Demand. 2. Connectedness: REST emphasizes connectedness with concepts like Self-Descriptive Messages, Resource-Based Interactions, Manipulation through Representations, and HATEOAS (Hypermedia as the Engine of Application State). 3. Methods: REST relies on core HTTP methods like GET, POST, PUT, and DELETE for interacting with resources. 4. Features: Additional features include Pagination, Filtering/Ordering, Versioning, Security, CORS, and Rate Limiting. 5. Best Practices: REST promotes monitoring, coaching, and secure interaction through Authentication, Logging, and Input Validation.

১১

Common patterns with C# and JSON Schema - object extensibility with open versus closed types. #dotnet #csharp #Json #JsonSchema #Serialization #Performance #Openapi https://buff.ly/4dUatHF

৬

Common patterns with C# and JSON Schema - the simple data object. #dotnet #csharp #Json #JsonSchema #Serialization #Performance #Openapi https://buff.ly/3UFc2jL

৩

Common patterns with C# and JSON Schema - constraints on a simple data object. #dotnet #csharp #Json #JsonSchema #Serialization #Performance #Openapi https://buff.ly/4am2Jep

৪

Writing and Implementing Custom Form Validator in Laravel 11 Validation is crucial for website development, and Laravel 11 offers strong form validation features. This article focuses on creating and using a custom form validator for Nepal's mobile service providers, Ncell and NTC, to validate phone numbers. #laravel #form_validation https://lnkd.in/gFsPzyMd

৬

২ মন্তব্যসমূহ

A Comprehensive Guide to Keyed Dependency Injection in #dotNET8! #dotNetCore #dotNetCoreDevelopers #dotNetCoreDevelopment #dotNetCoreDevelopmentIndia #dotNetCoreDevelopmentConsultants

২

Fullstack .NET (Startup) Developer Roadmap 2024 🗺 📁 Backend ∟👨‍💻 C# / ASP.NET Core ∟👨‍💻 EntityFrameworkCore / Postgres / MSSQL ∟👨‍💻 Design Patterns ∟👨‍💻 Memory Caching ∟👨‍💻 Localization ∟👨‍💻 RESTful APIs ∟👨‍💻 gRPC ∟👨‍💻 Clean / Onion Architecture ∟👨‍💻 CQRS (Command Query Responsibility Segregation) ∟👨‍💻 Modular Monolith ∟👨‍💻 Microservices Architecture ∟👨‍💻 DDD (Domain-Driven Design) ∟👨‍💻 Event-Driven Architecture 📁 Frontend ∟‍👨‍💻 HTML + CSS + Tailwind ∟👨‍💻 Blazor ∟👨‍💻 Javascript / Typescript 📁 Version Control ∟👨‍💻 Git / GitHub 📁 Web Sockets ∟‍👨‍💻 SignalR 📁 Message Queue ∟‍👨‍💻 RabbitMQ ∟‍👨‍💻 Azure Service Bus ∟‍👨‍💻 Amazon SQS ∟👨‍💻 Kafka (Not exactly a message queue, but anyways) 📁 Cloud & DevOps ∟👨‍💻 Docker / Kubernetes ∟👨‍💻 Azure DevOps / GitHub Actions ∟👨‍💻 Azure / AWS ∟👨‍💻 Terraform / Infrastructure as Code (IaC) ∟👨‍💻 Serverless Computing (Azure Functions, AWS Lambda) ∟👨‍💻 Continuous Integration / Continuous Deployment (CI/CD) 📁 Testing (XUnit / NUnit) ∟👨‍💻 Unit Testing ∟👨‍💻 Integration Testing ∟👨‍💻 Performance Testing ∟👨‍💻 End-to-End Testing (Selenium, Cypress) ∟👨‍💻 Test-Driven Development (TDD) 📁 Security ∟👨‍💻 Authentication / Authorization (OAuth, JWT) ∟👨‍💻 Data Protection ∟👨‍💻 Secure Coding Practices ∟👨‍💻 Application Security (OWASP) ∟👨‍💻 Azure AD / B2C ∟👨‍💻 AWS Cognito 📁 Monitoring & Logging ∟👨‍💻 Serilog / NLog ∟👨‍💻 ELK Stack (Elasticsearch, Logstash, Kibana) ∟👨‍💻 Prometheus / Grafana ∟👨‍💻 OpenTelemetry ∟👨‍💻 Azure Monitor 📁 Collaboration & Communication ∟👨‍💻 Agile / Scrum Methodologies ∟👨‍💻 Jira / Azure Boards ∟👨‍💻 Trello 📁 Other Essential Skills ∟👨‍💻 Code Reviews / Pair Programming ∟👨‍💻 Software Architecture Principles ∟👨‍💻 Performance Optimization ∟👨‍💻 Cost Optimization in Cloud If you have any suggestions, please feel free to comment below. 👇 #dotnet #blazor #aspnetcore #roadmap #typescript #javascript #kafka #rabbitmq #aws #azure #cloud #lambda #sqs #agile #kanban #git #github #xunit #nunit #jira #trello #tdd #dotnet #dotnetdeveloper #dotnetcore #devexpress #reporting #report #reports #csharp #csharpdeveloper #csharpdotnet #winforms #wpf #fullstackdeveloper #dotnetfullstackdeveloper #dotnetfullstack #dotnet7 #dotnetcoredeveloper #backenddeveloper #frontenddeveloper #code #coder #coders #programming #programmer #blazor #aspnetcore #aspnet #aspdotnet #asp #maui #dotnetmaui #dotnetmvc #bootstrap #blazor #wasm #softwaredevelopment #software #softwareengineering #softwaredesign #softwareengineer #softwaredeveloper #softwarearchitecture #softwarearchitecture #softwarecompany #softwaredev #softwareengineers #dotnetmaui #dotnetmvc #sqlserver #developer #designpatterns #designpattern #designprinciples #frontend #frontenddeveloper #frontenddevelopment #frontendwebdeveloper #backend #backenddeveloper #backendwebdevelopment #microservices #microservicesarchitecture #microservice #api #apis #apidevelopment #transcription

৪০

১ মন্তব্য

StructuralComparisons The `StructuralComparisons` class in .NET is part of the `System.Collections` namespace and is used to provide comparison services for collections that do not have a specific order, such as arrays. It offers two properties - `StructuralEqualityComparer` and `StructuralComparer` - that can be used to compare arrays and other collections based on their structure rather than their reference. Advantages 1.Structural Comparison: It allows for comparing the contents of two arrays or collections, treating them as equal if their structure and content are equivalent, rather than their references. 2.Ease of Use: The class provides a straightforward way to perform deep comparisons without needing to implement custom comparison logic. 3.Flexibility: It can be used with different data types, including nested collections, making it versatile for a variety of use cases. 4.Standard Implementation: By using StructuralComparisons, developers leverage a standardized implementation which can reduce potential bugs compared to custom comparison logic. 5.Support for Multiple Types: It can handle comparing arrays containing different types of elements, which can be helpful in dynamic programming situations. Disadvantages 1.Performance Overhead: Structural comparison may introduce performance overhead, especially for large collections, since it checks each element recursively. 2.Limitation to Arrays: Designed primarily for comparing arrays and flat collections, it may not be effective for more complex types or needs that require specialized comparison logic. 3.Implicit Dependencies: If the structures being compared contain nested objects that do not implement the appropriate equality members, the comparison might yield misleading results. 4.Use in .NET Core: As it is part of .NET Framework, usage in .NET Core and .NET 5+ may be limited or require a different approach. Users transitioning from .NET Framework to .NET Core should be mindful of this. 5.Lack of Advanced Features: It may not support advanced comparison features like filtering or custom sorting, requiring additional code to extend functionality. In this example, two integer arrays (array1 and array2) that contain the same elements in the same order are compared using StructuralComparisons.StructuralEqualityComparer, resulting in `true`. Conversely, array1 and array3,which contain the same elements but in different orders, are compared and yield `false`. The `StructuralComparisons` class provides functionality for comparing collections based on their structure and contents, making it suitable for scenarios where deep comparisons are necessary. However, developers should be aware of its performance implications, limitations in complex data types, and the potential need to implement custom logic for specific use cases, especially when transitioning to .NET Core. Want to know more? Follow me or connect🥂 Please don't forget to like❤️ and comment💭 and repost♻️, thank you🌹🙏

৯৪

১৫ মন্তব্যসমূহ

# 🎥 Must-Follow YouTube Channels for .NET Developers in 2024 ## 1. Nick Chapsas **Channel Focus**: Advanced .NET, Performance Optimization, Modern C# - 🔍 Deep dives into C# features - 🚀 Performance optimization techniques - ⚡ Modern patterns and practices - 📊 Benchmarking and profiling ## 2. Tim Corey (IAmTimCorey) **Channel Focus**: Comprehensive .NET Tutorial Series - 📚 Full course-style content - 🎯 Project-based learning - 🔨 Best practices - 🏗️ Architecture patterns ## 3. Milan Jovanović **Channel Focus**: Clean Architecture, Design Patterns - 🏛️ Architecture deep dives - 🎨 Design patterns - 🧪 Testing practices - 🔄 CQRS and DDD ## 4. Les Jackson **Channel Focus**: Microservices, Docker, Kubernetes - 🔄 Microservices architecture - 🐳 Docker containerization - ⛵ Kubernetes deployment - 🌐 API development ## 5. Shawn Wildermuth **Channel Focus**: Full Stack .NET Development - 🎯 ASP.NET Core - 🔄 Angular/Vue/React with .NET - 📱 Mobile development - 🏗️ Architecture patterns ## 6. Code Opinion (Derek Comartin) **Channel Focus**: Domain-Driven Design, Event Sourcing - 🎯 DDD implementation - 🔄 Event Sourcing - 🏗️ Microservices - 🚀 System Design ## 7. Rahul Nath **Channel Focus**: Azure, .NET Performance - ☁️ Azure best practices - ⚡ Performance optimization - 🔒 Security patterns - 💻 Developer productivity ## 8. Raw Coding **Channel Focus**: Advanced .NET Concepts - 🔍 Framework internals - 🏗️ Custom implementations - 🚀 Advanced patterns - ⚡ Performance tuning ## 9. Steve "Ardalis" Smith **Channel Focus**: Software Architecture, Clean Code - 🏛️ Clean architecture - 📝 Design patterns - 🧪 Testing strategies - 🔨 Refactoring techniques ## 10. dotNET **Channel Focus**: Official Microsoft Content - 📢 Latest .NET updates - 🎯 New feature announcements - 📚 Best practices - 🎓 Learning resources ## Bonus Channels Worth Mentioning: - **DevmentorLive**: Practical project implementations - **Coding Tutorials**: Quick tips and tricks - **Patrick God**: German/English .NET content - **Codewrinkles**: Advanced C# concepts ## Pro Tips for Learning: 1. 📝 Code along with tutorials 2. 🎯 Focus on one channel per topic 3. ⚡ Implement learnings in personal projects 4. 🔄 Revisit complex topics multiple times 5. 🚀 Share your learning journey #dotnet #csharp #programming #softwareengineering

৯৬

১৪ মন্তব্যসমূহ

Warning: Developer Geek Rant Topic: Configuration in .NET Apps Audience: .NET Developers If you’re not a .NET developer please move on you will not care I assure you. TL;DR; - Stop relying on old school token replacement in build pipelines for *non-secrets* - Do use .NET ConfigurationBuilder in the Microsoft .NET standard way - Understand the beauty of the secrets.json file for local private configuration on your dev workstation and use it! RANT: As a software engineer and architect for close to three decades now, I’ve seen all variations of configuration strategies for applications. The most basic is token replacement, which I discovered and used plenty since the 1990’s Fast-forward to the advent of .NET, and Microsoft came up with a much better way to setup configuration for .NET applications using their ConfigurationBuilder. The benefits are too numerous to explain in this post but here’s why I’m venting. With just about every client I work with, the way configuration is handled is inefficient at best or a total mess at worst and it’s usually the latter. It blows my mind that .NET developers, some of whom have been in their careers for well over a decade, do not understand the .NET standard of configuration, much less why it is so much better than the garbage strategy of token replacement. They continue to use terrible strategies for configuration causing headaches and annoyances that have been solved well before most Gen Z’ers were even born. These outdated configuration strategies cause delays and constitute a hidden source of loss of productivity. If I were to add up all the times some developer had to go and resolve some configuration issue it is probably causing large enterprises hundreds of thousands of dollars a year in hidden costs due to time lost because someone needed to hunt down some config buried in a build pipeline or ask and wait for a developer to copy/paste the config into a Teams chat to share configuration that should have been automatic plug & play through a file directly in the repo, or because of some other of the many ills of dumb config strategies. For all you .NET Devs out there … for the love of all that is pure and holy … please take the time to learn one of the most basic things in .NET app development: The ConfigurationBuilder. For those that do use ConfigurationBuilder most of them do not even know that the User Secrets file is a thing (ie, secrets.json) much less understand why it’s awesome. So learn that too and use it for local config, specific to your environment, that can’t be shared. And don’t get me started on, “but I hate repeating config across files for the other environments.” If you’re repeating config across files then you don’t know what the heck you are doing. No self-respecting .NET developer should go on developing .NET applications without knowing this basic aspect of building .NET apps. And shame on the architects that allow devs to do this. Please do better! 😤 End of rant.

২

𝐖𝐡𝐚𝐭 𝐢𝐬 𝐒𝐢𝐠𝐧𝐚𝐥𝐑 𝐢𝐧 .𝐍𝐞𝐭? 👇 SignalR is a 𝗿𝗲𝗮𝗹-𝘁𝗶𝗺𝗲 𝗺𝗲𝘀𝘀𝗮𝗴𝗶𝗻𝗴 𝗳𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 for .NET that allows server-side code to push content to connected clients instantly. It simplifies adding real-time web functionality to applications, enabling features like live chat, notifications, and collaborative editing. It abstracts away the complexity of handling WebSockets and other communication protocols, making it easier for developers to implement real-time features. 𝗙𝗼𝗿 𝗲𝘅𝗮𝗺𝗽𝗹𝗲, Imagine you're chatting with a friend online. Normally, you send a message and wait for them to reply. But with SignalR, it's like having a conversation in real-time. You send a message, and your friend instantly sees it without having to refresh the page. It's great for things like live chat, notifications, or any situation where you want updates to happen instantly without waiting for the user to do something. 𝗦𝗼𝗺𝗲 𝘂𝘀𝗲𝘀 𝗼𝗳 𝗦𝗶𝗴𝗻𝗮𝗹𝗥 𝗮𝗿𝗲 : ➽ Live chat applications ➽ Real-time gaming ➽ Real-time monitoring and dashboards ➽ Notification systems ➽ Collaborative document editing ➽ Social media feeds ➽ Live sports updates ➽ Auction platforms ➽ Online polling and voting systems Want to learn more about SignalR and how you can configure it with .Net? You can check detailed article from here - https://lnkd.in/dYk4Hx8S #signalr #signalrlibrary #dotnet #softwaredevelopment #xtremethoughtssofttech

৫

When creating a List<T> from an IEnumerable<T> constructor in C# should you use the List(IEnumerable<T>) constructor or the Enumerable.ToList<T>() extension method? Should it even matter? Well it turns out that if you care about performance, it does. The ToList() extension method can detect the size of the source collection in more cases than the List() constructor. When the size is known in advance, the List<T> can be initialized with the right capacity, and the data can be copied more efficiently by avoiding resizing operations which would result in expensive temporary array allocations and copies. The benchmark results below show the performance difference. You can check the benchmark code here: https://lnkd.in/dR_2BKXN But I don't think it should matter which you use, so I created an issue on the dotnet repo to report the performance gap and propose an "easy" fix: https://lnkd.in/dBEaYe6U #performance #dotnet #csharp

৩১