| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
From 2012 onwards, the solution format is unchanged, so there's
no need to define a 2017 format.
The ToolsVersion defined by the format is irrelevant except to new
project creation with the old template system. The build engine
will always be the latest MSBuild version.
Change the comment added to new files to match VS2017.
|
|
keyboard shortcut multiple times
https://devdiv.visualstudio.com/DevDiv/_workitems/edit/591324
This method isn't called anywhere else.
|
|
Fixes issue #4393 Error in text editor The original error should be
|
|
[Ide] Switched to roslyn folding infrastructure.
|
|
Fixes VSTS #591651 - Project model evaluation contention
|
|
|
|
|
|
This reduces lock contention happening when evaluating a with conditions
|
|
This reduces lock contention on imported files by not locking on the
global project info dictionary when accessing it, instead locking on
each project info.
This should help with concurrent imports of different imported files
|
|
|
|
Removes the need for locking on getting the variables. Also, should reduce pressure and grab everything in one go.
|
|
finding
|
|
Avoid enumerator boxing and avoid allocating a string for all the property imports
|
|
|
|
|
|
[master] Fix 594883: Goto Declaration is not available when creating an Android project
|
|
[master] Fix 597220: No IntelliSense for pages deriving from a custom ContentPage
|
|
[master] Fix 591345: [Updater] \u0022Updates have been downloaded and are ready to …
|
|
|
|
Fixes #4224. Missing binding redirects
|
|
be set via environment variable `VS_UPDATER_SERVICE_URL`. Real fix is not in `.Equals()` using `Id` to compare instead of `Idx`, but since some sorting still depends on Idx, I'm keeping .Idx fix for standard channels.
|
|
install" still shown after updating to Alpha Problem was with changes around MonoDevelop.Ide.AddinUpdater.UpdateChannel/UpdateLevel migration where `idx` was not set for each channel resulting in UpdateChannel.Equals returning wrong values causing https://github.com/xamarin/md-addins/blob/5b4c8d9/Xamarin.Ide/Xamarin.Ide/Xamarin.Ide.Updater/UpdatesDialog.cs#L278 to not execute and update list of updatable items.
|
|
project Main fix for this bug is in `LoadProject` method, problem was that if multiple calls to `LoadProject` were made, 1st call called `GetProjectData` and `CreateProjectData` and when second call called `GetProjectData` to set `oldProjectData` it was empty because 1st call didn't call `CreateDocuments` yet, resulting in `documentIdMap` being empty, hence documentIds were totally different after project reload, causing issues with GoToDefinition command... While working on this I also noticed that OnProjectModified is called ~10 times when restoring NuGets for Android project and none of this is canceled, in theory it could happen that older version finishes after latest version and cause project references list to be outdated, hence I added logic to cancel old requests...
|
|
This is just MonoDevelop part of fix, what I did here is update XmlName/Root and Tag states to support having `< xmlns="formsNamespace"` and parse this as element with attributes, because until now this was not element element yet(because it doesn't have name) so attributes also were not parsed, resulting in Forms extension not being aware of referenced namespaces, hence code completion not working...
I included also 2 unrelated fixes in SourceEditorView.cs and SimpleBracketMatcher.cs which deal with file edge cases that I found while working on this.
|
|
Fixes VSTS 597271: [Feedback] Getting "The type initializer for
|
|
already fixed (the line numbers indicate it). However the text editor
errors should be printed to the log and not the console. This had
historical reasons because the editor was stand alone and had no
connection to the Core/Ide and no own logging capabilities.
|
|
|
|
mono/msbuild-items-added-for-globs-with-link-metadata
[Core] Fix MSBuild items added for globs with link metadata
|
|
[Core] Remove per-project MSBuild opt-out
|
|
There is no reason to do this any more, it just opens
up a way to break things.
|
|
No need to evaluate the MSBuild item property since the evaluated
property can be matched when the unevaluated property contains
'%' characters.
This is a re-work of the fix for VSTS #569295 - Projects that
includes files using wildcards will expand (and remove) wildcards
upon save
|
|
A project containing the following MSBuild file globs would have
extra MSBuild items added when the project file was saved.
<ItemGroup>
<Compile Include="..\**\*.cs">
<Link>%(RecursiveDir)%(Filename)%(Extension)</Link>
</Compile>
</ItemGroup>
On saving the project Compile Update items would be added for each
file included by the file glob.
<ItemGroup>
<Compile Update="..\Test\Class1.cs">
<Link>Class1.cs</Link>
</Compile>
</ItemGroup>
Fixes VSTS #527721 - Overriding globs
|
|
[529478][Editor] Fix search marker fallback color with final colors
|
|
[Core] Support facade assemblies from a custom location
|
|
|
|
[529478][Editor] Fix search marker fallback color
|
|
'Mono.TextEditor.TextViewMargin' threw an exception." errors from VS
Community (Mac) on macOS 10.13.5 Beta
https://devdiv.visualstudio.com/DevDiv/_workitems/edit/597271
Seems to be a bug in the macOS beta but it can be handled.
|
|
Added a OnGetFacadeAssemblies method to the DotNetProjectExtension
that allows a project extension to provide the facade assemblies
for a project if the default behaviour does not work for the project.
This can be used by the Xamarin.Mac project extension to provide
the facade assemblies when the project uses Xamarin.Mac full. A
Xamarin.Mac full project will use a custom facades directory at
build time but the project has a target framework of .NET Framework
so the default facades assembly resolution logic will return the
wrong facade assemblies that are included with Mono.
|
|
tests for it.
|
|
|
|
Setting the search result marker color value to #f3da2d.
|
|
Use a default visible fallback color for search markers,
if the default highlight color is not bright enough.
|
|
|
|
mono/xamarin-forms-use-dotnet-templating-project-templates
[Forms] Use dotnet templating project templates
|
|
|
|
|
|
|
|
|
