ASP.NET Core in .NET 8 is here

No Comments »

In .NET 8, ASP.NET Core provides a comprehensive solution for contemporary web development. It takes care of all your front-end and back-end web development requirements. Blazor offers dependable, high-performance backend APIs and services that let you create stunning, richly interactive web experiences. Cloud-native application development is made easy with ASP.NET Core in .NET 8, and productivity is enhanced by excellent tools in Visual Studio and Visual Studio Code. Every developer is a full stack developer with ASP.NET Core in .NET 8!

Let’s examine some of the fantastic enhancements and new features that ASP.NET Core in .NET 8 has to offer.

Advantages of Using Native AOT With ASP.NET Core

Publishing and deploying a native AOT program can bring the following advantages:

  • Reduced disk footprint: When publishing with native AOT, a single executable is created that includes the program as well as a subset of code from external dependencies that the program utilizes. Reduced executable size may lead to:
    • Smaller container images, such as those used in containerized deployments.
    • Smaller pictures lead to a faster deployment time.
  • Reduced startup time: The absence of JIT compilation allows native AOT programs to start up faster.
    • Reduced start-up time means the program can handle requests more quickly.
    • Improved deployment by using container orchestrators to control app version transitions.
  • Reduced memory demand: Because ASP.NET Core apps are published as native AOT, they can have lower memory demands depending on the work being done, as the new DATAS GC mode is automatically enabled. Reduced memory consumption can result in higher deployment density and better scalability.

AOT compatibility for both ASP.NET Core and native

Not every functionality in ASP.NET Core is compatible with native AOT. Similarly, not all libraries used in ASP.NET Core are compatible with native AOT. .NET 8 marks the beginning of efforts to enable native AOT in ASP.NET Core, with an emphasis on enabling support for apps that use Minimal APIs or gRPC and are deployed in cloud settings.

Native AOT apps have a few core compatibility requirements. The main ones include:

  • No dynamic loading (such as Assembly.LoadFile).
  • No runtime code generation by JIT (for example, System.Reflection.Emit)
  • No C++/CLI
  • No built-in COM (only applicable to Windows).
  • Requires trimming, which has restrictions.
  • Implies compilation into a single file with known incompatibilities.
  • Apps include required runtime libraries (like self-contained apps, increasing their size as compared to framework-dependent apps).

AOT with minimal APIs and native capabilities

Developers introduced the Request Delegate Generator (RDG) to ensure that Minimal APIs are compatible with native AOT. The RDG is a source generator that does similar work to the RequestDelegateFactory (RDF), converting the various MapGet(), MapPost(), and so on calls in your application into RequestDelegates associated with the specified routes, but it does so at compile time and generates C# code directly into your project. This removes the runtime creation of this code and ensures that the types used in your APIs are retained in your application code in a fashion that the native AOT tool-chain can statically analyze, guaranteeing that required code is not clipped. They’ve worked to guarantee that the RDG supports the majority of the Minimal API features you use today, making them compatible with native AOT.

.NET WebAssembly enhancements

Running .NET code on WebAssembly from the browser has been considerably enhanced in .NET 8. Your .NET code will run significantly quicker thanks to the new Jiterpreter-based runtime, which supports partial just-in-time (JIT) compilation for WebAssembly. With the new runtime, components render 20% quicker, and JSON deserialization is twice as quick!

The .NET WebAssembly runtime also supports numerous new edit types with Hot Reload, including full compatibility with CoreCLR’s Hot Reload capabilities and generic type editing. WebCIL, a new web-friendly packaging format for Blazor WebAssembly programs, simplifies deployment by eliminating all Windows-specific parts from.NET assemblies and repackaging them as WebAssembly files. WebCIL allows you to deploy your Blazor WebAssembly programs with certainty.

JavaScript SDK and project framework

Working with ASP.NET Core frequently necessitates the use of JavaScript and the JavaScript ecosystem. Bridging the .NET and JavaScript worlds can be difficult. The new JavaScript SDK and project system in Visual Studio make it simple to integrate .NET with frontend JavaScript frameworks. The JavaScript SDK integrates MSBuild, allowing you to build, run, debug, test, and publish JavaScript or TypeScript code alongside your .NET applications. You may easily interact with common JavaScript build tools such as WebPack, Rollup, Parcel, esbuild, and others.

You can quickly get started using ASP.NET Core with Angular, React, and Vue using the provide Visual Studio templates.

These templates are available for both JavaScript and TypeScript, and the client app is generated using the most recent frontend JavaScript CLI tooling, ensuring that you always have the most recent version.

Debugging improvements

.NET’s sophisticated debugger is essential for developing any .NET app, including ASP.NET. In .NET 8, developers have improved the debugging visualization experience for commonly used types in ASP.NET Core apps, ensuring that the debugger displays the most critical information right immediately.

Check out all of the new ASP.NET debugging features in this Debugging Enhancements in .NET 8 blog post.

Wrapping Up

In conclusion, the advancements and new features introduced in ASP.NET Core in .NET 8 represent a significant leap forward in the realm of web development. The integration of Blazor provides a comprehensive solution for both front-end and back-end development, empowering developers to create stunning and highly interactive web experiences. .NET 8 is currently available. Upgrade your ASP.NET Core projects now!

Elevating Debugging Experience in .NET 8: A Deep Dive into Enhancements

No Comments »

In the ever-evolving landscape of web development, the debugging experience holds a paramount position for developers utilizing the .NET framework. With the advent of .NET 8, our commitment to refining and enhancing the debugging capabilities of frequently used types in .NET applications has taken center stage. This article provides a detailed exploration of the improvements made across crucial components, ushering in a new era of debugging proficiency.

A Closer Look at Debugging Enhancements

Improved Handling of HttpContext and Friends

For developers immersed in ASP.NET Core web app development, HttpContext, HttpRequest, and HttpResponse play pivotal roles. Viewing request and response values, such as headers, cookies, query strings, and form data, is considerably simpler. HttpRequest and HttpResponse now provide a user-friendly overview of the type. Essential information, such as the HTTP request URL or HTTP response status code, is immediately visible. This ensures a more intuitive debugging experience, allowing developers to effortlessly inspect headers, cookies, query strings, and form data. Notably, HttpRequest and HttpResponse now present concise and user-friendly summaries, displaying vital information such as the HTTP request URL and response status code.

.NET 7:

.NET 8:

WebApplication: Elevating Configuration Visibility

WebApplication, serving as the default configuration method for ASP.NET Core apps in Program.cs, has undergone significant updates in .NET 8. This includes the display of crucial information such as configured endpoints, middleware, and IConfiguration values directly within your IDE’s debugger. Similar refinements have been extended to the .NET Generic Host, enriching the debugging experience for apps without HTTP endpoints.

.NET 7:

.NET 8:

MVC and Razor Pages: Streamlined Debugging for Frameworks

The widely embraced ASP.NET Core MVC and Razor Pages frameworks have not been left untouched. In .NET 8, controllers, views, and Razor Pages have received targeted debugging enhancements. The focus has been on decluttering types and optimizing them for improved usability, resulting in a cleaner and more efficient debugging experience.

.NET 7:

.NET 8:

gRPC: Simplifying Client-Side Debugging

For developers leveraging gRPC, a high-performance RPC service library, .NET 8 brings simplifications to debugging client-side calls. The latest version of gRPC now includes comprehensive information about method, status, response headers, and trailers. Developers can benefit from a more insightful debugging experience, particularly when dealing with unary calls.

grpc-dotnet 2.55.0:

grpc-dotnet 2.56.0:

Endpoint Metadata: Enhancing Understanding of Endpoints

Endpoints are at the core of ASP.NET Core, representing executable request-handling code. Debugging Endpoint.Metadata has been enhanced in .NET 8, with the addition of debug text to common metadata. This improvement makes it easier to comprehend configured metadata and understand how requests are matched to endpoints.

.NET 7:

.NET 8:

Logging: Transforming ILogger for Debugging

Logging, powered by Microsoft.Extensions.Logging, is a cornerstone for .NET apps. In .NET 8, ILogger instances have undergone a transformation to be more debug-friendly. Displaying a user-friendly list of information, including name, log level, enablement status, and configured logging providers, ILogger now provides a more accessible debugging experience.

.NET 7:

.NET 8:

Configuration: Simplifying Configuration Understanding

Understanding an app’s configuration values has historically been challenging. In .NET 8, debugging Microsoft.Extensions.Configuration now presents a straightforward list of all configuration keys and values. With precedence already calculated, developers can easily grasp the configuration values that the app will use.

.NET 7:

.NET 8:

And More Across-the-Board Improvements

While the aforementioned improvements highlight key areas, .NET 8 brings a plethora of debugging enhancements across various components. From Dependency Injection to ClaimsPrincipal and ClaimsIdentity, StringValues and StringSegment, HostString, PathString, QueryString, FragmentString, HTTP header collections, to ASP.NET Core MVC’s ModelState, these improvements collectively contribute to a more refined debugging experience.

A Deeper Dive into Key Components

Dependency Injection

Dependency Injection (DI) plays a crucial role in modern software development, promoting code maintainability and scalability. In .NET 8, debugging enhancements have been introduced to streamline the visualization of DI, ensuring a clearer understanding of dependencies and their resolutions during debugging sessions.

ClaimsPrincipal and ClaimsIdentity

Authentication and authorization are fundamental aspects of web applications, and ClaimsPrincipal and ClaimsIdentity are central to managing user identities and access control. In .NET 8, debugging improvements in these components provide a more transparent view of claims, facilitating a smoother debugging experience for identity-related issues.

StringValues and StringSegment

Handling strings efficiently is paramount in any application. In .NET 8, improvements to StringValues and StringSegment aim to simplify string-related debugging challenges. Developers can now expect a more intuitive representation of string values during debugging, aiding in quicker issue identification and resolution.

HostString, PathString, QueryString, and FragmentString

In web development, understanding and manipulating URL components is crucial. .NET 8 introduces debugging enhancements to HostString, PathString, QueryString, and FragmentString, offering a clearer representation of URL-related data during debugging sessions. This facilitates a more straightforward identification of issues related to URL handling in applications.

HTTP Header Collections

HTTP headers play a vital role in web communication, and debugging issues related to header handling is common. In .NET 8, debugging improvements to HTTP header collections provide developers with enhanced visibility into requests, allowing for a more precise diagnosis of problems associated with headers during debugging sessions.

RouteValueDictionary

Routing is a critical component in web applications, and RouteValueDictionary is instrumental in handling route-related data. .NET 8 introduces debugging enhancements to RouteValueDictionary, offering augmented visibility into routing data during debugging. This facilitates a more insightful debugging experience when dealing with route-related issues.

ASP.NET Core MVC’s ModelState

In the world of ASP.NET Core MVC, ModelState is essential for handling and validating data models. Debugging ModelState has been streamlined in .NET 8, providing developers with a more organized and comprehensive view of model state information during debugging sessions. This ensures a more efficient debugging process when addressing model state-related issues.

Try It Now

Excited to experience these debugging enhancements in action? They are available in .NET 8 RC1, ready for exploration and feedback. To embark on this journey:

1. Download the latest .NET 8 release.

2. Launch Visual Studio 2022 or your preferred IDE.

3. Create an ASP.NET Core or Worker Service app.

4. Set breakpoints and run the app with debugging (F5).

What’s New in .NET 8, .NET MAUI and ASP.NET Core Final Release Candidates

No Comments »

Since Microsoft released the second and final release candidates for the framework and its related NET MAUI, ASP.NET Core, and EF8 versions,.NET 8 and all of its components are now one month away from become generally available.

They will be released between November 14 and 16 in conjunction with the business’s .NET Conf 2023 conference.

The dev team concentrated mostly on bringing things into final form for GA by polishing functionality and correcting bugs rather than introducing significant new features, thus the code is essentially set at this point.

The RC2s for Microsoft’s developer tools solutions are defined in the following manner.

.NET MAUI

Microsoft refers to this framework as the “Xamarin.Forms” progression since it allows developers to construct desktop apps in addition to typical iOS and Android mobile targets. It has had development issues, and Microsoft-centric developers are keeping a careful eye on it in light of the recent announcement that Microsoft was cancelling Visual Studio for Mac, which has its own major development issues.

Microsoft said “Today, we take one step closer to .NET 8 general availability (GA) by shipping .NET MAUI in .NET 8 release candidate 2 (RC2),”. “As with RC1, this release is covered by a go-live license so you can receive support when using it in your production applications. In this release we have focused on issues that regressed throughout the previews, and regaining some performance that was lost as we improved the reliability of hot reload, visual state manager, bindings, and app themes.”

  • .NET MAUI has a go-live license and no breaking API changes from .NET 7.
  • The team addressed a number of bugs with UI components and controls in order to increase uniformity and visual correctness across platforms.
  • For a uniform user experience across platforms, platform-specific updates addressing drag-and-drop functionality, tab bar look, and certain platform behaviors were implemented.
  • Several optimizations were made to boost performance of of ActivityExtensions.GetWindowFrame on Android, and “Setter Specificity.”
  • Microsoft released.NET 7 service release 8 (version 7.0.96) with high-priority updates.
  • With Visual Studio 17.8 Preview 3 or the most recent stable version of Visual Studio for Mac, Xamarin developers may use Xcode 15 and Android API 34.

The.NET MAUI release notes include further information.

.NET 8

“.NET 8 RC2 is now available,” Microsoft said on October 10. “This is the final release candidate. New NuGet package READMEs for.NET packages, easy CLI-based project assessment for MSBuild, publishing containers to tar.gz files, and Tensor Primitives for.NET are included in this version.

The following are some of the announcement post’s highlights:

  • NuGet package READMEs for.NET packages are provided to offer users with critical information and to assist them in rapidly understanding what a library is and what it does. This is part of the dev team’s ongoing efforts to improve the uptake and quality of NuGet package READMEs.
  • MSBuild now has a new, easy CLI-based project assessment feature that makes it simpler to incorporate MSBuild data into scripts or tools by utilizing the –getProperty, –getItem, and –getTargetResult parameters to assist project analysis.
  • The SDK Container Publish tools now includes the ability to immediately construct a container as a tar.gz archive, which can be beneficial for processes that involve scanning or transferring the image before sending it, hence broadening potential deployment possibilities.
  • Tensor Primitives for.NET are now available, boosting support for machine learning and data science activities. Tensor Primitives is a new collection of APIs that add support for tensor operations, which are critical in AI and machine learning applications. It includes vectorized versions of operations such as cosine similarity, dot product, matrix multiplication, and others.

The.NET 8 RC2 release notes also provide information on important fixes and much more.

ASP.NET Core

According to the announcement article regarding ASP.NET Core enhancements in.NET 8 RC 2, much of the dev team’s efforts in this cycle were spent to Blazor, Microsoft’s scheme for doing web development largely using C# rather than the traditional mainstay, JavaScript. The post said 11 things for Blazor, when every other component has just one item, with the exception of Servers & Middleware, which has two. Microsoft included an essential new notion for Blazor in .NET 8, the ability to deliver a full-stack Web UI.

The following are some of the announcement post’s highlights:

  • New features in HTTP logging middleware include duration logging, merged logs, and configurable interceptors.
  • Version 7x of the IdentityModel library has been released, which increases efficiency, consistency, and Native AOT compatibility.
  • Blazor now supports types with IFormFile attributes and form binding for simple APIs.
  • The SignalR TypeScript client now supports stateful reconnect, reducing downtime for clients experiencing brief network difficulties.
  • The Blazor Web App template now has additional options for enabling interactive render mode globally or per page, as well as using the Blazor identity UI.
  • The Blazor WebAssembly Standalone App template has been renamed and changed to allow static site hosting in the absence of an ASP.NET Core server.
  • Blazor’s form model binding now respects data contract characteristics for customizing how form data is tied to the model.
  • HttpContext may now be accessed from a static server component as a cascade parameter.
  • In a Blazor Web App, the PersistentComponentState service can now be used to save and access component state.
  • Using the [Inject] Attribute now enables injecting keyed services using the InjectAttribute.Key property.

Wrapping Up

The introduction of.NET 8 RC2 marks an important step toward the eventual release of.NET 8 in November 2023. This release contains updated NuGet package READMEs, easy CLI-based project assessment for MSBuild, publishing containers to tar.gz files, and Tensor Primitives for.NET.

Overall, .NET 8 RC2 is a strong release with a slew of important additions and enhancements. I strongly advise all .NET developers to download and test this release candidate.

.NET vs. .NET Framework: Choosing the Right Option for Server Apps

No Comments »

As the demands for robust and efficient server applications continue to grow, choosing the right platform for development has become increasingly crucial. In this article, we will compare .NET and .NET Framework, highlighting their differences, benefits, and considerations for choosing the right option. By the end of this guide, you will have a better understanding of which option best suits your server app development needs.

Let’s dive in and explore the world of .NET and .NET Framework for server apps!

What is .NET?

.NET is a free, open-source framework developed by Microsoft that allows developers to create applications for the Windows operating system. .NET can be used to create a wide range of applications, from small console programs to large-scale web applications.

One of the main benefits of using .NET is that it is platform-independent, meaning it can be used to create applications that run on different operating systems, such as Windows, Linux, and macOS. The framework also includes a large set of libraries and tools that can help developers build robust and efficient applications quickly and easily.

What is .NET Framework?

.NET Framework is a software framework developed by Microsoft that is widely used for building and running Windows-based applications. It is an integral part of the .NET platform and provides a runtime environment and a set of libraries and components that developers can use to create applications.

The main goals of .NET Framework are to provide a consistent programming model for building applications, to enable code reuse and compatibility across different versions of Windows, and to provide a secure and reliable runtime environment for executing code. Developers can use .NET Framework to build a wide range of applications, including desktop applications, web applications, and server-side applications. Its extensive library support makes it easy to leverage existing code and functionality, while its performance and security features make it a popular choice for mission-critical applications.

Key Differences Between .NET and .NET Framework

While .NET and .NET Framework share similarities, there are some distinct differences that can affect your decision for server app development.

Criteria

.NET

.NET Framework

Versions

Newer, cross-platform versions (such as .NET Core)

Windows-only, older versions

Compatibility

May require updates to work with some older Windows systems

Backwards compatible with older Windows systems

Functionality

Lighter weight and faster, but may require additional libraries for certain features

Comprehensive libraries and components for a wide range of features

The choice between .NET and .NET Framework largely depends on your specific project requirements and infrastructure. If you prioritize speed and agility, .NET may be the better choice. If you need a more comprehensive set of features and backward compatibility with older systems, .NET Framework may be the better choice.

Benefits of Using .NET for Server Apps

When it comes to server app development, using .NET can provide a range of benefits for developers and organizations. Here are some of the reasons why:

Performance: .NET is designed to be fast and efficient, making it a suitable choice for high-performance server apps.

Scalability: .NET enables developers to build scalable server apps that can handle large volumes of traffic and users.

Security: .NET includes various security features and built-in protections to help safeguard server apps from potential threats and attacks.

Developer Productivity: .NET provides an extensive set of tools, frameworks, and libraries that can help developers work more efficiently and streamline development processes.

Overall, using .NET can help developers build robust and reliable server apps that meet the needs of their organizations and users.

Advantages of Using .NET Framework for Server Apps

While .NET offers a range of benefits for server app development, there are also several advantages to utilizing .NET Framework. Here are some key benefits to consider:

Extensive Library Support: .NET Framework includes a vast array of pre-built libraries and components, making it easier for developers to build complex server apps without having to write all the code from scratch.

Backwards Compatibility: One of the major advantages of .NET Framework is its ability to run older .NET applications without needing to make any significant changes. This makes it a great choice for enterprises with existing server infrastructures that rely on legacy software.

Mature Ecosystem: Since .NET Framework has been around for over a decade, there is a large community of developers and resources available. This can be particularly helpful for troubleshooting issues, finding libraries, and sharing knowledge with others.

In addition to these benefits, .NET Framework also offers good performance and security capabilities. It is optimized for running on Windows servers and integrates well with other Microsoft technologies, such as Visual Studio and SQL Server.

Considerations for Choosing the Right Option

Choosing between .NET and .NET Framework for server app development can depend on several factors, including your project requirements, existing infrastructure, and future scalability needs. Here are some considerations to keep in mind:

Consideration

.NET

.NET Framework

Compatibility

Works across multiple platforms, including Windows, Linux, and macOS.

Primarily designed for Windows-based environments.

Functionality

Provides a lightweight and modular framework for building web, cloud, and mobile apps.

Offers a comprehensive library of pre-built components and tools for building desktop and server apps.

Community Support

Has a large and active open-source community with regular updates and contributions.

Has a mature ecosystem with established support channels and documentation.

Development Skills

Requires knowledge of C#, ASP.NET, and modern web development concepts.

Requires expertise in Windows-based technologies like .NET Framework, Visual Studio, and WinForms.

Ultimately, the choice between .NET and .NET Framework will depend on your specific needs and goals. If you are building a web or mobile app that needs to run on multiple platforms, .NET may be the best choice. On the other hand, if you are developing a Windows-based desktop app that requires a lot of pre-built components, .NET Framework could be the better option.

Wrapping Up

One thing I would like to add is that the choice between .NET and .NET Framework is not always a binary decision. In some cases, it may be possible to use both platforms together. For example, you could use .NET to build a web app that runs on Linux servers, while using .NET Framework to build a desktop app that runs on Windows machines. Ultimately, the best way to choose the right platform for your project is to carefully consider your specific needs and requirements.

Getting Started with ML.NET: Setting Up a Machine Learning Environment

No Comments »

By enabling systems to learn from data and make predictions or judgments without explicit programming, machine learning (ML) has transformed a number of sectors. Developers can embed machine learning models into their .NET applications using ML.NET, a Microsoft open-source machine learning framework. To make sure you have everything you need to begin your machine-learning adventure, we will walk you through the process of setting up a machine-learning environment with ML.NET in this post.

Installing Visual Studio

Installation of Visual Studio, a popular integrated development environment (IDE) for.NET developers, is the first step in starting our ML.NET adventure. A user-friendly interface and a variety of tools are provided by Visual Studio to make ML.NET development easier. How to install Visual Studio is as follows:

  • Access the most recent version of Visual Studio that is compatible with your operating system by visiting the official Visual Studio website
  • Run the downloaded installer and adhere to the prompts on the screen.
  • You will be prompted to choose the workloads you wish to install during the installation process. Select the workload “.NET desktop development” to access the ML.NET development-specific components.
  • Launch Visual Studio after the installation is finished to move on to the next action.

Setting Up ML.NET

After installing Visual Studio, let’s set up ML.NET:

  • Start Visual Studio, then choose “Create a new project.”
  • Run a search for “ML.NET” in the project template selection screen’s search field. Numerous ML.NET project templates are available, including “ML.NET Console App” and “ML.NET Model Builder.”
  • Based on your needs, select the suitable project template. Choose the “ML.NET Console App” template, for instance, if you wish to create a console application.
  • Click “Create” to start a new ML.NET project after entering the project’s name and location.

Installing ML.NET NuGet Packages

Installing the necessary NuGet packages is necessary in order to use ML.NET in your project. You can manage dependencies with ease using NuGet, a package management for.NET projects. Installing ML.NET NuGet packages is as follows:

  • In the Solution Explorer, right-click the project and choose “Manage NuGet Packages.”
  • Find “Microsoft.ML” in the NuGet Package Manager window and choose the most recent stable version.
  • To include the package in your project, click “Install”.
  • In addition, depending on your particular ML tasks or requirements, you might need to install other ML.NET-related packages. For instance, you can install the “Microsoft.ML.ImageAnalytics” package if you wish to work with image classification.
  • You are prepared to begin researching and leveraging ML.NET in your project after the packages have been installed.

Exploring the ML.NET Documentation

The ML.NET Documentation is a thorough source that provides instructions and examples for using ML.NET successfully. It addresses a broad range of subjects, such as model training, model evaluation, and model deployment. To aid developers in comprehending and making use of ML.NET’s capabilities, the documentation offers step-by-step instructions, code samples, and descriptions of fundamental concepts. Advanced subjects like model explainability, hyperparameter tuning, and transfer learning are also covered in the documentation. It provides advice on how to manage various data kinds, including structured data, text data, and image data, as well as how to pick the best algorithms and models for particular jobs.

Here are some tips for maximizing the ML.NET documentation:

  • Go to the official page of ML.NET documentation.
  • Learn how to use the documentation’s navigation and structure.
  • Start by reading the “Getting Started” section, which gives you an overview of ML.NET, explains its fundamental ideas, and walks you through creating your first ML.NET model.
  • For more information on specific subjects like data loading, data preprocessing, model training, and model evaluation, consult the documentation.
  • To learn more about ML.NET, make use of the code examples and sample projects offered in the documentation.
  • For updates, best practices, and actual use cases, keep a watch on the community resources and the official ML.NET blog.

Accessing ML.NET Samples

It is advised to examine the ML.NET samples offered by the community to get a better knowledge of its capabilities and how to utilize it successfully:

  • To access the ML.NET samples, go to the ML.NET GitHub repository
  • A variety of ML.NET samples arranged in many categories, including classification, regression, clustering, and more, may be found on the repository page. Select the category you are interested in.
  • You can find a selection of sample projects inside the category folder. Each project exemplifies a distinct machine-learning technique or circumstance. Select the sample that best suits your needs, or look through a variety of samples to learn about various ML.NET features.
  • Using the available choices, clone or download the example repository to your local computer. Cloning the repository will make it simple for you to pull updates and contribute to the project if you are familiar with Git.
  • Once you’ve downloaded the sample project to your computer, build and execute the project as directed. Setting up data sources, customizing parameters, or installing extra programs or dependencies can be required.

After the sample has been successfully executed, you can investigate the code and experiment with various parameters to better understand ML.NET and its potential.

You can learn how to use ML.NET in many areas, acquire practical insights into machine learning techniques, and use the community’s contributions to improve your own ML.NET projects by accessing ML.NET samples.

Wrapping Up

The first step in utilizing machine learning in your.NET apps is to set up a machine learning environment using ML.NET. You can prepare yourself for your ML.NET journey by installing Visual Studio, configuring ML.NET, perusing the documentation and samples, joining the community, and staying up to date with new releases. With the help of Microsoft’s vast support network and ML.NET’s user-friendly design, you can begin creating reliable machine-learning models and gaining insightful knowledge from your data. Happy coding!

UI Development in .NET MAUI: Building Beautiful and Functional User Interfaces

No Comments »

In the field of software development, designing user interfaces (UIs) that are aesthetically pleasing and simple to use is essential for gaining and maintaining user engagement. Developers now have a potent framework at their disposal to create cross-platform applications with gorgeous UIs thanks to the introduction of .NET MAUI (Multi-platform App UI). In this post, we’ll examine the fundamentals of .NET MAUI UI development and learn how to make contemporary, responsive, and user-friendly user interfaces.

Understanding .NET MAUI

Microsoft’s cross-platform .NET MAUI (Multi-platform App UI) framework enables programmers to design native user interfaces (UI) for software that can run on various operating systems, including Windows, macOS, iOS, and Android. It is an evolution of Xamarin.Forms and is built on top of the .NET ecosystem.

With the unified development paradigm provided by .NET MAUI, developers can create a single codebase for their business logic and user interface (UI), which can then be distributed to several platforms. This method saves time and effort because there is no longer a need to build unique UI code for each platform.

The framework offers a collection of controls and layouts that are natively generated on each platform, giving the applications a native appearance and feel. Additionally, it provides access to local APIs and support for platform-specific customization, enabling developers to make the most of each platform’s features.

XAML for UI Design

For the purpose of developing user interfaces in .NET applications, especially those created with .NET MAUI, XAML (eXtensible Application Markup Language) is a declarative markup language. It offers a clear and accessible approach to describing the organization, appearance, and behavior of the UI elements. It is simpler for developers and designers to work together when they can separate the UI design from the application functionality using XAML. You can establish data bindings to link UI elements with the underlying data model, specify attributes and events, and describe the visual hierarchy of your UI using XAML.

With the help of the numerous controls, layouts, and style options supported by XAML, you can design engaging user interfaces. Additionally, it enables animations, resources, and templates, allowing you to design extremely adaptable user interfaces.

Responsive Layouts

Responsive layouts refer to the ability of an application’s user interface to adapt and adjust its appearance based on the available screen space and device orientation. In the context of .NET MAUI, responsive layouts play a crucial role in creating user interfaces that can seamlessly adapt to different screen sizes, resolutions, and aspect ratios across various devices.

To achieve responsive layouts in .NET MAUI, developers can leverage XAML’s layout containers such as StackLayout, Grid, and FlexLayout, along with various properties and techniques provided by the framework. These include setting appropriate constraints, using adaptive triggers, employing adaptive layouts, and leveraging platform-specific APIs to optimize the UI for each device type.

Styling and Theming

Styling and theming are essential aspects of UI design that allow developers to define the visual appearance of their applications. In .NET MAUI, developers can use XAML to apply styles and themes to their UI elements, ensuring a consistent and visually appealing user experience.

Styles in XAML allow developers to define a set of visual properties that can be applied to multiple UI elements. This promotes code reuse and simplifies the process of updating the appearance of UI elements throughout the application. Themes, on the other hand, provide a way to switch between different visual styles based on user preferences or application requirements.

By leveraging styles and themes effectively, developers can create visually appealing interfaces, maintain a consistent design language, and enhance the overall user experience.

Data Binding

Data binding is a powerful feature in .NET MAUI that allows developers to establish a connection between the data and the user interface elements. It enables automatic synchronization of data between the model or view model and the UI, reducing the need for manual updates and providing a more responsive and interactive user experience.

In .NET MAUI, developers can use XAML to define data bindings between UI elements and the underlying data sources. This can include binding UI controls to properties, collections, or commands in the code-behind or view model. By establishing these bindings, any changes in the data source are automatically reflected in the UI, and user interactions can update the underlying data seamlessly.

Data binding simplifies the development process by decoupling the UI from the data, making applications more flexible, maintainable, and scalable.

Performance Optimization

When creating cross-platform apps like those in .NET MAUI, performance optimization becomes a crucial component of application development. Here are some essential factors for performance optimization:

  • Effective Data Binding: When it comes to regularly changing data, use data binding carefully and prevent frequent binding modifications. When applicable, take into account employing one-time or one-way data bindings.
  • Asynchronous Programming: To keep the UI fluid and avoid blocking the main thread, use asynchronous programming techniques like async/await. When possible, move time-consuming tasks to background threads.
  • Caching and Memory Management: Use caching techniques to lessen the need for repeated data retrieval and processing. To avoid memory leaks, appropriately dispose away unused resources.
  • Use UI virtualization techniques for lists and grids to quickly render massive datasets by only loading elements that are visible.

Conclusion

With the help of .NET MAUI, developers can create beautiful cross-platform UIs with less time and effort and a single codebase. .NET MAUI gives you the tools to build stunning and useful user interfaces that provide a wonderful user experience on a variety of devices and operating systems thanks to its robust UI design capabilities, responsive layouts, styling and theming options, support for data binding, and integration with platform-specific features. Accept the potential of .NET MAUI for UI development and you’ll be able to produce outstanding applications that your users will love.

ASP.NET MVC Overview: Building Scalable Web Applications

No Comments »

Microsoft offers ASP.NET MVC (Model-View-Controller), a potent framework for creating scalable and maintainable web applications. With its extensible architecture and separation of concerns, ASP.NET MVC provides developers with a structured method for building dynamic and reliable websites. The main ideas, elements, and advantages of ASP.NET MVC will be discussed in this article, along with an overview of its essential attributes and an explanation of how it makes it easier to create contemporary online applications.

Understanding the MVC Pattern

The Model-View-Controller (MVC) pattern is the ASP.NET MVC framework’s cornerstone. It is a software architectural design pattern that supports the separation of concerns between the data model (Model), user interface (View), and application logic (Controller). This division makes it simpler to maintain, test, and scale the code. The View takes care of the appearance and user interaction, the Model represents the application’s data and business logic, and the Controller controls the application’s flow.

The MVC pattern enables you to build applications with input logic, business logic, and user interface logic separated from one another while maintaining loose coupling between them. Each type of logic should be placed in the program according to the pattern. The view should contain the UI logic. The controller should contain the input logic. The model should contain the business logic. By allowing you to concentrate on only one part of the implementation at a time, this separation makes it easier for you to manage complexity when developing an application. You may, for instance, concentrate on the view without relying on the business logic.

In addition to controlling complexity, testing apps using the MVC pattern is simpler than doing so with an ASP.NET Web application that uses Web Forms. For instance, a single class is used in an ASP.NET Web application that uses Web Forms to display output and react to user input. It can be challenging to create automated tests for Web Forms-based ASP.NET applications since you need to instantiate the page class, all of its child controls, and other dependant classes in the application to test a single page. Writing tests that specifically target specific components of the application might be challenging because so many classes must be instantiated to execute the page.

Key Components of ASP.NET MVC

ASP.NET MVC is made up of several essential parts that cooperate to produce dynamic web applications:

  • Models are a representation of the data in the application and set out the business logic for modifying and validating that data.
  • Views: Views are in charge of the application’s presentation layer, creating HTML content to display data and gathering user input.
  • Controllers: Controllers interact with models and views, choreograph the application’s flow, and take requests from users and handle them.
  • Routing: ASP.NET MVC employs a routing engine that converts incoming URLs into a list of predetermined controller actions, resulting in a neat and reversible URL structure.
  • Razor View Engine: The Razor view engine, which is ASP.NET MVC’s default template engine, provides a short syntax for creating HTML markup.
  • Helpers: Utility classes known as helpers make routine activities like creating form controls, producing partial views, and navigating URLs easier.

Benefits of ASP.NET MVC

ASP.NET MVC provides the following advantages for creating web applications:

  • Clear separation of concerns is provided by the MVC pattern, which makes it simpler to organize and maintain code by clearly separating data from presentation and application logic.
  • Testability: ASP.NET MVC supports unit testing, which makes it easier to find and fix problems early in the development process because of its modular architecture and distinct separation of concerns.
  • Extensibility: ASP.NET MVC has a high degree of extensibility, enabling programmers to provide additional functionality via filters, model binders, action outcomes, and other means.
  • A robust URL- mapping element that enables you to create applications with understandable and searchable URLs. In addition to supporting URL naming patterns that are effective for search engine optimization (SEO) and representational state transfer (REST) addressing, URLs are not required to include file-name extensions.
  • Rich Ecosystem: ASP.NET MVC is supported by a thriving and active community that offers a plethora of libraries, frameworks, and tools to boost productivity and speed up development.
  • Integration with Other Technologies: ASP.NET MVC works in perfect harmony with other Microsoft products, such as ASP.NET Core for cross-platform development and ASP.NET Web API for creating RESTful services.

Conclusion

By providing a systematic and effective method for creating online applications, ASP.NET MVC enables programmers to write scalable and maintainable code. Developers can accomplish a separation of concerns, increased testability, and extensibility by adhering to the MVC paradigm and leveraging the essential ASP.NET MVC components. It may consequently be more challenging to develop tests for Web Forms-based ASP.NET applications than for MVC applications. A Web server is also necessary for tests in an ASP.NET application that uses Web Forms. It is feasible to test individual components independently of the rest of the framework because of the MVC framework’s decoupling of the components and extensive usage of interfaces. For developers looking to create robust and dynamic online applications, ASP.NET MVC continues to be a popular option thanks to its many advantages and integration options. The tools and flexibility you need to succeed in web development are provided by ASP.NET MVC, whether you are beginning a new project or migrating an old one.

Importance of .NET and C# in 2023

No Comments »

I have a strong interest in knowing what software development technologies are in demand in today’s market. In light of this ongoing progress and change, I find it fascinating that one of the prevailing themes in 2023 is the continued dominance of .NET development with the C# programming language.

The Stack Overflow Developer Poll shows that despite the rise of other technologies, the.NET framework has maintained its popularity. Although the tech industry is always changing, Microsoft’s main developer platform, .NET has been successful since 2000. I’m confident that .NET and C# will continue to be competitive and important for many years to come given Microsoft’s newly announced desire to continue investing in them.

The adaptability of.NET and C# is something I really like. They can be applied to a variety of projects, including desktop, web, and mobile development. They’re also perfect for creating cloud-based apps, which are hugely significant in the tech world of today. Applications are becoming more reliant on distributed systems as a result of the growth of cloud computing.

The basics of C# and .NET

It started out as Microsoft’s answer to Sun Microsystems and its Java platform, but it has now evolved into an open-source framework for creating various types of applications. .NET has you covered whether you want to write web development code, mobile app code, or even contemporary desktop programs.

About .NET

  • Microsoft developed the.NET software development framework, which offers a platform for creating and running apps across a variety of operating systems, including Windows, macOS, and Linux.
  • From its initial release in 2000, it has developed into a collection of strong tools and frameworks for creating cutting-edge and reliable applications.
  • C#, Visual Basic, F#, and many other programming languages are supported by.NET.
  • The.NET Framework Class Library, a sizable library of pre-built classes and functions, is a feature of NET that boosts the productivity of application development.
  • The Common Language Runtime (CLR), the runtime environment for NET, controls how.NET applications are executed and offers features like memory management, security, and exception handling.
  • NET is cross-platform and open-source.

About C#

  • Microsoft created the contemporary, object-oriented programming language C#.
  • It debuted in 2000 as a component of Microsoft’s.NET framework.
  • Simple, potent, and type-safe describe C#.
  • Building desktop, web, gaming, and mobile applications uses C#.
  • Both static and dynamic typing are supported in C#.
  • It has a garbage collector that controls memory allocation and deallocation automatically.

The Reasons .NET and C# are still relevant

Scalability

Enterprise-level applications are best served by C# and.NET because they are highly scalable technologies suitable for both small and large applications, including desktop, online, gaming, and mobile apps. Because of their adaptability, these technologies can be used to create any kind of application that best meets the needs of you and your company.

Cross-platform development

You can build programs using C# and .NET that can operate on a variety of operating systems, including Windows, macOS, Linux, and even mobile devices running iOS and Android. You may create applications that work on a variety of devices and reach a large audience.

Including Microsoft goods in the integration

If you’re working for a company that significantly relies on technologies like Azure and Visual Studio, mastering C# and.NET will make it simpler to develop and deploy applications on the Microsoft platform. With these talents, you may also be able to work on future AI models like Microsoft’s ChatGPT and Bing AI, which are already gaining ground across a wide range of industries.

Strong demand for jobs in the market

Both large tech organizations and startups are in high demand for C# and.NET developers. Since.NET and C# are now extensively utilized in enterprise-level applications, employers are constantly looking for developers with these skills. Given this demand, dedicating time and effort to learning these abilities can set you apart and significantly improve your chances of landing a job, even in the current unstable economic climate.

Simple to learn

Particularly if you’re already familiar with other object-oriented programming languages like Java or C++, C# is a comparatively simple programming language to learn. You may start building applications fast and effectively without relying on a challenging learning curve thanks to its straightforward syntax, which is designed to be both powerful and type-safe.

Community of active developers

There is a sizable and vibrant developer community for C# and.NET that offers a wealth of learning and development resources, including online tutorials, forums, and documentation. Hence, whether you’re a new or seasoned developer, you may find enough support to aid in your learning and development.

The Outlook of .NET and C#

Finally, the potential for these technologies to advance in the future is intriguing and worth following. Microsoft pledges to keep improving C# to accommodate developers’ changing needs and keep it a cutting-edge programming language.

We anticipate that C# developers will work closely with the.NET library and developer tool teams on innovative projects that will boost the language’s potential while preserving its essential characteristics. I therefore completely anticipate that.NET and C# technologies will continue to be preferred solutions for many high-performance software development projects due to their continued popularity among developers.

Wrapping Up

There is an acute scarcity of highly qualified software developers, particularly those with C# and .NET knowledge. Software development is still a strong professional path with lots of room for advancement, despite recent severe layoffs. There will only be more chances and demand for developing scalable apps in the .NET ecosystem using C# and other programming languages as the technology develops and improves under Microsoft’s stewardship.

Updates to ASP.NET Core in .NET 7 Release Candidate 2

No Comments »

On October 11th, 2022, Microsoft released.NET 7 Release Candidate 2. It is supported in production as the last release candidate (RC) for.NET 7.

Visual Studio 17.4 Preview 3 has been used to test.NET 7 Release Candidate 2. If you want to test out.NET 7 with products from the Visual Studio family, we advise using the preview channel builds. We advise using the most recent Visual Studio 2022 for Mac preview if you use macOS.

We want to highlight the key concepts of .NET 7 in this post and give you resources to delve further into the specifics. For a more thorough list of each enhancement and feature added to .NET 7 Release Candidate 2 you can check the previous posts from .NET’s official website.

C# 11

The most recent version of C#, C# 11, is now accessible in.NET 7.

They openly create and develop C#. To view the most recent C# feature requests and meeting notes, connect to them on the CSharpLang repository. As soon as work is scheduled, you can check the Feature Status page to see how things are going. Create a C# project and set the LangVersion property to Preview to experiment with the C# 11 preview features.

Libraries & SDK

The.NET libraries are always getting better. New APIs with completely new features are frequently added. Existing APIs are receiving performance upgrades, which will benefit you if you simply upgrade. New libraries are being created to help you with your daily tasks. Every new version of.NET brings a wealth of enhancements to the.NET SDK, which contains the essential tools for designing, developing, and maintaining.NET projects. Numerous improvements were already present in earlier preview. To read more about new SDK features, see the following:

Re-enable Reflection Fallback For System.Text.Json source generation

.NET 7 introduced an intentional breaking change which removes silent fallback to reflection-based serialization in System. generators for Text.Json sources. Early customer feedback indicates that a significant number of users have (mostly unintentionally) come to depend on the fallback behavior.

Despite the fact that a workaround for the breaking change has been documented, it still calls for a code change, which may not always be possible. Starting with.NET 7 RC 2, you can use the provided AppContext compatibility switch to globally re-enable reflection fallback. To enable reflection fallback once more for all source-generated contexts in your app, add the following entry to the project file for your application:

<ItemGroup>
  <RuntimeHostConfigurationOption Include="System.Text.Json.Serialization.EnableSourceGenReflectionFallback" Value="true" />
</ItemGroup>

See the post on .NET runtime configuration settings for more details on using AppContext switches.

Implementation of Generic Math interfaces correctly

The.NET runtime ensures that user code correctly implements the.NET Generic Math interfaces that use the Curiously Recurring Template Pattern (CRTP). It specifically issues a warning if a type that implements the CRTP pattern and the.NET Generic Math interfaces fails to fill the generic type parameter with the type itself.

For example:

public readonly struct DateOnly : IParsable<DateOnly> // correct implementation of IParsable<TSelf> interface
{ ... }
public readonly struct MyDate : IParsable<DateOnly> // Warns: "The 'IParsable<TSelf>' requires the 'TSelf' type parameter to be filled with the derived type 'MyDate' " the type parameter TSelf
{ ... }

Some built in operators added in .NET 7 for System. System and IntPtr. In.NET 6 and earlier, UIntPtr behave differently from user-defined operators. Some operators that used to throw when the context was unchecked while overflowing are now only allowed to do so when wrapped in checked context, and some operators that did not previously throw in checked context are now only allowed to throw when the context is unchecked. The analyzer alerts it when it finds the code that might be responsible for those behavioral changes.

For example:

checked
{
    intPtr2 = intPtr1 + 2; // Warns: "Starting with .NET 7 the operator '+' will throw when overflowing in a checked context. Wrap the expression with an 'unchecked' statement to restore the .NET 6 behavior."

    intPtr2 = intPtr1 - 2; // Warns: "Starting with .NET 7 the operator '-' will throw when overflowing in a checked context. Wrap the expression with an 'unchecked' statement to restore the .NET 6 behavior."

    void* ptr = (void*)intPtr1; // Warns: "Starting with .NET 7 the explicit conversion '(void*)IntPtr' will throw when overflowing in a checked context. Wrap the expression with an 'unchecked' statement to restore the .NET 6 behavior."

    intPtr2 = (IntPtr)ptr; // Warns: "Starting with .NET 7 the explicit conversion '(IntPtr)void*' will throw when overflowing in a checked context. Wrap the expression with an 'unchecked' statement to restore the .NET 6 behavior."
}

intPtr1 = (IntPtr)longValue; // Warns: "Starting with .NET 7 the explicit conversion '(IntPtr)Int64' will not throw when overflowing in an unchecked context. Wrap the expression with a 'checked' statement to restore the .NET 6 behavior."

int a = (int)intPtr1; // Warns: "Starting with .NET 7 the explicit conversion '(Int32)IntPtr' will not throw when overflowing in an unchecked context. Wrap the expression with a 'checked' statement to restore the .NET 6 behavior."

Support

The release of.NET 7 is covered by Standard Support. There is no change to the support duration despite the fact that this is the new name for what was previously known as Current. The Standard Support period for.NET releases with odd numbers is 18 months. The 36-month length of Long-Term Support (LTS), as well as its name, have not changed. For more information, see our.NET and.NET Core Support Lifecycle document.

Wrapping Up

.NET is loved for it’s simplicity of C# cause everything can be completed quickly and easily (in C#, everyone who can program can program). Similarly, the Jit itself is intuitive in the way it applies compiler techniques. Finally, a shoutout to SuperPMI.

Releases of .NET include products, libraries, runtime, and tooling, and represent a collaboration across multiple teams inside and outside Microsoft. Give .NET 7 Release Candidate 2 a try and tell us what you think!

ASP.NET Authentication: Overview

No Comments »

.NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications. The base platform provides components that apply to all different types of apps. Additional frameworks, such as ASP.NET, extend .NET with components for building specific types of apps.

ASP.NET is an open source web framework, created by Microsoft, for building modern web apps and services with .NET. ASP.NET is cross platform and runs on Windows, Linux, macOS, and Docker. The server-side web application framework ASP.NET, also known as Active Server Pages Network Enabled Technologies, is free to use. It is intended for use in web development to create interactive websites, programs, and services. Let’s take a closer look at ASP.Net Authentication.

What Is ASP.NET Authentication?

Microsoft’s ASP.NET is an open source framework for creating contemporary web sites, services, and applications. It is supported by Linux, macOS, Windows, and Docker. IAuthenticationService is the foundation of the ASP.NET authentication framework. The service can authenticate users in ASP.NET applications thanks to registered authentication handlers.

ASP.NET Authentication Concepts

Authentication Schemes

A scheme for authentication identifies the authentication handler in charge of generating the appropriate set of claims. The names of authentication handlers and the particular configuration settings for each handler’s instance are known as authentication schemes. Schemes can be used to discuss authentication and challenge or forbid associated handler behavior.

Authentication Handler

The actions of an authentication scheme are carried out by authentication handlers. From AuthenticationHandler <TOptions> or IAuthenticationHandler, handlers can be derived. Authenticating users is its main objective. The associated authentication scheme’s configuration and the context of incoming requests will influence how the authentication handler responds.

The handler creates an AuthenticationTicket object, which represents a user’s identity, if the authentication is successful. A “failure” or “no result” is returned if the authentication fails. The handler offers ways to thwart or oppose actions taken by a user. Unauthorized users will be denied access, while unauthenticated users will be presented with a challenge.

Authentication Challenge

When unauthenticated users try to access a resource that needs authentication, the authorization system takes an additional precaution known as authentication challenges. For instance, if an anonymous user clicks on a login link or requests access to a restricted resource, the IAuthenticationService may issue a challenge. The challenge is issued by the authorization system using a default authentication scheme (or a specified scheme if one exists).

Forbid Action

If authenticated users attempt to access resources without the required permissions, the authorization system triggers the ‘forbid’ action for authentication schemes. Users are informed by forbidden actions when they have been authenticated but are denied access to a resource. The following situations, for instance, may result in the system forbidding authentication:

  • An access-restricted page is redirected to by a cookie authentication scheme.
  • A 403 (forbidden) error is returned by a JWT bearer scheme.
  • A page where users can request access to a protected resource is the destination of an authentication scheme.

ASP.NET Core Identity

An API that supports UI login features is called Core Identity. You can manage a variety of user data elements with it, such as user profiles, passwords, roles, tokens, and claims. Users can create accounts using the login information from ASP.NET Core Identity. A supported external login provider, such as Google, Facebook, Twitter, or Microsoft accounts, can also be used to create accounts.

The SQL Server database that houses usernames, profile information, and passwords is typically used to configure Identity. A different persistent store, like Azure Table Storage, is also an option.

Providers of authentication for each tenant

There is no integrated method for multi-tenant authentication in ASP.NET Core. We advise customers to think about Orchard Core or ABP Framework for multi-tenant authentication even though they are able to create one using the built-in features.

Orchard Core is an ASP.NET Core-based multi-tenant, open-source, and modular app framework and an app framework with a content management system (CMS) added on top. ABP Framework supports various architectural patterns including modularity, microservices, domain driven design, and multi-tenancy. See ABP Framework source on GitHub.

ASP.NET Multi-Factor Authentication

During a sign-in event, multi-factor authentication (MFA) asks the user for multiple forms of identification. Passwords are frequently used as the first identification factor, and a fingerprint scan, a FIDO2 key, or a verification code sent to the user’s phone can be used as the second factor. Adding MFA as a requirement for an application greatly increases the security of authentication.

Using ASP.NET Core Identity offers native support for 2FA (2-factor authentication). Set the IdentityUserTKey> to enable or disable 2FA for a specific user. Property TwoFactorEnabled. When utilizing ASP.NET Core Identity, cMFA with the Time-based One-Time Password (TOTP) algorithm is additionally natively supported. This approach is compatible with authenticator programs like the Google Authenticator and the Microsoft Authenticator.

Users accessing sensitive pages in an ASP.NET Core Identity application can be forced to use MFA. This is beneficial for programs with various levels of access for various identities. Users can log in using their password, for instance, to view profile information, but administrators need MFA to access admin pages.

Wrapping Up

Finding a user’s identity is the first step in user authentication. We take this action to make sure they are who they claim to be. Once we are confident in our ability to trust them, we can log them into our app and give them access to resources that are intended for logged-in users only. Now that you know how to authenticate and log in a user to an ASP.NET application, hopefully you are off to a good start.

keep looking »