Add warnings/explanations about Nfluent projects, files and T4 templa…

…te generation.

CONTRIBUTING.md

@@ -27,7 +27,13 @@ You should **never** work on a clone of master, and you should **never** send a
 
 Before adding code
 ------------------
-Don't forget to install the __[Project Linker Visual Studio Add-in](https://visualstudiogallery.msdn.microsoft.com/7c36d531-4464-479b-934b-bbe71e621528)__ so that NFluent35 and NFluent 40 projects (same for tests) contain the same elements (adding all your new types in the *35 projects by default if possible, and letting the plugin to add links in the *40 version).
+ - Don't forget to install the __[Project Linker Visual Studio Add-in](https://visualstudiogallery.msdn.microsoft.com/7c36d531-4464-479b-934b-bbe71e621528)__ so that NFluent35 and NFluent 40 projects (same for tests) contain the same elements (adding all your new types in the *35 projects by default if possible, and letting the plugin to add links in the *40 version).
+
+#### WARNING: (almost) all files are now located within the NFluent.Core project, and the other projects embed file aliases
+
+__Since T4 template aren't supported for dotnet core projects, we've setup a hack that allow T4 template to be generated from the T4 located within the NFluent.35 project (which generates files within the proper dotnet core project target location)__
+
+---
 
 Handling Updates from Upstream/Master
 -------------------------------------