1. 27 11月, 2018 1 次提交
  2. 25 11月, 2018 2 次提交
  3. 31 3月, 2017 2 次提交
  4. 13 5月, 2015 1 次提交
    • J
      Get rid of Roslyn.VisualStudio.Setup as a shipping assembly · 915f8d45
      Jason Malinowski 提交于
      The RoslynPackage type originally lived in a seperate assembly than
      Microsoft.VisualStudio.LanguageServices when it was important for us
      to be able to support the core parts of Roslyn being installed atop
      the existing Visual Studio 2013 language services. This is no longer
      a supported scenario anywhere, so we should just get rid of the
      assembly.
      
      Doing this is easy, it's just a matter of moving the files and related
      assets to the LanguageServices assembly. A MEF interface is added
      to prevent a circularity around triggering a load of stuff in the
      SolutionExplorerShim. That could be delt with later by moving the core
      of that code back to LanguageServices, but I don't want to touch that
      now since it's very sensitive.
      915f8d45
  5. 06 5月, 2015 1 次提交
  6. 14 2月, 2015 1 次提交
    • B
      Move VisualStudioSetup into the open · da85b6e0
      beep boop 提交于
      This change moves the contents of VisualStudioSetup into the open,
      merging with (and consuming) VisualStudioComponents. The Components/
      Setup split originally existed as a way to allow multiple Roslyn-using
      components to have a single source of truth of the MEF exports. This
      meant you could have either the interactive window, language services,
      or both installed and everything worked. This was important when we
      were atop Visual Studio 2013, but now that we're integrated it's buying
      us nothing.
      
      The VSIX ID from VisualStudioComponents is preserved so that way any
      extensions that declared a dependency on it will still work.
      da85b6e0
  7. 06 2月, 2015 1 次提交
  8. 14 1月, 2015 1 次提交
  9. 02 7月, 2014 1 次提交
    • T
      More robust command line compiler testing · e863aad6
      TomasMatousek 提交于
      Previously the command line tests were looking in various directories for csc.exe/vbc.exe. Instead, add a reference to csc/vbc project to the command line unit test assembly, so that we always test what we build and not depend on directories outside of Roslyn.
      To make it easy to test the default .rsp file this change links it into the command line unit test project and includes it to resources. The tests then extract the .rsp from the resources and save it to a temp file for testing.
       (changeset 1285693)
      e863aad6
  10. 20 6月, 2014 1 次提交
    • T
      Splits Microsoft.CodeAnalysis, Microsoft.CodeAnalysis.CSharp and... · fc3b332f
      TomasMatousek 提交于
      Splits Microsoft.CodeAnalysis, Microsoft.CodeAnalysis.CSharp and Microsoft.CodeAnalysis.VisualBasic into portable and desktop assemblies.
      
      Existing Core\Source, CSharp\Source and VisualBasic\Source directories are renamed to Core\Portable, CSharp\Portable and VisualBasic\Portable.
      New sibling Desktop folders are added and non-portable source is moved there.
      "System.Runtime" references has to be removed in order for the portable project system magic to automatically add facade references.
       (changeset 1281686)
      fc3b332f
  11. 19 3月, 2014 1 次提交