In a previous post we looked at dependency injection within Blazor. One of the services available by default is an implementation of IConfiguration, hence to inject the configuration object we do the following<\/p>\n
\r\n@inject IConfiguration Configuration\r\n<\/pre>\nand we can interact with the configuration using a key, i.e.<\/p>\n
\r\n@Configuration["SomeKey"]\r\n<\/pre>\nFor Blazor on the server we can simply add the key\/value to the appsettings.json file, like this<\/p>\n
\r\n"SomeKey": "Hello World" \r\n<\/pre>\nBy default Blazor WebAssembly does not come with an appsettings.json, so you’ll need to add one yourself. This file will need to be in the wwwroot folder as these files will be deployed at part of your client.<\/p>\n
You can put sensitive data in the server appsettings.json because it’s hosted on the server, do not put sensitive information in the appsettings.json for a WebAssembly\/client<\/strong> otherwise this will be downloaded to the user’s machine.<\/p>\n
If you want to store more complicated data in the appsettings.json, for example a JSON object, you’ll need to create a class that looks like the data, for example if your appsettings.json had the following<\/p>\n
\r\n"Person": {\r\n "FirstName": "Scooby",\r\n "LastName": "Doo"\r\n} \r\n<\/pre>\nSo now we’ll need a class to match the structure of the data. The name of the class is not important, the structure is, so here we have<\/p>\n
\r\npublic class MyPerson\r\n{\r\n public string FirstName { get; set; }\r\n public string LastName { get; set; }\r\n}\r\n<\/pre>\nNow to access this we need to use <\/p>\n
\r\nConfiguration.GetSection("Person").Get<MyPerson>();\r\n<\/pre>\n