title: How to see source code from github in Visual Studio IDE, but compile with dlls from Nuget?
body: <p>Nowadays there's a lot of great open source packages and frameworks for all sorts of uses. Let's take for example, ASP.NET Core MVC and Newtonsoft.Json.
  Those are shipped in Nuget packages, which are stripped of the source code.
  I think many of you can remember a lot of situations in which one would like to see the source code freely available on GitHub (to help debugguing some issue), but was forced to do one of the following:</p>
  
  <ol>
  <li>Be lazy and just forget about it, or continue debugging your issue with a popular library treating it more like a "black box";</li>
  <li>Go to the browser, type github.com and search the source code without the mighty advises of the Visual Studio IDE;</li>
  <li>Spend 5 minutes, clone the repository to the local drive and look at it with IDE;</li>
  <li>Spend even more time while compiling the source code, deinstalling all of the nuget packages of interest from your projects and instead, hooking up directly to all of the freshly compiled assemblies (which are not always one-to-one to Nuget package).</li>
  </ol>
  
  <p>This last option is the most viable, but you're left with a lot of time spent and you can't just push this to your repository or deploy the compiled code anymore. Other developers won't find those relative paths to the dlls and customers may end up with wrong versions of nuget packages baked in the deployment package.</p>
  
  <p>Is there a fifth option which has all the pros of the fourth, but none of the cons? I imagine this being done by an IDE in an isolated fasion, i.e. no modification to my .csproj and package.config files, but the "Go to definition" &amp; "Find all references" features and debugging should work as if I'm hooked up to the real stuff. </p>
  
  <p>Yes, I'm pretty lazy.</p>