The SlowCheetah NuGet package uses the MSBuild API to directly modify
the MSBuild project file stored in memory in MSBuild's
GlobalProjectCollection. It adds properties that contain special
MSBuild characters, for example $( ). When SharpDevelop was merging
these new properties back into the project file on disk it was using
MSBuild to encode them so the wrong values were added. Now the
property values are not encoded.
Ignore all project item types apart from None and TypeScriptCompile.
This fixes the startup exception when opening SharpDevelop.Tests.sln
with SharpDevelop when the TypeScript addin is enabled.
System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at ICSharpCode.TypeScriptBinding.Hosting.TypeScriptContextProvider.AddFileToProjectContext(TypeScriptContext context, FileName fileName)
at ICSharpCode.TypeScriptBinding.Hosting.TypeScriptContextProvider.CreateProjectContext(TypeScriptProject project)
at ICSharpCode.TypeScriptBinding.TypeScriptProjectMonitor.CreateTypeScriptContextIfProjectHasTypeScriptFiles(IProject project)
at ICSharpCode.TypeScriptBinding.TypeScriptProjectMonitor.SolutionLoaded(Object sender, SolutionEventArgs e)
Keyboard shortcuts assigned to the file tab strip menu's items
(/SharpDevelop/Workbench/OpenFileTab/ContextMenu) were ignored
because InputBindingOwner was not set in MenuCreateContext while
creating these menu items. As a result the MenuCommand's
AddGestureToInputBindingOwner method refused to register any
keyboard shortcuts assigned to these menu items.
Make AvalonWorkbenchWindow register itself as InputBindingOwner in
MenuCreateContext when creating the file tab strip menu items and
hence make shortcuts assigned to them work.
And make "Alt-Shift-L" the default shortcut for the NavigateToFileInProjectBrowser menu command.
Cherry picked from pull request #729
If there is an exception finding init.ps1 files when the solution is
opened then the unhandled exception dialog is shown. This can happen
if a NuGet package requires NuGet 3.0. This results in an
NuGetVersionNotSatisfiedException being thrown. Now when this happens
the error message is reported in the PowerShell console if it is open.
When using test data source, where some data fails, following item
that is successful, overwrites "red" status to "green" again in the
Unit Tests window.
This is a workaround. Ideally SharpDevelop would have proper support
for test cases, such as showing them in the Unit Tests window and
being able to run individual test cases.
Fixes#726
Fixes the following issue with code completion.
class Foo
{
public void Bar() {}
}
var foo = new Foo();
foo.
^ Pressing Ctrl+Space here makes the code completion window show
itself. The completions list contains the type names from the 'global'
scope whereas it should contain only the list of Foo's members.
Cherry-picked from pull request #730
Do not register code actions and code issues that are disabled in
NRefactory.
Temporarily disable the CSharpFormattingTests.EnterInsideString test
which is broken due to a change in AvalonEdit.
Xelwon
Xelwon
Kentaro Inomata
NikhilMTomy
Matt Ward
Rinat Hafizov
Daniel Grunwald
Christoph Wille
jogibear9988
Márcio Fábio Althmann
nik
devgopher
ddur
Peter Forstmeier
13.beta2