<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Progress Telerik &amp; Kendo UI - Medium]]></title>
        <description><![CDATA[Highlights of .NET &amp; JavaScript developer news. - Medium]]></description>
        <link>https://medium.com/progress-telerik-kendo-ui?source=rss----27e1c50b50be---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Progress Telerik &amp;amp; Kendo UI - Medium</title>
            <link>https://medium.com/progress-telerik-kendo-ui?source=rss----27e1c50b50be---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:49:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/progress-telerik-kendo-ui" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Progress Telerik Agentic UI Generator vs. Syncfusion Agentic UI Builder]]></title>
            <link>https://medium.com/progress-telerik-kendo-ui/progress-telerik-agentic-ui-generator-vs-syncfusion-agentic-ui-builder-a025d51affb9?source=rss----27e1c50b50be---4</link>
            <guid isPermaLink="false">https://medium.com/p/a025d51affb9</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[telerik]]></category>
            <category><![CDATA[generative-ai-use-cases]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <dc:creator><![CDATA[Progress Telerik & Kendo UI]]></dc:creator>
            <pubDate>Tue, 28 Apr 2026 20:00:46 GMT</pubDate>
            <atom:updated>2026-04-28T20:00:48.318Z</atom:updated>
            <content:encoded><![CDATA[<p>See how the AI-based UI creation tools from devtools powerhouses Progress and Syncfusion stack up when they go head to head.</p><figure><img alt="Progress Telerik vs Syncfusion" src="https://cdn-images-1.medium.com/max/1024/1*MDG9sug1myjUeSzrk7R6Tw.jpeg" /></figure><p>AI-powered code generation has become a significant part of how developers build user interfaces. The <a href="https://survey.stackoverflow.co/2025/ai/#1-ai-tools-in-the-development-process">2025 Stack Overflow Developer Survey</a> found that 84% of developers are now using or planning to use AI tools in their development process.</p><p>Original AI adoption has been through tools like code autocompletion and chat-based assistants, but agentic UI tools take things further. Rather than suggesting the next line of code, they can take a natural language prompt and produce working, styled UI code in seconds.</p><p>However, not all AI generation tools are created equal. The quality of the output, how reliably it builds on the first attempt, how fast it runs and how well it handles things like accessibility and theming can vary quite a bit between tools. These differences matter because a tool that requires a large number of follow-up prompts to correct errors or produce code that doesn’t match the original requirements isn’t truly saving us time.</p><p>In this article, we’ll look at a head-to-head comparison between two agentic UI generation tools: the <strong>Progress Telerik Agentic UI Generator</strong> which includes the <a href="https://www.telerik.com/blazor-ui/documentation/ai/agentic-ui-generator/getting-started">Blazor Agentic UI Generator for .NET/Blazor</a> and the <a href="https://www.telerik.com/kendo-react-ui/components/ai-tools/agentic-ui-generator/getting-started">Kendo UI Generator for Angular and React</a>, and the <a href="https://www.syncfusion.com/explore/agentic-ui-builder/"><strong>Syncfusion Agentic UI Builder</strong></a>. We’ll walk through the results of extensive testing across multiple frameworks, covering output quality, performance, stability, accessibility, theming and more.</p><h3>How the Comparison Was Conducted</h3><p>To make this comparison as fair and thorough as possible, both tools were tested across multiple frameworks using two evaluation approaches.</p><h3>Blazor/.NET</h3><p>On the Blazor/.NET side, 23 prompts were run through the Telerik Agentic UI Generator and the Syncfusion Agentic UI Builder. These prompts ranged from simple single-component requests to complex multi-section layouts like e-commerce catalog pages and CMS admin dashboards. Each prompt’s output was rated on a 0 to 7 scale:</p><ul><li><strong>0–1</strong>: Doesn’t build or crashes with no UI</li><li><strong>2–3</strong>: Partially renders, major sections broken</li><li><strong>4</strong>: Renders but requires multiple prompts to clear build or runtime errors</li><li><strong>5</strong>: Renders but doesn’t match prompt requirements in several areas</li><li><strong>6</strong>: Mostly complete, minor issues</li><li><strong>7</strong>: Fully matches requirements</li></ul><p>The evaluation also tracked how many prompts were needed before the output could successfully build and render, as well as the time (in seconds) from initial prompt submission to output generation.</p><h3>Angular and React</h3><p>For Angular and React, a dedicated evaluation was conducted comparing the Kendo Agentic UI Generator against the Syncfusion Agentic UI Builder. Rather than scoring individual prompts, this evaluation focused on a technical comparison of the tools themselves. By running many prompts and examining the context returned by each tool, the analysis compared how each MCP server helps the AI agent arrive at its output across categories like layout, styling, accessibility, documentation and component handling.</p><h3>Output Quality and Reliability</h3><p>This is the category where the gap between the two tools becomes immediately clear.</p><p>Across the 23 Blazor prompts, the Telerik Agentic UI Generator consistently produced complete, requirement-matching output on the first attempt. The Syncfusion Agentic UI Builder told a different story. It experienced <strong>five failures</strong> where no usable UI was generated at all, and several other prompts that required follow-up prompts to fix errors before the output could even build. Let’s look at a couple of examples.</p><h3>Failures</h3><p>The very first prompt asked both tools to build a login screen with email/password validation and an admin dashboard with a sidebar menu, key metrics and recent activity.</p><p><strong>Prompt</strong>: <em>“I have created an empty application that now needs a login screen and an admin dashboard. Add a login form with email/password fields and validation. After a successful login, redirect to an admin dashboard page featuring a sidebar menu and a main content area displaying key metrics and recent activity.”</em></p><p>The Telerik Generator produced a fully working output on the first attempt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*YHgukCsOhHYSEWN2cKkvSw.png" /></figure><p>The Syncfusion Builder returned an error along the lines of: Error. This response is truncated because it is too long. Try rephrasing your question. No UI was generated at all.</p><p>The second prompt told both tools to create a monitoring dashboard with system health KPIs, a log stream panel, charts for API response times and requests per service.</p><p><strong>Prompt</strong>: <em>“Create a new page using the existing top navigation and footer. In the middle, add 3 rows with 3 responsive columns each. The top row shows system health KPIs for CPU, memory and error counts. The middle rows include a Log Stream panel, a line Chart of API response times and a bar chart of requests per service. The bottom row contains a Deployment History table, an Alerts panel and a list of open tickets.”</em></p><p>The Telerik Generator again produced a fully working output on the first pass.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fDNiUAo0QAVvEHPBb0rI_Q.png" /></figure><p>The Syncfusion Builder hit the same truncation error.</p><p>These are the kinds of prompts that represent real-world use cases. A login screen with a dashboard and a monitoring page with multiple data panels aren’t unusual requests.</p><h3>Errors Requiring Follow-ups</h3><p>Not every issue is an error during the generation process. Some prompts produced output that needed additional work to get running.</p><p>We fired a prompt to ask for a product catalog page with a responsive layout, product cards, a filtering toolbar and expandable detail views. The Telerik Generator handled it cleanly on the first attempt. The Syncfusion Builder hit an error about a missing component parameter and needed a second follow-up prompt to fix it.</p><p><strong>Prompt</strong>: <em>“Create a product catalog page with a responsive CSS layout. The layout should display product cards. Add a toolbar with filtering options, and expandable detail view for each product that work seamlessly on mobile, tablet, and desktop.”</em></p><p>The first output by the Telerik Blazor generator:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/931/1*BGyN0r_5p2A01wPjlP7C-Q.png" /></figure><p>The final output from Syncfusion, after the necessary follow-up prompt:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gD8FBBkgr5XJ7S6ijDohhw.png" /></figure><p>The Syncfusion Builder’s errors in these cases often involved referencing component parameters that don’t exist, which may suggest the tool’s AI agent is working with less reliable component information during generation.</p><h3>Partial Results</h3><p>Not all issues showed up as crashes or errors needing follow-ups. Let’s look at an example of a prompt that was made which involved a theming request.</p><p><strong>Prompt</strong>: <em>“Generate a custom theme for a corporate blue and green color scheme with high contrast accessibility requirements.”</em></p><p>The Telerik Agentic UI Generator created the output matching the requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8AKPK4hUdi7kYT1UdrS06w.png" /></figure><p>The Syncfusion Builder did create a custom theme, but the expected theme wasn’t applied to the output.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*FshL86mk0Xf2FEs-W3pinw.png" /></figure><h3>The Bigger Picture</h3><p>Even when we set aside the failures and only look at prompts where the Syncfusion Builder produced something usable, the outputs still frequently fell short of the original requirements.</p><p>On the Angular and React side, the findings were consistent. While the final rendered UI sometimes appeared similar at a glance, the most significant differences were in how each tool’s MCP server helped the agent arrive at that output. The Kendo Generator’s tools consistently delivered more relevant, targeted context to the AI agent, filtering results to what was actually needed for the prompt. The Syncfusion Builder’s tools returned broader, less filtered responses, often including full component prop lists and governance rules regardless of what was asked.</p><h3>Performance</h3><p>Speed matters when we’re iterating on UI designs with AI. Waiting several minutes for a complex layout to generate can significantly slow down the development flow.</p><p>Across the Blazor evaluation, the Telerik Generator was consistently faster. The speed advantage was most noticeable on complex layout prompts. For example, on a complex e-commerce catalog page with filtering, sorting, responsive breakpoints and pagination, the Telerik Generator completed in about 799 seconds while the Syncfusion Builder took 908 seconds.</p><p>There was one outlier where Syncfusion was notably faster (a simpler single-component case), but across the full set of 23 prompts, the speed advantage consistently favored Telerik.</p><h3>Accessibility</h3><p>Accessibility is often treated as an afterthought, but for enterprise applications, it’s a requirement, not a nice-to-have!</p><p>The Kendo Generator includes a dedicated accessibility tool (<a href="https://www.telerik.com/kendo-react-ui/components/ai-tools/agentic-ui-generator/prompt-library#accessibility-assistant">#kendo_accessibility_assistant</a>) that retrieves WCAG 2.2 Level AA guidelines as a mandatory step in the generation process. It also fetches component-specific accessibility requirements for each component used in the output. This leads to every piece of generated UI having accessibility considerations baked in from the start.</p><p>From what we can gather, and at the time of writing, the Syncfusion Builder doesn’t have a strong accessibility tool like the #kendo_accessibility_assistant.</p><h3>Theming, Layout and Documentation</h3><p>Beyond output quality and speed, the Angular and React evaluation revealed some important architectural differences in how each tool handles theming, layout and documentation.</p><h3>Theming</h3><p><strong>Theming</strong> is more than color selection. The Kendo UI Generator produces a complete design system from a single prompt, including colors, typography, spacing scales, border radius, elevation and shadows. The Syncfusion Builder’s style tool is limited to component state colors and semantic colors. Typography, spacing and elevation aren’t reachable through it, so the generated output may look right in terms of color but lack the design coherence that holds a full application together.</p><h3>Layout</h3><p><strong>Layout</strong> is also where a notable dependency difference comes in. The Kendo UI Generator uses a self-contained layout system built on its own CSS utilities, introducing no external dependencies. The Syncfusion Builder relies on <a href="https://tailwindcss.com/">Tailwind CSS</a>, injected into every project, and works from a catalog of 265+ prebuilt blocks. When the desired layout doesn’t match a catalog entry, the result approximates what was asked for.</p><p>For teams already using Tailwind, this might feel natural but for projects on a different CSS framework (<a href="https://material.angular.dev/">Angular Material</a>, for example), adding Tailwind on top can introduce style conflicts. This can also be a potential blocker for organizations that restrict third-party dependencies.</p><p>Responsiveness follows a similar split: the Kendo UI Generator has a dedicated phase with explicit breakpoint reasoning, while the Syncfusion Builder inherits responsive behavior from Tailwind’s defaults without any first-class responsive logic of its own.</p><h3>Documentation</h3><p><strong>Documentation</strong> plays a bigger role in output quality than it might seem, since it directly shapes how well the AI agent understands the components it’s generating. The Kendo UI Generator injects relevant documentation chunks directly into every component tool call, including API references with full type signatures. The Syncfusion Builder treats documentation as a separate tool, triggered only by specific keywords. At the time of the evaluation, results from this tool were inconsistent and the service had been unavailable for over 24 hours for both Angular and React.</p><p>One other important observation from the Angular and React evaluation: the Kendo UI Generator customizes its workflow per prompt using confidence scores, including only the tools and instructions relevant to each request. The Syncfusion Builder runs the same fixed sequence for most prompts regardless of complexity, and its component tools return the full prop list and approximately 250 lines of governance rules on every call. The result is that <strong>the Kendo UI agent operates on targeted, preprocessed context while the Syncfusion agent carries a heavier payload for every request</strong>.</p><h3>Wrap-up</h3><p>The comparison across Blazor, Angular and React tells a consistent story with these agentic UI generators. The Progress Telerik Agentic UI Generator outperforms the Syncfusion Agentic UI Builder across output quality, reliability, performance, accessibility, theming, layout and documentation.</p><p>On the Blazor side, the Telerik Generator had zero full failures across 23 prompts while Syncfusion had five, along with a consistent speed advantage on complex prompts and more reliable first-pass output. On the Angular and React side, the advantages show up in the underlying architecture, where the Kendo Generator’s tools consistently deliver cleaner, more relevant context to the AI agent.</p><blockquote><em>Get started with AI-empowered development. The </em><a href="https://wwwuat.telerik.com/mcp-servers"><em>Kendo UI and Telerik AI tools</em></a><em> are ready. And they come as part of the free trial of the component libraries.</em></blockquote><blockquote><a href="https://wwwuat.telerik.com/mcp-servers#how-to-try"><em>Try Now</em></a></blockquote><p>For more information on the Progress Telerik Agentic UI Generator, check out the following resources:</p><ul><li><a href="https://www.telerik.com/blazor-ui/documentation/ai/agentic-ui-generator/getting-started">Telerik Agentic UI Generator for Blazor</a></li><li><a href="https://www.telerik.com/kendo-angular-ui/components/ai-tools/agentic-ui-generator/getting-started">Kendo UI Generator for Angular</a></li><li><a href="https://www.telerik.com/kendo-react-ui/components/ai-tools/agentic-ui-generator/getting-started">Kendo UI Generator for React</a></li></ul><p>The full comparison data referenced in this article is available for download:</p><ul><li><a href="https://www.telerik.com/docs/default-source/blogs-docs//syncfusion-builder-vs-telerik-generator-comparison.xlsx">Telerik UI for Blazor Agentic UI Generator vs Syncfusion Agentic UI Builder Comparative Evaluation (XLSX)</a></li><li><a href="https://www.telerik.com/docs/default-source/blogs-docs//syncfusion-ui-builder-vs-kendo-ui-generator.xlsx">Kendo Agentic UI Generator vs Syncfusion Agentic UI Builder (XLSX)</a></li></ul><h3>By Hassan Djirdeh</h3><p>Hassan is a senior frontend engineer and has helped build large production applications at-scale at organizations like Doordash, Instacart and Shopify. Hassan is also a published author and course instructor where he’s helped thousands of students learn in-depth frontend engineering skills like React, Vue, TypeScript and GraphQL.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a025d51affb9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/progress-telerik-kendo-ui/progress-telerik-agentic-ui-generator-vs-syncfusion-agentic-ui-builder-a025d51affb9">Progress Telerik Agentic UI Generator vs. Syncfusion Agentic UI Builder</a> was originally published in <a href="https://medium.com/progress-telerik-kendo-ui">Progress Telerik &amp; Kendo UI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WPF or .NET MAUI — How to Choose]]></title>
            <link>https://medium.com/progress-telerik-kendo-ui/wpf-or-net-maui-how-to-choose-3242975cf641?source=rss----27e1c50b50be---4</link>
            <guid isPermaLink="false">https://medium.com/p/3242975cf641</guid>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[wpf]]></category>
            <category><![CDATA[net-maui]]></category>
            <dc:creator><![CDATA[Progress Telerik & Kendo UI]]></dc:creator>
            <pubDate>Wed, 23 Jul 2025 11:51:36 GMT</pubDate>
            <atom:updated>2025-07-23T11:51:36.273Z</atom:updated>
            <content:encoded><![CDATA[<h3>WPF or .NET MAUI — How to Choose</h3><h4>Creating a desktop application and need to decide between the long-time reliable WPF and the up-and-coming cross-platform .NET MAUI? This post will help you explore the features that matter.</h4><figure><img alt="WPF or MAUI cover image" src="https://cdn-images-1.medium.com/max/1024/0*V8qmsrWh-Tb4PFZc" /></figure><p><em>Brought to you by the team behind </em><a href="https://www.telerik.com/maui-ui?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication"><em>Telerik UI for .NET MAUI</em></a><em> — a complete set of enterprise-grade .NET MAUI components that help you design visually stunning, accessible and high-performing apps faster. Originally published at the </em><a href="https://www.telerik.com/blogs/wpf-net-maui-how-choose?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication"><em>Telerik blog</em></a><em>.</em></p><p>What technology to use is a question that should be considered before starting any new application. It’s even more relevant nowadays when starting a new desktop app, as .NET offers several solutions for a .NET developer to create such. In this post, we will focus on WPF and .NET MAUI and how to choose between them.</p><p>We will consider the following criteria:</p><ul><li>Targeted OS</li><li>Future plans for the application</li><li>Developer background</li><li>Customization ability</li><li>AI capabilities</li><li>Deployment options</li><li>State of the framework</li></ul><h3>Targeted OS</h3><p>This is perhaps the first thing to consider when you have to make such a decision, as it is one of the major differences between the two frameworks.</p><p>Windows Presentation Foundation (WPF) is a UI framework for Windows-based desktop applications. While WPF is a Windows-only framework, .NET Multi-platform App UI (.NET MAUI) is designed to be cross-platform and target Windows, macOS and mobile devices working with iOS and Android.</p><p>So if you need to target both macOS and Windows for your desktop app and reach more end users, .NET MAUI gives you this.</p><p>On the other hand, if you want to target Windows only, WPF is designed exactly for this job. WPF is also the choice if you need to target versions of Windows older than Windows 10.</p><h3>Future Plans for the Application</h3><p>If your answer to the previous question is yes, your current goal is Windows only — stop and think again about future plans. Take into consideration whether the business need will push you to add a mobile version soon.</p><p>In this case, .NET MAUI is a viable solution as it wins here with source code reusability. Developers can reuse code and easily update apps across different platforms.</p><h3>Background</h3><p>When creating a new desktop application and choosing the right toolset and framework, it is important to have the background and learning curve in mind.</p><p>If you are familiar with WinForms or have experience with web development and do not have experience with any XAML technology, .NET MAUI may seem more attainable for you with the abilities of CSS, dependency injection and others. On the other side, .NET MAUI does not offer Visual Studio Designer, typical for other .NET frameworks like WinForms, ASP.NET or WPF.</p><p>If you are familiar with WinUI or Xamarin, note that the XAML language is almost the same for .NET MAUI and learning it will be straightforward. .NET MAUI XAML is actually the <a href="https://learn.microsoft.com/en-us/dotnet/desktop/xaml-services/xaml-2009-language-features">2009 XAML Specification</a>.</p><p>However, if your experience is with Silverlight XAML, which follows 2006 XAML Specification, you will have no issue with WPF, but you will meet some differences with .NET MAUI. I have listed several of these differences in another <a href="https://www.telerik.com/blogs/transform-wpf-app-cross-platform-net-maui?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">.NET MAUI vs. WPF post</a>.</p><h3>Styling and Customization Ability</h3><figure><img alt="Customized .NET MAUI app and customized WPF app" src="https://cdn-images-1.medium.com/max/1024/0*0OUCfL8Rbk1NGLPF" /></figure><p>A good-looking UI is very important for any application, right? 😊</p><p>The good news is that both frameworks offer a lot of possibilities to achieve this, such as Implicit, Explicit,Global Styling and Theming.</p><p>The image above illustrates how a style can be applied to change the default look of a button in both frameworks. (Find the code for any of the platforms in the specific section.)</p><h3>WPF</h3><figure><img alt="Style settings in xaml for WPF" src="https://cdn-images-1.medium.com/max/1024/0*STzBF-zE4wTC3ymx" /></figure><figure><img alt="Button settings in XAML for WPF" src="https://cdn-images-1.medium.com/max/1024/0*ymX_A_tw3wJLq9GC" /></figure><p>One major difference between the two frameworks is the default look on Windows. While WPF is expired from older versions of Windows OS, .NET MAUI UI creates a WinUI app when targeting Windows. This means that your .NET MAUI app will provide the same user experience on Windows as Windows 11 fluent apps.</p><p>Of course, both can be customized. My personal vote here goes for WPF as I find the approach of customization simpler — you rely on XAML. On the other hand, .NET MAUI offers several approaches. This is powerful but may add an additional layer of complexity.</p><p>WPF MVVM patterns offer clear separation between the UI (the View), the application logic (the ViewModel) and the root data (the Model).</p><p>On top of that, Progress <a href="https://www.telerik.com/products/wpf/overview.aspx">Telerik UI for WPF</a> also offers more than 20 ready-to-use <a href="https://www.telerik.com/products/wpf/overview.aspx#professional-looking-themes">themes</a> that you can use directly or personalize with <a href="https://www.telerik.com/wpf/color-theme-generator">Telerik Color Generator</a>.</p><p>Another important thing to notice is that WPF offers Visual Studio drag-drop designer, while such is not available for .NET MAUI.</p><h3>.NET MAUI</h3><p>.NET MAUI UI offers a native look and feel by default — Windows 11 styling on Windows. The UI can be also customized in several ways:</p><ul><li>Using XAML</li><li>Using CSS, although it’s not possible to fully style a .NET MAUI app using CSS; however, XAML styles can be used to supplement CSS</li><li>Using Handlers (read more here: <a href="https://www.telerik.com/blogs/details/xamarin-renderers-net-maui-handlers?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Xamarin Renderers to .NET MAUI Handlers</a>)</li></ul><p>The XAML code to style a button, for example, looks like this:</p><figure><img alt="Style settings in XAML for MAUI" src="https://cdn-images-1.medium.com/max/842/0*PXGjcIC3EH4M3yOo" /></figure><figure><img alt="button settings in XAML for MAUI" src="https://cdn-images-1.medium.com/max/1024/0*4bcMAlnfT9oIwoAE" /></figure><p>One more thing to notice is the Dark and Light support and the skinning mechanism that the platform offers. <a href="https://www.telerik.com/maui-ui">Telerik UI for .NET MAUI</a> also has theming support on their <a href="https://www.telerik.com/support/whats-new/maui-ui/roadmap">roadmap</a>.</p><h3>AI Capabilities</h3><p>Both platforms, as part of .NET family, can have integration with ML.NET when AI features like image recognition, text classification and others are needed.</p><p>Telerik UI also offers <a href="https://www.telerik.com/conversational-uihttps://www.telerik.com/blogs/details/xamarin-renderers-net-maui-handlers?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Conversational UI</a> and is planning a <a href="https://www.telerik.com/support/whats-new/maui-ui/roadmap?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">AI Prompt</a> component for both platforms to give one more tool to .NET devs for building modern apps.</p><h3>Deployment Options</h3><h4>WPF</h4><p>WPF has multiple deployment options, including:</p><ul><li>XCopy deployment.</li><li>Windows Installer deployment to produce exe, msi or msix. You can also deploy the application on the Microsoft Store once you package it as MSIX.</li><li>ClickOnce deployment, which enables web-style application deployment for non-web applications. (<a href="https://learn.microsoft.com/en-us/dotnet/desktop/wpf/app-development/deploying-a-wpf-application-wpf?view=netframeworkdesktop-4.8#clickonce-deployment">Learn more.</a>)</li></ul><h4>.NET MAUI</h4><p>.NET MAUI apps are configured through a single-project system for managing features across platforms, including settings for deployment per platform. For Windows, we can rely on two options — an MSIX app package (known as a packaged app) or creating an executable file (known as an unpackaged app).</p><h3>State of the Framework</h3><h4>WPF</h4><figure><img alt="WPF Toolbox list" src="https://cdn-images-1.medium.com/max/630/0*y4ltPVNsXfWUokHn" /></figure><p>Microsoft developed WPF in 2006 and it remains an essential part of the .NET Framework. So it is very mature and has a lot of resources, articles and courses available.</p><p>Tooling is also complete with Hot Reload support, VS Designer, Microsoft UI Automation support and a rich UI toolbox.</p><p>The Telerik UI suite also adds 160+ components that save time when you need complex UI, like <a href="https://docs.telerik.com/devtools/wpf/controls/radscheduleview/overview?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Scheduling</a>, <a href="https://docs.telerik.com/devtools/wpf/controls/radgridview/overview2?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">DataGrid</a> or <a href="https://docs.telerik.com/devtools/wpf/controls/radchartview/overview?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Charts</a>. You can find a <a href="https://docs.telerik.com/devtools/wpf/introduction?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">full list of components here</a>.</p><p>Microsoft and Telerik are still adding functionality to keep WPF up to date with the latest .NET capabilities. One of the interesting things in <a href="https://github.com/dotnet/wpf/blob/main/roadmap.md">Microsoft’s roadmap</a> is Windows 11 theming, while Telerik UI will add new components like an <a href="https://www.telerik.com/support/whats-new/wpf/roadmap?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">AI prompt</a>.</p><h4>.NET MAUI</h4><figure><img alt=".NET MAUI toolbox list" src="https://cdn-images-1.medium.com/max/625/0*-W4uP3xfOwoIHOFs" /></figure><p>.NET MAUI is a 3-year-old framework and the desktop features are still being developed. However, they are one of the main goals of Microsoft as well as improving the tooling. See more details in the <a href="https://github.com/dotnet/maui/wiki/Roadmap">.NET MAUI roadmap here</a>.</p><p>Some of the <a href="https://devblogs.microsoft.com/dotnet/5-dotnet-maui-desktop-features">.NET MAUI desktop capabilities</a> added recently are:</p><ul><li>Multi-windows support</li><li>Context Menu</li><li>Tooltip</li><li>Menu</li><li>Pointer gestures</li></ul><p>On top of that, <a href="https://www.telerik.com/maui-ui?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Telerik UI for .NET MAUI</a> is also another tool that you can rely on to build powerful desktop applications with 60+ components, AI and theming capabilities <a href="https://www.telerik.com/support/whats-new/maui-ui/roadmap?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">planned</a>.</p><h3>Conclusion</h3><p>It is great that nowadays .NET developers have more than one stable solution for building desktop applications. If you have already made your choice, you can share it in the comments.</p><p>And no matter what your choice, <a href="https://www.telerik.com/devcraft?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Telerik UI DevCraft</a> is here to support you with both <a href="https://www.telerik.com/products/wpf/overview.aspx?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Telerik UI for WPF</a> and <a href="https://www.telerik.com/maui-ui?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Telerik UI for .NET MAUI</a> including all kinds of desktop components, a free trial, tons of resources, <a href="https://www.telerik.com/support/demos?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">demos</a> and <a href="https://www.telerik.com/forums?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">forums</a> where you can discuss any technology challenges you may have.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3242975cf641" width="1" height="1" alt=""><hr><p><a href="https://medium.com/progress-telerik-kendo-ui/wpf-or-net-maui-how-to-choose-3242975cf641">WPF or .NET MAUI — How to Choose</a> was originally published in <a href="https://medium.com/progress-telerik-kendo-ui">Progress Telerik &amp; Kendo UI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deep Dive into the New .NET MAUI Blazor Hybrid and Web App Solution Template]]></title>
            <link>https://medium.com/progress-telerik-kendo-ui/deep-dive-into-the-new-net-maui-blazor-hybrid-and-web-app-solution-template-e06aa803da7b?source=rss----27e1c50b50be---4</link>
            <guid isPermaLink="false">https://medium.com/p/e06aa803da7b</guid>
            <category><![CDATA[net-maui]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[dotnet]]></category>
            <dc:creator><![CDATA[Progress Telerik & Kendo UI]]></dc:creator>
            <pubDate>Wed, 16 Jul 2025 14:21:39 GMT</pubDate>
            <atom:updated>2025-07-16T14:21:23.763Z</atom:updated>
            <content:encoded><![CDATA[<h3>Deep Dive into the New .NET MAUI Blazor Hybrid and Web App Solution Template</h3><figure><img alt="Cover image with Telerik ninja" src="https://cdn-images-1.medium.com/max/1024/1*0l15n2WGLt9pXgZhsC3QtQ.png" /></figure><p><em>Brought to you by the team behind </em><a href="https://www.telerik.com/maui-ui?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication"><em>Telerik UI for .NET MAUI</em></a><em>— a complete set of enterprise-grade .NET MAUI components that help you design visually stunning, accessible and high-performing apps faster. Originally published at the </em><a href="https://www.telerik.com/blogs/deep-dive-new-net-maui-blazor-hybrid-web-app-solution-template?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication"><em>Telerik blog</em></a><em>.</em></p><p>One of the new features that will surely please many developers is the new .NET MAUI <a href="https://www.telerik.com/blazor-ui/blazor-hybrid?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Blazor Hybrid</a> and Web App template, which will allow you to reuse components in web and mobile projects. In this article, I’m going to tell you what this new template is about and how you can start using it for your future projects. Let’s get started!</p><h3>How to Get the New .NET MAUI Blazor Hybrid and Web App Template?</h3><p>Undoubtedly, the first step you should take is to get the new template to experiment with it. The easiest way to do this is through the <a href="https://visualstudio.microsoft.com/es/vs/preview/">preview version of Visual Studio 2022</a>, which contains the preview versions of future .NET versions.</p><p>An important thing to know is that when you install the Preview version, this installation will not interfere with other Visual Studio installations you have, so it is a safe process to perform.</p><p>The installer is the same as Visual Studio 2022, you just need to make sure to select the .NET MAUI Multi-platform App UI development workload, as seen in the following image:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/0*AYj7Rkl7GjIuZjOX" /></figure><p>When the installation process is finished, you will be ready to explore the newly installed template.</p><h3>Template Overview</h3><p>Once the preview version of Visual Studio 2022 has been installed, you can start the process to create a new project, which will display the available templates according to the workloads selected in the installation. An easy way to find the new template is by filtering it through the Blazor Hybrid project type, as seen below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/558/0*Fx60sWZfnQUEEfjI" /></figure><p>The next step is to select the template to configure the name and location of the solution, to later move on to the Additional Information window.</p><p>This is a common configuration window in Blazor projects, which allows you to select the Framework version, if you want to use HTTPS, the Interactive rendering mode, among other properties. In my case, I will leave the default values as seen below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/0*sJp0olG5Cy56kQLs" /></figure><p>With this information, you can click on the Create button to create the new project.</p><p>Once the solution has been created, you will see that it is composed of three projects, unlike a .NET MAUI Blazor Hybrid App project that only consisted of a single project.</p><h3>Template Structure</h3><p>Let’s look a little more in detail at the projects that have been created with this new template.</p><p>First, we have a project with the .Shared ending. This project is the one that will allow us to create and host components that can be shared for both the .NET MAUI application and the Blazor project. This is a great advantage in the .NET development world, as for the first time we will be able to create projects that target both mobile devices and web browsers while reusing code to the maximum through Razor components.</p><p>In the example project, you can see that this component contains the application Layouts, a set of Razor pages, the routing file and the definition of the IFormFactorinterface, which will be reused from the other projects:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/0*ue8WM1BhhgNWcQZQ" /></figure><p>Secondly, we see a project with the .Web ending. This project is the Blazor project that we can run in a web browser through the interactive rendering mode selected in the configuration screen.</p><p>Within this project, you can see components specific to the Blazor project, such as the file that serves as an entry point App.razor, the error handling component Error.razor and the initialization file Program.cs. Additionally, you can notice that there is also a reference to the Shared project in the dependencies section:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/331/0*uYjwpUUZiHTFH9lF" /></figure><p>Lastly, the project that has the same name as the solution (unless you have changed the project name) is the .NET MAUI project. This project has configurations to target different platforms such as Android, iOS, Windows, among others.</p><p>In this project, we can notice some interesting things, like the fact that there is a folder called wwwroot with the files index.html and app.css, which serve to render the Blazor components. Additionally, there is a reference to the Shared project from each library of each platform (in the image below I show only the Android one), as well as a Components folder where we could add components specific to the mobile project:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/359/0*AGsgqttR9vqCBNAT" /></figure><h3>Operation of the Example Project</h3><p>Now that you know how the example project is composed, let’s examine in more depth how you can access the features of each platform thanks to the sample code.</p><p>Earlier, I mentioned that the Shared project defines an IFormFactor interface that has the following structure:</p><pre>public interface IFormFactor<br>{<br>    public string GetFormFactor();<br>    public string GetPlatform();<br>}</pre><p>It is this interface that defines which methods will be implemented on each platform, both Blazor and .NET MAUI.</p><p>In the Blazor project, you can see that within the Services folder there is a FormFactor.cs file, which looks like this:</p><pre>public class FormFactor : IFormFactor<br>{<br>    public string GetFormFactor()<br>    {<br>        return &quot;Web&quot;;<br>    } <br>public string GetPlatform()<br>    {<br>        return Environment.OSVersion.ToString();<br>    }<br>}</pre><p>This class returns a string with the value Web through the GetFormFactor method to represent that we are running the Blazor project, in addition to getting the operating system version through the OSVersion property in the GetPlatform method.</p><p>On the other hand, in the .NET MAUI project within the Services folder there is also a FormFactor class that has the following structure:</p><pre>public class FormFactor : IFormFactor<br>{<br>    public string GetFormFactor()<br>    {<br>        return DeviceInfo.Idiom.ToString();<br>    }<br>public string GetPlatform()<br>    {<br>        return DeviceInfo.Platform.ToString() + &quot; - &quot; + DeviceInfo.VersionString;<br>    }<br>}</pre><p>In this class, we use the DeviceInfo class, which allows obtaining information about the platform on which the application is being executed. In this example, the Idiomproperty is used in the GetFormFactor method to know on what type of device the application is running. And within the GetPlatform method, the Platform and VersionString properties are used to know the operating system and its respective version.</p><p>When running the Blazor application, we get the following result:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/981/0*x1cdCba39kxWKr8i" /></figure><p>On the other hand, if we select the .NET MAUI project as initial and specify a startup platform, for example Android, we will get the following result:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/458/0*okWN5fJHaERgg7t2" /></figure><p>Undoubtedly, being able to reuse components between both platforms is exciting and will encourage more developers to go this route to deploy their solutions on the most well-known and used platforms today.</p><h3>Creating an Image Generator App with the Flux Model Sharing Telerik Components in Blazor and .NET MAUI</h3><p>The time has come to get to work to create an interesting image generator project, using the FLUX.1 schnell model, which is super realistic and powerful. Additionally, we are going to use Progress Telerik UI components, which allow us to use pre-created controls for simple and agile development.</p><p>To start, you must create a new project by selecting the .NET MAUI Blazor Hybrid and Web App template. Next, we are going to focus on configuring the Shared project.</p><h3>Configuring the Shared Project to Add the Image Generator Component</h3><p>Once we have created the new project, we are going to add the reference of the Telerik controls to the .Shared project, according to one of the <a href="https://www.telerik.com/blazor-ui/documentation/introduction?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">installation methods</a>. In my case, I have chosen to add the Telerik NuGet package to the project.</p><p>Next, we open the _Imports.razor file to add the global namespaces and not have to be referencing them in each component, ending up as follows:</p><pre>@* required *@<br>@using Telerik.Blazor // set component parameters<br>@using Telerik.Blazor.Components // recognize components tags<br>@using Telerik.SvgIcons // use SVG icons<br>@using Telerik.FontIcons // use font icons<br>@* optional *@<br>@using Telerik.DataSource // implement data-related programmatic customizations<br>@using Telerik.DataSource.Extensions // use OnRead events and ToDataSourceResult()</pre><p>With the namespace file ready, the next step is to create our own Razor Component, which you can add through a right-click on the Pages folder in the project with the .Shared ending | Add | Razor Component. I have called the new component FluxGenerator, but you can name it whatever you want.</p><h3>Creating the New Component</h3><p>Once the new component is created, replace it with the following code:</p><pre>@page &quot;/flux&quot;<br>@using System.Text.Json<br>@using System.Net.Http.Headers<br>@using System.Text<br>@using Telerik.Blazor.Components<br><br>&lt;div class=&quot;container py-5&quot;&gt;<br>    &lt;h1 class=&quot;text-center mb-5&quot;&gt;AI Image Generator&lt;/h1&gt;<br>    &lt;div class=&quot;row justify-content-center&quot;&gt;<br>        &lt;div class=&quot;col-lg-8&quot;&gt;<br>            &lt;div class=&quot;card custom-shadow&quot;&gt;<br>                &lt;div class=&quot;card-body&quot;&gt;<br>                    &lt;div class=&quot;mb-4&quot;&gt;<br>                        &lt;label for=&quot;prompt&quot; class=&quot;form-label&quot;&gt;Describe the image you want to generate:&lt;/label&gt;<br>                        &lt;textarea class=&quot;form-control&quot; id=&quot;prompt&quot; rows=&quot;3&quot; @bind=&quot;prompt&quot; placeholder=&quot;E.g.: A cat astronaut floating in space with Earth in the background&quot;&gt;&lt;/textarea&gt;<br>                    &lt;/div&gt;<br>                    &lt;div class=&quot;d-grid&quot;&gt;<br>                        &lt;button class=&quot;btn btn-primary btn-lg&quot; type=&quot;button&quot; id=&quot;generateBtn&quot; @onclick=GenerateImage disabled=&quot;@isLoading&quot;&gt;Generate Image&lt;/button&gt;<br>                    &lt;/div&gt;<br>                &lt;/div&gt;<br>            &lt;/div&gt;         <br>            &lt;div class=&quot;card mt-4 custom-shadow&quot;&gt;<br>                &lt;div class=&quot;card-body&quot;&gt;<br>                    &lt;h5 class=&quot;card-title mb-3&quot;&gt;Generated Image&lt;/h5&gt;<br>                    &lt;div class=&quot;text-center&quot;&gt;<br>                        @if (isLoading)<br>                        {<br>                            &lt;TelerikLoader Visible=&quot;@isLoading&quot;<br>                                           Size=&quot;@ThemeConstants.Loader.Size.Large&quot;<br>                                           ThemeColor=&quot;@ThemeConstants.Loader.ThemeColor.Tertiary&quot;<br>                                           Type=&quot;@LoaderType.ConvergingSpinner&quot; /&gt;<br>                        }<br>                        else if (!string.IsNullOrEmpty(imageUrl))<br>                        {                            <br>                            &lt;div class=&quot;flex-center&quot;&gt;<br>                                &lt;TelerikCard&gt;                                   <br>                                    &lt;CardImage Src=&quot;@imageUrl&quot;&gt;&lt;/CardImage&gt;<br>                                    &lt;CardBody&gt;<br>                                        &lt;CardTitle&gt;Used prompt:&lt;/CardTitle&gt;<br>                                        &lt;CardSeparator&gt;&lt;/CardSeparator&gt;<br>                                        &lt;p&gt;@prompt&lt;/p&gt;<br>                                    &lt;/CardBody&gt;<br>                                    &lt;CardActions Layout=&quot;@CardActionsLayout.Stretch&quot;&gt;<br>                                        &lt;TelerikButton FillMode=&quot;@(ThemeConstants.Button.FillMode.Flat)&quot; Icon=&quot;@SvgIcon.HeartOutline&quot;&gt;Like&lt;/TelerikButton&gt;<br>                                        &lt;TelerikButton FillMode=&quot;@(ThemeConstants.Button.FillMode.Flat)&quot;&gt;Share&lt;/TelerikButton&gt;<br>                                        &lt;TelerikButton FillMode=&quot;@(ThemeConstants.Button.FillMode.Flat)&quot;&gt;Read More&lt;/TelerikButton&gt;<br>                                    &lt;/CardActions&gt;<br>                                    &lt;CardFooter Class=&quot;k-hbox justify-space-between&quot;&gt;<br>                                        &lt;span&gt;Created by @@hprez&lt;/span&gt;<br>                                        &lt;span&gt;@DateTime.Now.ToShortDateString()&lt;/span&gt;<br>                                    &lt;/CardFooter&gt;<br>                                &lt;/TelerikCard&gt;<br>                            &lt;/div&gt;<br>                        }<br>                        else<br>                        {<br>                            &lt;p&gt;No image generated yet.&lt;/p&gt;<br>                        }<br>                    &lt;/div&gt;<br>                &lt;/div&gt;<br>            &lt;/div&gt;<br>            <br>        &lt;/div&gt;<br>    &lt;/div&gt;<br>&lt;/div&gt;<br><br>@code {<br>    private string prompt = &quot;&quot;;<br>    private string imageUrl = &quot;&quot;;<br>    private bool isLoading = false;<br>    private DateTime StartDate = new DateTime(2019, 5, 2);<br>    private DateTime Min = new DateTime(2015, 1, 1);<br>    private DateTime Max = new DateTime(2025, 12, 31);<br>    private async Task GenerateImage()<br>    {<br>              isLoading = true;<br>        var apiKey = &quot;api-key&quot;; // Replace with your actual API key<br>        var apiUrl = &quot;https://api.together.xyz/v1/images/generations&quot;;<br>        var client = new HttpClient();<br><br>        var requestData = new<br>        {<br>            model = &quot;black-forest-labs/FLUX.1-schnell&quot;,<br>            prompt = prompt,<br>            width = 1024,<br>            height = 768,<br>            steps = 4,<br>            n = 1,<br>            response_format = &quot;b64_json&quot;<br>        };<br><br>        var requestContent = new StringContent(JsonSerializer.Serialize(requestData), Encoding.UTF8, &quot;application/json&quot;);<br>        client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue(&quot;Bearer&quot;, apiKey);<br><br>        var response = await client.PostAsync(apiUrl, requestContent);<br>        if (response.IsSuccessStatusCode)<br>        {<br>            var responseContent = await response.Content.ReadAsStringAsync();<br>            var jsonResponse = JsonDocument.Parse(responseContent);<br>            var base64Image = jsonResponse.RootElement.GetProperty(&quot;data&quot;)[0].GetProperty(&quot;b64_json&quot;).GetString();<br>            imageUrl = $&quot;data:image/png;base64,{base64Image}&quot;;<br>        }<br>        else<br>        {            <br>            Console.WriteLine(&quot;Error generating image: &quot; + response.ReasonPhrase);<br>        }<br>        isLoading = false;<br>    }<br>}<br>&lt;style&gt;<br>    .justify-space-between {<br>        justify-content: space-between;<br>    }<br>&lt;/style&gt;</pre><p>With the above code ready, go to the <a href="https://api.together.xyz/playground/image/black-forest-labs/FLUX.1-schnell">together</a> site and create an account, which will give you an API access key for three months of unlimited and free use, enough time to play with the API. Once you have your API key ready, replace the value of the apiKeyvariable with your key, which will allow you to connect to the service.</p><p>Finally, go to the file located in Layout | NavMenu.razor and add the following section within the div with the class nav-scrollable:</p><pre>&lt;div class=&quot;nav-scrollable&quot; onclick=&quot;document.querySelector(&#39;.navbar-toggler&#39;).click()&quot;&gt;<br>    &lt;nav class=&quot;flex-column&quot;&gt;<br>        ...<br>        &lt;div class=&quot;nav-item px-3&quot;&gt;<br>            &lt;NavLink class=&quot;nav-link&quot; href=&quot;flux&quot;&gt;<br>                &lt;span class=&quot;bi bi-list-nested-nav-menu&quot; aria-hidden=&quot;true&quot;&gt;&lt;/span&gt; Flux Generator<br>            &lt;/NavLink&gt;<br>        &lt;/div&gt;<br>    &lt;/nav&gt;<br>&lt;/div&gt;</pre><p>With this, we finish the configuration of the Shared project.</p><h3>Configuring the Blazor Project</h3><p>For the Blazor project to work correctly, we need to modify the file located in Components | App.razor, adding the following to the head tag:</p><pre>&lt;head&gt;<br>    ...<br>    &lt;link rel=&quot;stylesheet&quot; href=&quot;_content/Telerik.UI.for.Blazor/css/kendo-theme-default/all.css&quot; /&gt;    <br>    &lt;link rel=&quot;stylesheet&quot; href=&quot;css/app.css&quot; /&gt;<br>    &lt;!-- CSS isolation stylesheet --&gt;<br>    &lt;link rel=&quot;stylesheet&quot; href=&quot;AppName.styles.css&quot; /&gt;<br>    &lt;script src=&quot;_content/Telerik.UI.for.Blazor/js/telerik-blazor.js&quot; defer&gt;&lt;/script&gt;<br>    &lt;HeadOutlet @rendermode=&quot;InteractiveServer&quot; /&gt;<br>&lt;/head&gt;</pre><p>On the other hand, in the body tag we will add the following:</p><pre>&lt;body&gt;<br>    ...<br>    &lt;script&gt;<br>        document.addEventListener(&quot;DOMContentLoaded&quot;, function () {<br>           Blazor.start();<br>        });<br>    &lt;/script&gt;<br>&lt;/body&gt;</pre><p>With this change, if we start the application, we will see a screen that asks us for a prompt to generate the image:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1_wXx85rwKgr75cP" /></figure><p>By entering a prompt and clicking on the Generate Image button, a super realistic image is generated in just a couple of seconds:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/0*mhoEAHzpEeX0ybcs" /></figure><p>Now, let’s move on to configuring the .NET MAUI project.</p><h3>Configuring the .NET MAUI Project</h3><p>It’s time to configure the .NET MAUI project. In this case, we need to open the file located in wwwroot | index.html.</p><p>In the head section, we’re going to add the following lines:</p><pre>&lt;head&gt;<br>    ...<br>    &lt;link rel=&quot;stylesheet&quot; href=&quot;_content/Telerik.UI.for.Blazor/css/kendo-theme-default/all.css&quot; /&gt;    <br>    &lt;!-- CSS isolation stylesheet --&gt;<br>    &lt;link rel=&quot;stylesheet&quot; href=&quot;AppName.styles.css&quot; /&gt;<br>    &lt;script src=&quot;_content/Telerik.UI.for.Blazor/js/telerik-blazor.js&quot; defer&gt;&lt;/script&gt;<br>&lt;/head&gt;</pre><p>In the body section there’s no need to add anything, so we won’t touch it. With these changes, we can start the project and enter a prompt:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/0*DocnIQndf-OI-7di" /></figure><p>As you can see, we have the same behavior on a mobile device reusing the Blazor component.</p><h3>Conclusion</h3><p>In this post, you’ve been able to learn in detail about the .NET MAUI Blazor Hybrid and Web App template. Similarly, we’ve created a project that allows you to generate images using AI in an instant, which combined with the use of <a href="https://www.telerik.com/maui-ui?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Telerik controls</a> to allow the creation of apps in a fast and robust way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e06aa803da7b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/progress-telerik-kendo-ui/deep-dive-into-the-new-net-maui-blazor-hybrid-and-web-app-solution-template-e06aa803da7b">Deep Dive into the New .NET MAUI Blazor Hybrid and Web App Solution Template</a> was originally published in <a href="https://medium.com/progress-telerik-kendo-ui">Progress Telerik &amp; Kendo UI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Telerik & Kendo UI Launched AI Coding Assistants and You Can Try Them Free Until June 28]]></title>
            <link>https://medium.com/progress-telerik-kendo-ui/telerik-kendo-ui-launched-ai-coding-assistants-and-you-can-try-them-free-until-june-28-df98fec0ae07?source=rss----27e1c50b50be---4</link>
            <guid isPermaLink="false">https://medium.com/p/df98fec0ae07</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[ai-coding]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[blazor]]></category>
            <dc:creator><![CDATA[Progress Telerik & Kendo UI]]></dc:creator>
            <pubDate>Fri, 30 May 2025 16:44:31 GMT</pubDate>
            <atom:updated>2025-05-30T16:44:31.655Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Progress <a href="https://www.telerik.com/blogs/announcing-telerik-kendo-ui-coding-assistants?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Telerik and Kendo UI AI Coding Assistants</a> were announced on May 28 and with them comes an introductory 30-day period where anybody can get full access. This article is your guide to getting started.</h4><figure><img alt="Telerik and Kendo Coding Assistants Featured Image" src="https://cdn-images-1.medium.com/max/1024/0*azMBYvQLOAF1JOGK" /></figure><p>As a reminder, the Coding Assistants integrate with your preferred IDE and are installed as GitHub Copilot Extensions or MCP tools. They are currently available for <a href="https://www.telerik.com/blazor-ui?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Telerik UI for Blazor</a> and <a href="https://www.telerik.com/kendo-react-ui?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">KendoReact</a> and will be extended to other libraries in the coming months.</p><p>These coding assistants are a subscription benefit, but everybody gets full access until June 28.</p><h4>Who Gets Full Access</h4><ul><li>License holders for Telerik DevCraft, Kendo UI, KendoReact and Telerik UI for Blazor with an active maintenance plan are entitled to full access until June 28.</li><li>Those without licenses to the above only need to <a href="https://www.telerik.com/download?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">sign up for a free trial</a> of one of those products and they will also be able to use the AI Code Assistants.</li><li>Those with a subscription to one of the above get full access as part of their package.</li></ul><h4>How to Get Started</h4><p>We have comprehensive getting started articles for each:</p><ul><li><a href="https://www.telerik.com/blazor-ui/documentation/ai/overview?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Blazor: Telerik AI Coding Assistant</a></li><li><a href="https://www.telerik.com/kendo-react-ui/components/ai-assistant?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">React: Kendo UI AI Coding Assistant</a></li></ul><p>Learn more about the specifics of <a href="https://www.telerik.com/blogs/until-june-28-anybody-gets-full-access-new-ai-coding-assistants?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">how to get access in this blog post</a>.</p><h4>What the AI Coding Assistants Mean for Developer Productivity</h4><p>Today’s developer tools/IDEs come with AI integration, and AI models/agents are getting good at generating code in response to developer prompts. While the potential on the surface is enticing, developer productivity is often hampered by inaccurate responses — AI hallucinations are real without all the context. As the makers of Telerik UI for Blazor and KendoReact, we know our UI the best and can provide contextual grounding for AI — powered by our documentation, API canvas and lots of sample code.</p><p>Telerik and Kendo UI AI Coding Assistants for Blazor/React are surfaced up in two broad ways. Developers can choose the workflow that suits them the best:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w0N6WSi3XFJDJrU92cFsCg.png" /></figure><p>The goal is to maintain developer workflows. GitHub Copilot Extensions and MCP tools work consistently across any IDE/code editor and your choice of AI code generator/models. No need for developers to switch context — Telerik and Kendo UI AI Coding Assistants happily work with established workflows to make developers more productive.</p><p><a href="https://www.telerik.com/blogs/until-june-28-anybody-gets-full-access-new-ai-coding-assistants?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">The AI Coding Assistants are available for anyone to try until June 28. Learn more.</a></p><h4>Contextual Intelligence</h4><p>GitHub Copilot is already one of the most popular and productive coding assistants for developers — an AI pair programmer that helps developers write better code. GitHub Copilot is available across a wide variety of developer code editors/IDEs and brings with it access to the latest AI models.</p><p>We’re happy to augment the capabilities of GitHub Copilot with two specialized GitHub Copilot Extensions: @telerikblazor and @kendoreact. These extensions bring all the context for Telerik UI for Blazor and KendoReact to enable high-quality AI code generation and minimize the need for developers to spend time reworking generic results.</p><p>The GitHub Copilot Extensions are powered by GitHub apps hosted in the cloud (eventually in the GitHub Copilot Extensions marketplace). This instills consistency of developer experiences wherever GitHub Copilot is being used. Here’s how to get started:</p><ul><li>For Telerik UI for Blazor, head to <a href="https://github.com/apps/telerikblazor">https://github.com/apps/telerikblazor</a>.</li><li>For KendoReact, head to <a href="https://github.com/apps/kendoreact">https://github.com/apps/kendoreact</a>.</li></ul><p>For both, developers need to be signed in to the same GitHub account that is being used inside code editors/IDEs. App installation needs to be approved once and then the GitHub Copilot Extensions show up on next launch. Once wired up, developers can talk to our our GitHub Copilot Extensions directly through prompts. Our Telerik/Kendo UI GitHub Copilot Extensions are driven by powerful tokenizers and vector databases behind the scenes.</p><p>Ask us anything around Telerik UI for Blazor. Developers can get specific about UI or API questions:</p><figure><img alt="prompt reads: @telerikblazor show me how to render a Telerik Blazor Grid with sorting, filtering and grouping" src="https://cdn-images-1.medium.com/max/1024/0*J1K70DHvWAg3qPhF" /></figure><figure><img alt="prompt reads: @telerikblazor help me code a Telerik Blazor AIPrompt UI with custom View templats that override default rendering" src="https://cdn-images-1.medium.com/max/1024/0*V3qMONGDcazKKgVc" /></figure><p>Ask us anything around KendoReact, from simple to complex scenarios:</p><figure><img alt="prompt reads: @kendoreact show me code for a KendoReact Grid with multi-column headers and frozen columns" src="https://cdn-images-1.medium.com/max/1024/0*xl0aEVM0YfY9MJ8j" /></figure><figure><img alt="prompt reads: @kendoreact show me how to render a KendoReact Scheduler in month view with event recurring every week" src="https://cdn-images-1.medium.com/max/1024/0*gkCQhWUPk_NQGj3Q" /></figure><p>In GitHub Copilot Ask mode, developers can experiment with a few AI models and settle on the one that works best for given workflows. Our job is to provide deep contextual intelligence around Telerik UI for Blazor and KendoReact.</p><figure><img alt="GitHub Copilot Ask mode with telerikblazor" src="https://cdn-images-1.medium.com/max/1024/0*A6bCNXMfR0Mv6sFT" /></figure><h4>Agent Mode Confidence</h4><p>AI is slowly graduating from a pair programmer to a peer programmer. With the latest agent modes, developers can simply chat using natural language to have AI complete multistep complex coding tasks.</p><p>AI agents can understand entire codebases and recognize/fix errors automatically, suggest and execute terminal commands, and analyze run-time errors until the assigned developer task is complete. If developers are open to giving up the rein a little, AI agentic workflows have the potential to streamline and automate developer tasks — with human intervention where desired.</p><p>The need for context and accuracy is, however, accentuated in AI agentic modes. Developers need confidence to know AI agents will be successful in autonomous actions. Model Context Protocol (MCP) is an open standard protocol that standardizes how applications provide context to AI models/agents. Developers can think of it as a common language for information exchange between disparate systems.</p><p>Developed by Anthropic, MCP aims to provide a standardized way to connect AI models/agents to different data sources, tools and non-public information. This provides deep contextual knowledge and bolsters confidence in performing tasks with customized tools.</p><blockquote>The Promise of Model Context Protocol</blockquote><blockquote>Read more about <a href="https://www.telerik.com/blogs/promise-model-context-protocol?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Model Context Protocol (MCP)</a> to understand its value and explore potential solutions it enables.</blockquote><p>The biggest benefit of MCP standardization is democratizing access to specialized tooling and grounding, through MCP servers to AI agents. Say hello to Telerik and Kendo UI AI Coding Assistance through MCP tools. The goal is contextual power to AI agents.</p><p>The MCP tools are hosted/exposed through MCP Servers with npm packages available to pull them down. Here’s how to get started:</p><ul><li>For Telerik Blazor AI Coding Assistant, head to <a href="https://www.npmjs.com/package/@progress/telerik-blazor-mcp">https://www.npmjs.com/package/@progress/telerik-blazor-mcp</a>.</li><li>For KendoReact AI Coding Assistant, head to <a href="https://www.npmjs.com/package/@progress/kendo-react-mcp">https://www.npmjs.com/package/@progress/kendo-react-mcp</a>.</li></ul><p>To use Telerik/Kendo UI MCP tools, developers need a compatible MCP client. This is commonly found built into coding editors or IDEs, like VS Code, Visual Studio, Cursor and more. Here’s the most common type of configuration, either in a mcp.json locally for a workspace or global settings at the IDE level:</p><pre>...<br>...<br>&quot;chat.mcp.discovery.enabled&quot;: true,<br>&quot;mcp&quot;: {<br>    ...<br>    &quot;telerik-blazor-assistant&quot;: {<br>            &quot;type&quot;: &quot;stdio&quot;,<br>            &quot;command&quot;: &quot;npx&quot;,<br>            &quot;args&quot;: [&quot;-y&quot;, &quot;@progress/telerik-blazor-mcp@latest&quot;],<br>            &quot;env&quot;: {<br>                &quot;TELERIK_LICENSE_PATH&quot;: &quot;&lt;FilePath&gt;/.telerik/telerik-license.txt&quot;<br>            }<br>        },<br>    &quot;kendo-react-assistant&quot;: {<br>            &quot;type&quot;: &quot;stdio&quot;,<br>            &quot;command&quot;: &quot;npx&quot;,<br>            &quot;args&quot;: [&quot;-y&quot;, &quot;@progress/kendo-react-mcp@latest&quot;],<br>            &quot;env&quot;: {<br>                &quot;TELERIK_LICENSE_PATH&quot;: &quot;&lt;FilePath&gt;/.telerik/telerik-license.txt&quot;<br>            }<br>        }<br>    }</pre><p>Once configured, AI agents have access to Telerik/Kendo UI MCP tooling. Envision the agents having an expert at hand, trained in deeply contextual knowledge about Telerik UI for Blazor and KendoReact respectively. Developers can check the listing of MCP tools in agent mode — here’s how VS Code lists them:</p><figure><img alt="MCP Server: telerik-blazor-assistant ; MCP Server: kendo-react-assistant" src="https://cdn-images-1.medium.com/max/1024/0*j4f6ILhPLn4zmcUK" /></figure><p>In Agent mode, developers are again free to use whichever AI model works best — the agents simply have more contextual grounding when it comes to Telerik UI for Blazor and KendoReact usage. To check if MCP tools are installed and available to agents, developers can switch to agent mode. Here’s how VS Code lists tools with #names:</p><figure><img alt="#telerik_blazor_assistant and #kendo_react_assistant" src="https://cdn-images-1.medium.com/max/1024/0*8Ka8PZvPY3Di_Ur_" /></figure><p>With metadata, the MCP tools can be automatically invoked by AI agents with any mention of telerik/kendo. To be sure, developers can always use #telerik-blazor-assistant or #kendo-react-assistant in their prompts. Once everything is wired up, developers can fire away coding wishlists as prompts. The MCP tools get to work with anything to do with Telerik UI for Blazor or KendoReact.</p><p>Here’s an example of adding a Telerik Blazor Grid in a new page to an existing Blazor app:</p><figure><img alt="Let’s add a new page to show a Telerik Grid. GitHub Copilot proceeds and walks the developer through the steps it is taking" src="https://cdn-images-1.medium.com/max/1024/0*Zv9D1JaRXB2oWpL9" /></figure><p>Here’s en example of adding KendoReact references to an existing React app with Next.js:</p><figure><img alt="Let’s add KendoReact to the project. And GitHub Copilot proceeds and walks the developer through the steps it is taking" src="https://cdn-images-1.medium.com/max/1024/0*dYFyD0D-6Z9ZTcUn" /></figure><p>The same Telerik/Kendo UI MCP tools with similar configurations can be leveraged from any code editor. Here’s the experience in Cursor:</p><figure><img alt="Initiating Telerik Blazor UI Assistance in Cursor" src="https://cdn-images-1.medium.com/max/1024/0*jizJWzWmVyyNCMMK" /></figure><h4>Sprinkle of AI</h4><p>While developer productivity has much to gain from modern AI, the benefits should be passed down to users. UI/UX should be smarter. The latest Telerik/Kendo UI Q2 2025 release has lots of other AI-powered updates that enhance the end user experience:</p><ul><li><strong>AI theme generation in Progress ThemeBuilder:</strong> Developers get to effortlessly create custom styles/themes for Telerik/Kendo UI components with natural language AI prompt. Results can be fine-tuned and changes previewed in real time right inside ThemeBuilder before applying to web projects.</li><li><strong>GenAI-powered insights in Telerik Reporting:</strong> Users of Telerik Reporting get instant answers and intelligent summaries, directly within the report preview without the need to use external tools.</li><li><strong>AI-powered document summary and insights in DPL:</strong> The GenAI-enhanced PDF Processing Library enables developers to extract key insights and summaries from documents, thus streamlining analysis.</li><li><strong>New AI prompt in Telerik/Kendo UI Editors:</strong> The Editor control across the board is enriched with side panel and inline AI helper.</li><li><strong>AI building blocks and page templates:</strong> AI App Welcome screen, AI-powered text editor and conversation source are new to the robust collection of building blocks, while a new AI Usage Monitoring dashboard enriches the page templates collection.</li><li><strong>AI Prompt component integration with Microsoft.Extensions.AI package:</strong> Developers get to build AI-powered features in .NET apps more efficiently with out-of-the box abstractions for integrating popular AI services.</li><li><strong>Welcoming AI Prompt into Telerik UI for ASP.NET AJAX:</strong> Developers now get access to the versatile AI Prompt UI control for WebForms projects, allowing easy integration of GenAI capabilities.</li><li><strong>Smart (AI) Grid demos in KendoReact:</strong> Smart Grid demos are now available for KendoReact, thus allowing semantic searches within Grid data.</li></ul><p>Read more release highlights and find all the relevant links in our dedicated release blog post: <a href="https://www.telerik.com/blogs/ai-powered-telerik-kendo-ui-2025-q2-release?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">The AI-Powered Telerik and Kendo UI 2025 Q2 Release Is Here — See What’s New</a>!</p><h4>Seeing Is Believing</h4><p>Words don’t always do justice to modern developer productivity powered by AI — you have to see the developer experience and try things yourself. Come join us for some Q2 release webinars where we’ll unpack all the AI goodness and updates across Telerik, Kendo UI, Reporting, Fiddler and more. Three chances to join and team up for productivity:</p><p>Discover all <a href="https://www.telerik.com/campaigns/kendo-ui-2025-q2-release-webinar?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">updates across KendoReact and Kendo UI for Angular, Vue and jQuery</a>, as well as ThemeBuilder. Tune in 11:00 a.m.–1:00 p.m. ET on Monday, June 2.</p><figure><img alt="KendoUI 2025 Q2 Release Webinar" src="https://cdn-images-1.medium.com/max/1024/0*UKn7Fz85qIzB5pe1" /></figure><p>Discover all updates across Telerik UI for Blazor, UI for ASP.NET Core, UI for ASP.NET MVC, UI for ASP.NET AJAX, UI for WPF, UI for WinForms, UI for .NET MAUI and ThemeBuilder. Tune in 11:00 a.m.–1:00 p.m. ET on Wednesday, June 4.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p-ndf6UDBJTd1UFF" /></figure><p>Discover all updates across <a href="https://www.telerik.com/campaigns/telerik--2025-q2-release-webinar-web--desktop--mobile?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Telerik Reporting and Fiddler Everywhere</a>. Tune in 11:00 a.m.–1:00 p.m. ET Friday, June 6.</p><figure><img alt="Telerik 2025 Q2 Release Webinar Web, Desktop and Mobile" src="https://cdn-images-1.medium.com/max/1024/0*rgEcB6tPp-uAE6XG" /></figure><p>Cheers, developers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df98fec0ae07" width="1" height="1" alt=""><hr><p><a href="https://medium.com/progress-telerik-kendo-ui/telerik-kendo-ui-launched-ai-coding-assistants-and-you-can-try-them-free-until-june-28-df98fec0ae07">Telerik &amp; Kendo UI Launched AI Coding Assistants and You Can Try Them Free Until June 28</a> was originally published in <a href="https://medium.com/progress-telerik-kendo-ui">Progress Telerik &amp; Kendo UI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Angular Basics: How To Get the Value of a Selected Dropdown Menu Item]]></title>
            <link>https://medium.com/progress-telerik-kendo-ui/angular-basics-how-to-get-the-value-of-a-selected-dropdown-menu-item-aad22b1aeda7?source=rss----27e1c50b50be---4</link>
            <guid isPermaLink="false">https://medium.com/p/aad22b1aeda7</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[angular]]></category>
            <dc:creator><![CDATA[Progress Telerik & Kendo UI]]></dc:creator>
            <pubDate>Tue, 27 May 2025 09:03:30 GMT</pubDate>
            <atom:updated>2025-05-27T09:03:30.725Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Angular Basics Featured Image" src="https://cdn-images-1.medium.com/max/1024/1*R4sDCy4J4w3zqQOCL79J2w.png" /></figure><p><em>Brought to you by the team behind </em><a href="https://www.telerik.com/kendo-angular-ui?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication"><em>Kendo UI for Angular</em></a><em> — a complete set of enterprise-grade Angular components that help you design visually stunning, accessible and high-performing apps faster. Originally published at the </em><a href="https://www.telerik.com/blogs/angular-basics-how-to-get-value-selected-dropdown-menu-item?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication"><em>Telerik blog</em></a><em>.</em></p><p>Have you ever had to ask, “How do I get the value of the selected dropdown menu item in Angular?” Let’s answer that!</p><p>In Angular apps, the dropdown is a typical HTML element used in forms and components to allow the users to select values. Today, we will learn three ways to get the value of the user’s selected item in a dropdown list with Angular.</p><p>Our three approaches are:</p><ul><li>Using a change event</li><li>Using ngModel</li><li>Using viewChild</li></ul><p>Our example app has three components with the same HTML markup, a dropdown with a list of NBA teams, and one property, selectedTeam, on the TypeScript file. We will implement each solution to assign the selected value from the dropdown to the selectedTeam variable.</p><ul><li>TeamWithChangeEventComponent: Uses the HTML change event and template reference.</li><li>TeamUsingViewChildComponent: Uses the viewChild decorator and template reference.</li><li>TeamWithNgmodelComponent: Uses the ng-model directive.</li></ul><p>The HTML markup looks like this:</p><pre>&lt;div class=&quot;col&quot;&gt;<br>&lt;p&gt;You select your team {{ selectedTeam }} using viewChild&lt;/p&gt;<br>	&lt;select #teams (change)=&quot;onSelected()&quot;&gt;<br>		&lt;option default&gt;Pick a team&lt;/option&gt;<br>		&lt;option&gt;Lakers&lt;/option&gt;<br>		&lt;option&gt;Miami&lt;/option&gt;<br>		&lt;option&gt;Cleveland&lt;/option&gt;<br>	&lt;/select&gt;<br>&lt;/div&gt;</pre><p>And the TypeScript file will have the variable selectedTeam.</p><pre>{<br>	selectedTeam = &#39;&#39;;<br>}</pre><p>Let’s work with the first solution TeamWithChangeEventComponent.</p><h3>Using the Change Event and Template Reference Variables</h3><p>To work with this approach, we first use HTML reference variables to read the value and the dropdown event change, listen when the user changes the selection in the dropdown, and create a new method onSelected to assign the value to selectedTeam.</p><blockquote><strong><em>How to Build Modern Angular Dropdowns in Minutes with Kendo UI</em></strong></blockquote><blockquote><em>Go beyond HTML select by </em><a href="https://www.telerik.com/blogs/learn-how-to-build-modern-angular-dropdowns-minutes-kendo-ui?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication"><em>learning how to implement modern dropdowns</em></a><em>.</em></blockquote><p>First, create the template variables for dropdown using #teams. Use the event binding to listen for the change event and link with the onSelect method.</p><p>The onSelect method receives the reference variable and takes the value of the dropdown element.</p><p>The code will look like this:</p><pre>&lt;div class=&quot;col&quot;&gt;<br>&lt;p&gt;You select your team {{ selectedTeam }} using change event&lt;/p&gt;<br>	&lt;select #teams (change)=&quot;onSelected(teams.value)&quot;&gt;<br>		&lt;option default&gt;Pick a team&lt;/option&gt;<br>		&lt;option&gt;Lakers&lt;/option&gt;<br>		&lt;option&gt;Miami&lt;/option&gt;<br>		&lt;option&gt;Cleveland&lt;/option&gt;<br>	&lt;/select&gt;<br>&lt;/div&gt;</pre><p>Next, create the onSelected(value) method in the TypeScript file. Take the value as a parameter and assign it to the selectedTeam variable.</p><pre>import { Component } from &#39;@angular/core&#39;;<br>@Component({<br>	selector: &#39;app-team-with-change-event&#39;,<br>	templateUrl: &#39;./team-with-change-event.component.html&#39;,<br>	styleUrls: [&#39;./team-with-change-event.component.css&#39;],<br>})<br>export class TeamWithChangeEventComponent {<br>	selectedTeam = &#39;&#39;;<br>	onSelected(value:string): void {<br>		this.selectedTeam = value;<br>	}<br>}</pre><h4>How Does It Work?</h4><p>Angular uses event binding to link the method, and it gets the value from the parameter because it uses template reference to gain access to the dropdown HTML element.</p><blockquote><em>You can read more about </em><a href="https://angular.io/guide/template-reference-variables"><em>template reference variables</em></a><em> and </em><a href="https://angular.io/guide/event-binding"><em>event binding in Angular</em></a><em>.</em></blockquote><p>Next, using the viewChild — let’s do it!</p><h3>Using viewChild and Template Reference Variable</h3><p>The new approach uses the @ViewChild decorator and template reference variables. In the new scenario, we create the template reference variable for the teams dropdown using #teams and listen for the (change) event. However, the method onSelecteddoesn’t require passing the value with a slight change.</p><p>The HTML looks like this:</p><pre>&lt;div class=&quot;col&quot;&gt;<br>&lt;p&gt;You select your team {{ selectedTeam }} using viewChild&lt;/p&gt;<br>	&lt;select #teams (change)=&quot;onSelected()&quot;&gt;<br>		&lt;option default&gt;Pick a team&lt;/option&gt;<br>		&lt;option&gt;Lakers&lt;/option&gt;	<br>		&lt;option&gt;Miami&lt;/option&gt;<br>		&lt;option&gt;Cleveland&lt;/option&gt;<br>	&lt;/select&gt;<br>&lt;/div&gt;</pre><p>In our TypeScript file, add the variable teams, using the decorator @ViewChild with type ElementRef and create the method onSelected() without parameters. But using the reference of teams, we can read the value of the reference of teams and assign it to the variable.</p><p>The code will look like this:</p><pre>import { Component, ElementRef, ViewChild } from &#39;@angular/core&#39;;<br>@Component({<br>	selector: &#39;app-team-using-view-child&#39;,<br>	templateUrl: &#39;./team-using-view-child.component.html&#39;,<br>	styleUrls: [&#39;./team-using-view-child.component.css&#39;],<br>})<br>export class TeamUsingViewChildComponent {<br>	@ViewChild(&#39;teams&#39;) teams!: ElementRef;<br>	selectedTeam = &#39;&#39;;<br>	onSelected():void {<br>		this.selectedTeam = this.teams.nativeElement.value;<br>	}<br>}</pre><h3>But How Does It Work?</h3><p>The ElementRef is a wrapper for the DOM HTML element, and the property nativeElement has a reference to the DOM object. Using the @ViewChilddecorator, we get ElementRef in the component class.</p><blockquote><em>Feel free to read more about the </em><a href="https://angular.io/api/core/ViewChild"><em>ViewChild decorator</em></a><em> and </em><a href="https://angular.io/api/core/ElementRef#description"><em>ElementRef</em></a><em>.</em></blockquote><h3>Using NgModel Directive</h3><p>Angular has another way to get the selected value in the dropdown using the power of ngModel and two-way data binding.</p><p>The ngModel is part of the forms module. We need to import it into the NgModule list in the app.module, which will be available in our app.</p><p>The ngModel directive helps us listen and update variables when the event changes trigger, and to use it, add the ngModel using [(ngModel)]=&quot;selectedTeam&quot;.</p><p>Angular automatically gets the value and updates the variable selectedTeam using the ngModel approach when the user changes the value. We don’t need to create the onSelected method in our TypeScript file.</p><pre>&lt;div class=&quot;col&quot;&gt;<br>&lt;p&gt;You select your team {{ selectedTeam }}&lt;/p&gt;<br>&lt;p&gt;The change Event&lt;/p&gt;<br>	&lt;select [(ngModel)]=&quot;selectedTeam&quot;&gt;<br>		&lt;option default&gt;Pick a team&lt;/option&gt;<br>		&lt;option&gt;Lakers&lt;/option&gt;<br>		&lt;option&gt;Miami&lt;/option&gt;<br>		&lt;option&gt;Cleveland&lt;/option&gt;<br>	&lt;/select&gt;<br>&lt;/div&gt;</pre><p>How Does It Work?</p><p>First, the ngModel directive uses the ControlValueAccessor, because Angular provides access to all HTML form elements like input, select and checkbox by default. It sends the value, and the two-way data binding creates the link between the value and the variable.</p><p><em>If you want to read more:</em></p><ul><li><a href="https://angular.io/api/forms/NgModel">NgModel</a></li><li><a href="https://angular.io/guide/two-way-binding#how-two-way-binding-works">Two-way data binding</a></li><li><a href="https://angular.io/api/forms/SelectControlValueAccessor">SelectControlValue</a></li><li><a href="https://angular.io/api/forms/ControlValueAccessor">ControlValueAccessor</a></li></ul><h3>Conclusion</h3><p>We built three different ways to work with dropdowns in our apps. You can find a full code example for this article and play with the example app in the following links:</p><ul><li><a href="https://github.com/danywalls/dropdowns-in-angular">GitHub repo</a></li><li><a href="https://stackblitz.com/edit/angular-ivy-mdajjb?file=src/index.html">StackBliz</a></li></ul><p>If you want to save your time and create fast and advanced dropdowns, then I recommend visiting the article about <a href="https://www.telerik.com/blogs/learn-how-to-build-modern-angular-dropdowns-minutes-kendo-ui?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Angular Dropdowns in Minutes with Kendo UI</a> — it shows you how to use <a href="https://www.telerik.com/kendo-angular-ui/components/dropdowns/dropdownlist?utm_campaign=dt_blog_syndication&amp;utm_source=medium&amp;utm_medium=content_syndication">Angular DropDownList in your apps.</a></p><p>Thanks for your time. I hope you can see how many ways there are to work with dropdowns and pick the best for your app.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aad22b1aeda7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/progress-telerik-kendo-ui/angular-basics-how-to-get-the-value-of-a-selected-dropdown-menu-item-aad22b1aeda7">Angular Basics: How To Get the Value of a Selected Dropdown Menu Item</a> was originally published in <a href="https://medium.com/progress-telerik-kendo-ui">Progress Telerik &amp; Kendo UI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>