stream:// .net core

July 20, 2020
[DISPLAY_ULTIMATE_SOCIAL_ICONS] Blazor is a new Single Page Application (SPA) technology by Microsoft. It is a comparable technology to React, Angular, and Vue.js but uses C# instead of JavaScript. It brings C# to the world of SPAs and challenges traditional web apps frameworks such as ASP .NET Web Forms and ASP .NET Core MVC for building web apps. This article discusses the choice between SPAs and traditional web apps and explains the difference between server-side and client-side rendering.  What are Traditional Web Apps? Traditional web apps are apps that have little or no client-side processing. HTML is rendered server-side and passed to the browser. They mostly center around static text and filling out forms, and most interactions require a full page refresh. Browsers send data to the server via HTML forms, and the server handles the processing. Technologies like ASP (including all flavors such as classic, and MVC) and  PHP facilitate the transfer of data between the client and server and handle server-side processing. They mix server-side and client-side logic by allowing developers to declare the client-side UI with HTML alongside code that runs on the server. Forms can be developed quickly with no separation between APIs and front-end code. Traditional web app workflow typically presents the user with a form, a submit button, and a full-page response is received from the server after they click the button. The result is usually a disjointed and unsatisfactory user experience. In the approach, APIs are typically not made as first-class citizens. Traditional web apps usually require developers to build a separate set of APIs for consumption by 3rd parties or other apps such as phone apps. It often leads to code duplication. ASP Web Forms is an example of a traditional web app technology. It is possible to build SOAP Web Services, but it does not support designing modern Web APIs. Microsoft introduced ASP.NET Core for flexibility. It supports everything from modern Web APIs to traditional web apps. The MVC flavor of ASP.NET Core is a framework for building traditional web apps. What are Single Page Apps? Single page apps are web-based apps where UI is dynamically modified based on data transfer with the server via API calls. SPAs render the HTML DOM on the client-side. They are analogous to native phone or desktop apps. The server generally transfers all HTML, JavaScript, and CSS or WebAssembly code at the beginning of the session and does not transfer these as part of subsequent API calls. The browser modifies the HTML DOM instead of requesting the full HTML from the server. Ajax was the first step toward SPA frameworks. The approach became popular in the early 2000s. It uses JavaScript to call server-side APIs and so on to allow for asynchronous partial page refreshes. It provides a radical user experience improvement over traditional web apps. The browser can perform partial updates of data on the screen, and there is no HTML transfer on each call. Many traditional web apps started partially integrating Ajax. Developers added Web services to the back-end, and JavaScript code was served to the browser to call the endpoints. It meant that most traditional apps ended up becoming a mixture of server-side HTML rendering and client-side DOM manipulation with JavaScript.  JavaScript module bundlers such as webpack simplify the process of building pure JavaScript applications. They bundle an application in a similar way to a compiled native application. When coupled with frameworks such as Vue.js, Angular, and React, SPAs are easy to build and deploy. Developers build APIs as first-class citizens in parallel with SPA front-ends. Native app developers and 3rd parties can reuse the APIs so that all applications in the ecosystem depend on the same APIs. Modern systems frequently target platforms such as iOS and Android, so it is critical to reuse back-end infrastructure as much as possible.  What is Blazor? Blazor is a SPA framework that uses compiled C# to manipulate the HTML DOM instead of JavaScript. Blazor allows for server-side or client-side hosting models, but in either case, the browser manipulates HTML DOM client-side. The app remains a SPA app because the user does not experience full page refreshes. Non-Blazor SPA frameworks may have a steep learning curve for C# programmers. Typescript has some similarities to C#, but the programming paradigm is quite different. Bla...
July 14, 2020
We will discuss in detail, Globalization and Localization in ASP.NET Core Application and go through various approaches on changing the Culture of the App.
July 13, 2020
I was first introduced to TPL Dataflow when I watched Stephen Toub talk about it on the MSDN Channel9 Developers Channel. I’ve had very few chances to use the TPL Dataflow library in my professional work, but when I have, it’s been simple and clean to implement. All code is available on my public GitHub where I’ve provided samples for .NET Core 3.0. Why Would I Use TPL Dataflow? If you find yourself having to process a lot of data concurrently in a variety of ways in a single application, you really should take a look.
July 11, 2020
I create the CoronaClient project implement the domain layer. I also create an implementation of our ICoronavirusCountryService using a Coronavirus API. To c...
July 11, 2020
Today the AWS Elastic Beanstalk service extends its .NET support with the creation of the new .NET Core on Linux platform. This new platform version makes it easy to get ASP.NET Core applications deployed to AWS quickly for either a dev stack or a full production environment including enhanced health, patching, autoscaling, and rolling deployments. […]
July 10, 2020
Introducing the .NET Guide – Tutorials, Tips & Tricks for .NET, Rider, and ReSharper – .NET Tools Blog | JetBrains
July 09, 2020
Rider 2020.1.4 and ReSharper Ultimate 2020.1.4 Bugfixes Are Ready! – .NET Tools Blog | JetBrains
July 08, 2020
.NET Core is the future of .NET! Version 4.8 of the .NET Framework is the last major version to be released, and Microsoft has stated it will receive only bug-, reliability-, and security-related fixes going forward. For applications where you want to continue to take advantage of future investments and innovations in the .NET platform, […]
July 07, 2020
[DISPLAY_ULTIMATE_SOCIAL_ICONS] The options for building cross-platform phone, desktop, and web-apps with C# are expanding. I previously wrote about Uno Platform, Xamarin.Forms, and Avalonia UI. The recent Microsoft Build conference mentioned Blazor, Uno Platform and MAUI. MAUI is an evolution of Xamarin.Forms that targets .NET 5/6. Whether or not Blazor can be considered a genuinely cross-platform technology is complicated. This article compares the technologies and some others and attempts to clarify some confusion around the future of C# cross-platform development. BrowserPhonesDesktopIdiomMAUI✔✔XAMLUno Platform✔✔✔XAMLAvalonia UI◑✔XAMLBlazor✔Blazor, HTML/CSSMobile Blazor Bindings✔Blazor, XAMLPlatform / Technology Comparison Note: all technologies mentioned are open-source. Read the previous article MAUI MAUI is an evolution of Xamarin.Forms (XF). It is a technology for building native mobile and desktop apps with C# and XAML. There is no preview available yet. This is the roadmap. However, MAUI should take over from Xamarin.Forms when it is ready. Xamarin.Forms is the flagship Microsoft C# cross-platform technology. It is a mature technology that large organizations have implemented to build many quality mobile applications. MAUI runs on the .NET 5/6 runtime while Xamarin.Forms runs on the Mono runtime for phones. .NET 5 is in preview mode so it could be some time before MAUI itself is production ready or even stable enough to experiment with. Platforms: iOS, Android, Tizen, UWP (WinUI) When to use: Your team already has a Xamarin.Forms appYou want the native look and feel of the native platformYou need to build a native phone and desktop app from a single codebaseYou don't need to target the browser Uno Platform Uno is a technology for building native mobile, desktop, and WebAssembly (WASM) apps with C# and XAML. It is a bridge for UWP that brings Windows 10 (WinUI/UWP) apps to phones, macOS, and the browser. UWP XAML, which is the purest evolution of the Microsoft XAML technology. Uno Platform has a lot of crossover with MAUI, but one point of distinction is browser support. Uno Platform targets WASM, which allows developers to deploy web-apps from a UWP based codebase. Uno's XAML paradigm closely models itself after. The second point of distinction between MAUI/XF and Uno is that XF apps look like their native platform by default while Uno styles the app to be identical across platforms by default. Bookmark my upcoming Introduction to Uno Platform Udemy Course.  Platforms: Browsers, iOS, Android, macOS, UWP (WinUI), Linux support on the roadmap When to use: Your team already has a UWP app or is looking to adopt WinUIYou need to target the browserYour team is familiar with the XAML paradigm from WPF, Silverlight or UWPYou need to build a native browser, phone and desktop app from a single codebase Avalonia UI A cross platform XAML Framework for .NET Framework, .NET Core and Mono Avalonia allows developers to build native applications across Windows, macOS, and Linux. It embraces the XAML paradigm, which is familiar to C# developers who have built WPF applications. It takes on the unique approach of rendering graphics with Skia on Win32, X11 & Cocoa instead of relying on the platform's native controls. The platform also has experimental support for phones, and this promises to make it a strong contender. WASM support is also on the roadmap, which brings it to browsers. Platforms: Windows, macOS, Linux, experimental iOS and Android, browser and full iOS support on the roadmap When to use: Your team already has a WPF appYou need pixel-perfect rendering across platformsYou need to build a cross-platform desktop app from a single codebase (especially Linux)You don't need to target the browser Blazor Blazor is a browser-based technology that uses WASM or SignalR to bring .NET code to the browser. Developers define UI with HTML, and style with CSS, but manipulate the HTML DOM with C# instead of JavaScript. Its popularity has recently surged and strikes a chord with web developers because of the familiarity with HTML DOM access. Blazor apps work like JavaScript apps but with C#. Blazor comes with a syntax called Razor, which is familiar to ASP MVC developers.  Pure Blazor is only a real cross-platform technology insomuch as it runs in most modern browsers. However, Mobile Blazor Bindings (below) bring Blaz...
July 06, 2020
Microservices communication with rabbitmq and core using masstransit. How to communicate in an efficient maner between micro services.

Hot Vacancies

Senior .NET Developer

.NET Core

We are looking for Senior .Net Developer to join Kiev team. You will be part of a team of strong, result-oriented professionals developing new generation tasks management, people management, learning platform.

C# developer

Wallit SRO
.NET Core

A Hybrid exchange (HEX) is the link that will unite the advantages of a centralized exchange, such as cooperation with large investors and the trust of many users with the advantages of a decentralized exchange. Ping Exchange is a hybrid-decentralized exchange with a specific focus on a user-friendly, trading platform which also provides the ability for peer-to-peer, community barter trades. Trading on the Ping Exchange platform with our broker software is exceptionally fast, once again in line with our global design objectives.

Middle .Net developer

.NET Core

We are looking for Middle .Net developer. Our client is a company that serves the terminals around the world!

Backend developer

.NET Core

We are an Irish product company “OneView Healthcare” and we are looking for backend developer!

Lead Software Engineer at ServiceTitan

.NET Core

ServiceTitan is a leading mobile, cloud-based software platform that connects home service companies with value-added products and services. In 2018 the company raised $165 million in Series D funding and became a unicorn startup. 60% of the working time of an Engineer will be devoted to the development, 40% - to the work on requirements, mentorship, and supervision. You will work on new features and products.