X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=README.md;h=52580fdb4232acb157abd620aa3945e85829747e;hb=3ca530a8bdedfb8d1c50585a5e8a7bb8f3d7b5ea;hp=5aad9440a06112eb34bb89a82f8bd46fb2910640;hpb=1639e26a6b22a59d0bfb8ad564530eeff593e4a3;p=mono.git

diff --git a/README.md b/README.md
index 5aad9440a06..52580fdb423 100644
--- a/README.md
+++ b/README.md
@@ -517,7 +517,24 @@ See the LICENSE file for licensing information, and the PATENTS.TXT
 file for information about Microsoft's patent grant.
 
 Mono Trademark Use Policy
-=======
+=========================
 
 The use of trademarks and logos for Mono can be found [here] (http://www.dotnetfoundation.org/legal/mono-tm). 
 
+Maintaining the Class Library Solution Files
+============================================
+
+Mono now ships with a solution file that can be used to build the
+assemblies from an IDE.  Either by opening the topmost `net_4_x.sln`
+file, or to by loading one of the individual `csproj` files located in
+each directory.
+
+These are maintained by extracting the configuration information from
+our Makefiles, which as of May 2016 remain the canonical location for
+configuration information.
+
+When changes are made to the Makefiles, a user would need to run the
+following command to re-generate the solution files at the top level:
+
+	$ make update-solution-files
+