So, you’ve got .NET Core, .NET Standard and .NET Framework. Microsoft, when developing all this, had the brilliant idea to create a set of APIs that should be available on both Framework and Core. A Standard set, if you will. Thus, .NET Standard was born. Libraries targeting this “platform” (which technically is not really a platform) will be available on both .NET Core and .NET Framework. Therefore, whenever you can target .NET Standard when developing a library, you should do so.<\/p>\n
That was the start for me when upgrading our systems to .NET Core: take the internal libraries, transform them to .NET Standard, and tadaa, they can be used immediately in the projects already there. Just put them in your local NuGet server, make sure it references the right packages, and everything solves itself.<\/p>\n
Except when it doesn’t.<\/p>\n
I got the strangest error while updating a newly migrated library in my project to the .NET Standard version in a WebApi project. As expected, some extra dependencies came in that were not necessary first (e.g. System.ComponentModel.Annotations). All was installed and built correctly, but when running and trying to open the Swagger UI page, the following error popped up:<\/p>\n
System.MissingMethodException: 'Method not found: 'System.String\r\nSwashbuckle.Application.SwaggerDocsConfig.DefaultRootUrlResolver(System.Net.Http.HttpRequestMessage)'.'<\/pre>\nNice. A quick search around the internet found me this github issue<\/a>. Cool, so<\/p>\n
\n
- Go to the Error List window in Visual Studio.<\/li>\n
- Find a warning looking like “Found conflict between different versions of the same dependent assembly.”.<\/li>\n
- Double-click the warning. This will show a dialog asking to automatically generate binding redirects.<\/li>\n
- Click “OK” to add the binding redirects to your web.config file.<\/li>\n
- Now you can run again!<\/li>\n<\/ul>\n
Test projects<\/h2>\n
So I was happily updating all references to this package to the version with .NET Standard, expecting all to be good. But no, I got a problem on… my test projects. All tests that actually touch the controllers fail with an exception. Again, the
System.MissingMethodException<\/code>. But when I went looking for the warning message in the Error List, I couldn’t find any. How weird. So, back to the internet it was, where I came upon this github issue<\/a>. Apparently, the trick with automatically generate binding redirects doesn’t work on Library projects, and of course test projects are library projects.<\/p>\nTo make those run as well, do the following:<\/p>\n
\n
- In Visual Studio, “unload” the project (or open the project file in a different text editor).<\/li>\n
- Find the first
<PropertyGroup><\/code> tag.<\/li>\n- Insert the following line of XML at the end of the tag:<\/li>\n<\/ul>\n
\r\n<AutoGenerateBindingRedirects>true<\/AutoGenerateBindingRedirects>\r\n<\/pre>\n\n
- Go to the end of the file where a bunch of
<Target><\/code> tags are defined.<\/li>\n- Insert the following
<Target><\/code> tag:<\/li>\n<\/ul>\n\r\n<Target Name="ForceGenerationOfBindingRedirects"\r\n AfterTargets="ResolveAssemblyReferences"\r\n BeforeTargets="GenerateBindingRedirects"\r\n Condition="'$(AutoGenerateBindingRedirects)' == 'true'">\r\n <PropertyGroup>\r\n <!-- Needs to be set in a target because it has to be set after the initial evaluation in the common targets -->\r\n <GenerateBindingRedirectsOutputType>true<\/GenerateBindingRedirectsOutputType>\r\n <\/PropertyGroup>\r\n<\/Target>\r\n<\/pre>\n\n
- Open\/load the project again in Visual Studio and rebuild.<\/li>\n
- The redirects are generated automatically<\/li>\n<\/ul>\n
All tests were green! So, while using .NET Standard is a great way for gradually migrating your projects, some work still needs to be done before everything works in your .NET Framework projects.<\/p>\n","protected":false},"excerpt":{"rendered":"
So, you’ve got .NET Core, .NET Standard and .NET Framework. Microsoft, when developing all this, had the brilliant idea to create a set of APIs that should be available on both Framework and Core. A Standard set, if you will. Thus, .NET Standard was born. Libraries targeting this “platform” (which technically is not really a…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"twitterCardType":"","cardImageID":0,"cardImage":"","cardTitle":"","cardDesc":"","cardImageAlt":"","cardPlayer":"","cardPlayerWidth":0,"cardPlayerHeight":0,"cardPlayerStream":"","cardPlayerCodec":""},"categories":[6],"tags":[],"_links":{"self":[{"href":"https:\/\/daan.wsng.eu\/index.php\/wp-json\/wp\/v2\/posts\/58"}],"collection":[{"href":"https:\/\/daan.wsng.eu\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/daan.wsng.eu\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/daan.wsng.eu\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/daan.wsng.eu\/index.php\/wp-json\/wp\/v2\/comments?post=58"}],"version-history":[{"count":9,"href":"https:\/\/daan.wsng.eu\/index.php\/wp-json\/wp\/v2\/posts\/58\/revisions"}],"predecessor-version":[{"id":67,"href":"https:\/\/daan.wsng.eu\/index.php\/wp-json\/wp\/v2\/posts\/58\/revisions\/67"}],"wp:attachment":[{"href":"https:\/\/daan.wsng.eu\/index.php\/wp-json\/wp\/v2\/media?parent=58"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/daan.wsng.eu\/index.php\/wp-json\/wp\/v2\/categories?post=58"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/daan.wsng.eu\/index.php\/wp-json\/wp\/v2\/tags?post=58"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}