Understanding Basic Blazor Components

By Ashwin Venugopal -

 





Exploring Components

In Blazor, a component refers to a .razor file that may encapsulate a specific, self-contained functionality (including both code and markup) or may serve as a standalone page. Additionally, a component has the capability to contain other components.

There are three different ways we can create a component:

  • Using Razor syntax, with code and HTML sharing the same file

  • Using a code-behind file together with a .razor file

  • Using only a code-behind file

Counter

The counter page displays a button and a counter, where pressing the button increments the counter. At the top of the page, the @page directive enables direct routing to the component. By running the MyBlogServerSide project and add/counter to the URL, we can access the component directly via its route. The implementation of the counter component is consistent for both Blazor WebAssembly and Blazor Server. In contrast, the FetchData component has two distinct implementations since the Blazor Server project can connect directly to server data, whereas Blazor WebAssembly must access it through a web API. We apply the same methodology with our API, allowing us to understand how to utilize Dependency Injection (DI) and directly connect to a database when using Blazor Server.

FetchData

The FetchData component can be found in the Pages/FetchData.razor directory. The core implementation of the FetchData component is similar for both Blazor WebAssembly and Blazor Server. However, the initial lines of the files and the method of retrieving data vary between the two versions. It establishes a route, includes a namespace, and injects a service. This service is located in the Data folder of the MyBlogServerSide project.

Conclusion

Some of the components that comes with Blazor template are explored.

















Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Deployment (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 3, please click  here Microsoft Sentinel Content Hub Content in Microsoft Sentinel includes any of the following types: Data connectors offer log ingestion from different sources into Microsoft Sentinel. Parsers give log formatting/transformation into ASIM formats, supporting usage across various Microsoft Sentinel content types and scenarios. Workbooks provide monitoring, visualization, and interactively with data in Microsoft Sentinel, highlighting meaningful insights for users.  Analytics rules give alerts that point to relevant SOC actions via incidents.  Hunting Queries are used by SOC teams to proactively hunt for threats in Microsoft Sentinel. Notebooks help SOC teams in using advanced hunting features in Jupyter and Azure Notebooks. Watchlists support the ingestion of specific data for enhanced threat detection and reduced alert fatigue.  Playbooks and Azure Logic Apps Custom Connectors provide featu...
Read more