Introducing Entity Framework Core (Part 2)

By Ashwin Venugopal -

 





Creating The Database Context

The Database Context is the class from which we will access the database. This is how we create one:

  • Right-click on the MyBlog.Data project and select Add | Class. Name the class MyBlogDBContext.cs.

  • Open the new MyBlogDBContext.cs file and replace the content with a code.

This file contains two classes- MyBlogDbContext and MyBlogDbContextFactory. MyBlogDbContext serves as the DbContext for our database, allowing us to interact with it. The second class, MyBlogDbContextFactory, is intended for setting up our database during the migration process; it consists of code that executes exclusively when we are performing migrations, not during production.

Creating A Migration

A migration is a code snippet used for configuring the database, which encompasses the creation of the database and the establishment or modification of tables. We can do this from within Visual Studio:

  • Start PowerShell and navigate to our MyBlog.Data folder.

  • If this is the first time we start PowerShell, we might need to launch it as an administrator and run the following command- Set -ExecutionPolicy -ExecutionPolicy Unrestricted -Scope LocalMachine

  • To install the Entity Framework tools run the following command- dotnet tool install --global dotnet-ef

  • Now it is time to create our migration. A migration contains the differences between the database now and the changes we have done in our model classes and our MyBlogDbContext.

  • To create a migration run the following command- dotnet ef migrations add InitialDatabaseMigration

We can also use the Package Manager Console inside Visual Studio to do run these commands.

Creating An Interface

As we are presently utilizing Blazor Server, we have the ability to connect directly to the database, meaning that the API we are developing will establish a direct link to the database:

  • Right-click in the Interfaces folder and select Add | Class.

  • In the list of different templates, select Interface and name it IMyBlogApi.cs.

  • Open IMyBlogApi.cs and replace its content with a code.

The interface contains all the methods we need to get, save, and delete blog posts, tags, and categories.

Conclusion

Some more steps to create a database project using Entity Framework are discussed above.































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