Cross-Platform C# UI Technologies 

We're going to use Dapper.NET on our project; that much is not in doubt. However, we're not going to start development with it, and it will not be the only ORM in use. The plan is to develop this project using Entity Framework, and later optimize to use Dapper.NET in certain scenarios where the system needs a performance boost. 

The fourth preview of .NET 7 includes enhancements to observability in the .NET implementation of OpenTelemetry, the addition of properties to track microseconds and nanoseconds in date and time structures, new metrics for caching extensions, performance-boosting “on stack replacement,” APIs to work with .tar archives, and additional features as part of an ongoing effort to improve the performance of and add features to regular expressions in .NET 7.  

These are the customer-reported issues addressed in 15.7.2:

• With 15.7, users installing an extension on the command line with a nested extension may see an error installing. This has been addressed in the 15.7.2 servicing release.
• Anaconda fails to uninstall during upgrade and issues warning (Error 87).
• The SSDT 15.6.0 Installer configuration registry key could not be opened..
• Editor performance Issues when editing JavaScript.
• The Code Coverage functionality in Visual Studio 2017 ignores async methods.
• Missing atls.lib in arm/arm64 after update.
• Test Explorer no longer greys out the previously run unit tests.
• Version 15.7.1 debugs .aspx App in a new Chrome instance even if JavaScript debugging is disabled.
• 15.7 compiler fails with Folly.
• ASP project keeps running after closing the web page.
• Chrome Debugger not working and shows an error message, however, the debugger buttons stay active. .
• Rename Python from Rename on the Refactor menu no longer works.
• Visual Studio Installer doesn't work correctly in low disk space conditions.
• Debugger links to browser when previously not set.
• Problems with template argument deduction for class templates.
• C++ constexpr string_view == fails to compile.
• A regression in Type Providers which use native resources (e.g., FSharp.Data.TypeProviders) has been fixed.
• You can now add files to F# ASP.NET Core projects from the UI.
• Listening to Microsoft-Extensions-Logging causes VS diagnostic events window to disconnect with an error message has been fixed in Service Fabric Tools. 

Ready to get started with Visual Studio 2017? This is your course! Join the experts and get the details, from installation to debugging, in this practical Visual Studio 2017 deep dive.

See how to download and install Visual Studio in standalone and networked environments, along with some of the configuration options, such as choosing your workloads (types of apps or services, languages, and platforms), customizing the installation, and installing language packs. Then, take a tour of the Visual Studio IDE, including all the basics you need to get started with your development projects. Finally, explore debugging in Visual Studio, and learn how to use its features to investigate problems in your code.

Fast timer plugin for countdown and count forward Demo

With this plugin you can easily put a timer on your site, it works both ways. You can use two version, one version is the version for modern browsers with the standards of the ES2017 and the version for old browsers with ES2015 standards. Using the config you can change the tags as letters and numbers, you can also change the text output next to the numbers.

.NET 8 Preview 1 is now available! This is the first preview of the next major version of .NET, which will include the next wave of innovations for web development with ASP.NET Core.

In .NET 8 we plan to make broad investments across ASP.NET Core. Below are some of the areas we plan to focus on: 

In this webinar, we will show the benefits of using DevExpress Object-Relational Mapping Library - the eXpress Persistent Objects - with .NET Core 2. The presentation will quickly cover the basics for those new to DevExpress products, and will show how you can use our ORM to manage data in ASP.NET Core or Xamarin apps. 

At work, we are planning to migrate our WPF application from .NET Framework 4.7 to .NET Core 3.0. The main reason for doing so is that it was always a big pain to organize the updates of the .NET Framework on our customer machines. So being able to bundle .NET Core with our application is a big plus for us. Then, for sure, we are looking for the performance improvements brought by .NET Core and finally the new capabilities brought by the fast pace of innovation of .NET Core.