Update Rule “write-integration-test-for-dependencies/rule” (#7189)

rules/write-integration-test-for-dependencies/rule.md

@@ -1,17 +1,16 @@
 ---
 type: rule
-archivedreason: We now use NuGet to manage dependencies
 title: Do you write Integration Test for Dependencies - e.g. DLLs?
-guid: 62615da5-6ce6-4f6d-b236-88cc2c918f93
 uri: write-integration-test-for-dependencies
-created: 2020-03-11T21:59:13.0000000Z
 authors:
-- title: Adam Cogan
-  url: https://ssw.com.au/people/adam-cogan
+  - title: Adam Cogan
+    url: https://ssw.com.au/people/adam-cogan
 related: []
 redirects:
-- do-you-write-integration-test-for-dependencies-e-g-dlls
-
+  - do-you-write-integration-test-for-dependencies-e-g-dlls
+created: 2020-03-11T21:59:13.000Z
+archivedreason: We now use NuGet to manage dependencies
+guid: 62615da5-6ce6-4f6d-b236-88cc2c918f93
 ---
 
 Dependant code is code that relies on other factors like methods and classes inside a separate DLL. Because of the way the .NET works assemblies are loaded as required by the program (this is what we call the JIT compiler). Thus, when a DLL goes astray, you will only find out at run time when you run a form/function that uses that DLL. These run time errors can occur when you have not packaged DLLs in your release or if the versions are incompatible. Such errors cause the following exceptions:
@@ -28,7 +27,7 @@ Sample code:
 
 
 
-```
+```cs
 [Test]
 public void ReferencedAssembliesTest()
 {