- 19 4月, 2016 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 06 4月, 2016 1 次提交
-
-
由 Jason Malinowski 提交于
-
- 05 4月, 2016 1 次提交
-
-
由 Jason Malinowski 提交于
Back in 84d7856e, I updated our targets to always include all dependencies from NuGet packages in our VSIXes. This was quick, but had a few problems: 1. we would force-include everything, including VS SDK assemblies 2. we would include the same assembly in multiple VSIXes, even when we really didn't need them. This is mostly a change to address the former. Now you have to explicitly state which NuGet packages you do want to bring in, and only those will get brought in to your VSIX. The rest are excluded.
-
- 25 3月, 2016 1 次提交
-
-
由 Jason Malinowski 提交于
For the Shell binary, we have two choices. We could either reference the version that matches the version of Visual Studio you are building with, or we could reference a fixed version with a HintPath so we can find the binary on all versions of Visual Studio. Doing the former is tricky since the name of the assembly is embedded into some XAML, so I go with the latter option.
-
- 12 11月, 2015 1 次提交
-
-
由 Jason Malinowski 提交于
-
- 16 10月, 2015 1 次提交
-
-
由 Paul Harrington 提交于
-
- 22 9月, 2015 1 次提交
-
-
由 Tanner Gooding 提交于
* This updates all references to nuget.exe to use the copy in the root. * This deletes all NuGet.config and NuGet.exe files that are not in the root. * This removes all references to NuGet.targets (which is obsolete and no longer exists)
-
- 09 9月, 2015 1 次提交
-
-
由 Kevin Halverson 提交于
...to include nuget references in the output VSIX. This was broken with the migration to project.json, because we no longer have a way to specify <ForceIncludeInVSIX>true</ForceIncludeInVSIX> for nuget references.
-
- 03 9月, 2015 1 次提交
-
-
由 Andy Gocke 提交于
-
- 27 8月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 26 8月, 2015 1 次提交
-
-
由 Dustin Campbell 提交于
-
- 29 7月, 2015 2 次提交
-
-
由 Kevin Halverson 提交于
My wild guess as to why the Workspaces dlls aren't signed in the Interactive VSIX is that they're not marked "ForceIncludeInVSIX=true" (as most of the other references are).
-
由 Kevin Halverson 提交于
...in Roslyn.VisualStudio.InteractiveComponents.vsix.
-
- 16 7月, 2015 1 次提交
-
-
由 Kevin Halverson 提交于
This is preliminary work for Interactive setup authoring. - Fix versions of InteractiveWindow and VsInteractiveWindow at 1.0.0.0 so as not to break existing consumers (e.g. Python Tools). - Redirect consumers of the VsInteractiveWindow to 42.42.42.42 in the RoslynDev hive. - Delete some unused Debugger stuff from VisualStudioInteractiveServices. - RootNamespace and AssemblyName should match TargetVsixContainerName to avoid confusion. - Don't deploy an extra copy of Microsoft.CodeAnalysis.VisualBasic.dll with Roslyn.VisualStudio.Setup.Interactive.vsix.
-
- 09 7月, 2015 1 次提交
-
-
由 Andy Gocke 提交于
The targets files were previously split into an open version in Microsoft.CodeAnalysis.Toolset.Open and a closed version in build/. This unifies the four targets into two new targets, VSL.Settings.targets and VSL.Imports.targets, and moves all the targets from ..Toolset.Open into the build/ folder.
-
- 30 6月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 27 6月, 2015 1 次提交
-
-
由 Kevin Halverson 提交于
The VsSdk changed to specifically exclude System.Collections.Immutable and System.Reflection.Metadata from the output vsix so we'll have to mark them <ForceIncludeInVSIX>true</ForceIncludeInVSIX>. (fixes #3687)
-
- 24 6月, 2015 1 次提交
-
-
由 Andrew Casey 提交于
It doesn't make sense to have both ReferenceOutputAssembly=false and IncludeOutputGroupsInVSIX=BuildProjectOutputGroup. (The upshot is that the affected references end up in the VSIX unsigned.)
-
- 18 6月, 2015 1 次提交
-
-
由 Andrew Casey 提交于
Recently, a change was made to exclude assemblies that are part of Visual Studio from all VSIXes. However, VSIXes that are to be included obviously need to be able to include such assemblies, so we use the new ForceIncludeInVsix element to override the filtering.
-
- 16 6月, 2015 1 次提交
-
-
由 Charles Stoner 提交于
-
- 15 5月, 2015 1 次提交
-
-
由 Jared Parsons 提交于
This deletes the empty and unused Desktop assemblies from the code base.
-
- 30 4月, 2015 1 次提交
-
-
由 Andrew Casey 提交于
-
- 29 4月, 2015 3 次提交
-
-
由 Andrew Casey 提交于
-
由 Andrew Casey 提交于
This reverts commit 8cfc284c.
-
由 Andrew Casey 提交于
This reverts commit 0eba2636.
-
- 28 4月, 2015 1 次提交
-
-
由 Andrew Casey 提交于
-
- 28 3月, 2015 1 次提交
-
-
由 Paul Harrington 提交于
-
- 27 3月, 2015 1 次提交
-
-
由 Paul Harrington 提交于
-
- 26 3月, 2015 1 次提交
-
-
由 Kevin Halverson 提交于
These extra properties should cause only the build outputs of the directly referenced projects to be included in the vsix(es). (fixes #578)
-
- 14 2月, 2015 1 次提交
-
-
由 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.
-
- 01 2月, 2015 1 次提交
-
-
由 beep boop 提交于
-