diff --git a/Daniel15.Web/Posts/2015-08-01-entity-framework-6-mysql-aspnet.md b/Daniel15.Web/Posts/2015-08-01-entity-framework-6-mysql-aspnet.md index 91d3f49..cfe478f 100644 --- a/Daniel15.Web/Posts/2015-08-01-entity-framework-6-mysql-aspnet.md +++ b/Daniel15.Web/Posts/2015-08-01-entity-framework-6-mysql-aspnet.md @@ -67,7 +67,7 @@ public class MyDbConfiguration : DbConfiguration The first part of the configuration is a hack to register the ADO.NET provider at runtime, by dynamically adding a new configuration entry to the `system.data` section. The second part registers the Entity Framework provider. We also need to modify the configuration file to include the connection string. You can use any configuration provider supported by ASP.NET 5, I'm using `config.json` here because it's the default provider. -```js +```json { "Data": { "DefaultConnection": { diff --git a/Daniel15.Web/Posts/2017-05-10-fixing-msb3552-resource-file-resx-cannot-be-found.md b/Daniel15.Web/Posts/2017-05-10-fixing-msb3552-resource-file-resx-cannot-be-found.md index 19daa5e..5299086 100644 --- a/Daniel15.Web/Posts/2017-05-10-fixing-msb3552-resource-file-resx-cannot-be-found.md +++ b/Daniel15.Web/Posts/2017-05-10-fixing-msb3552-resource-file-resx-cannot-be-found.md @@ -22,7 +22,7 @@ Microsoft.Common.CurrentVersion.targets(2867,5): error MSB3552: Resource file "* It turns out this is caused by a long-standing MSBuild bug: [Wildcard expansion is silently disabled when a wildcard includes a file over MAX_PATH](https://github.com/Microsoft/msbuild/issues/406){rel=nofollow}. The `Microsoft.NET.Sdk.DefaultItems.props` file bundled with .NET Core includes a section that looks like this: -``` +```xml