| Age | Commit message (Collapse) | Author |
|---|
|
* pad-call-stack
* pad-locals
* pad-threads
* pad-watch
See https://github.com/xamarin/icons/issues/158
|
|
|
|
|
|
|
|
|
|
The NuGet addin no longer uses the DispatcherService to run package
actions in the background. It now uses its own background thread to
queue and run these actions.
Due to being unable to use the original DispatcherService's
BackgroundDispatchAndWait without locking up the UI the
PackageManagementProjectOperations.InstallPackages has been changed
to return when the package install has started. Previously it would
wait until the packages were finished installing.
Also the PackageManagementProjectOperations.GetIstalledPackages now
returns installed packages as well as those being installed. This
prevents a Xamarin Component that installs a NuGet package from
showing an error when it is installed. Unfortunately one side effect
of this change is that if the NuGet package fails to install the
Component does not show an error icon when previously it did since
originally the packages were installed and then the list of packages
was checked. Now this happens whilst the packages are being installed.
|
|
|
|
|
|
Most of the DispatchService functionality has been superseeded by async api
and by methods in MonoDevelop.Core.Runtime.
|
|
Fixed bug #36918 - NuGet addin saves project after each change it makes
https://bugzilla.xamarin.com/show_bug.cgi?id=36918
The NuGet addin saves the project each time NuGet modifies the project.
This results in the "Saving..." message to briefly appear in the status
bar and causes the status bar message to appear to blink on and off.
To prevent the status bar message changing a different progress monitor
is now used when saving the project. This progress monitor does not
show the Saving message so the status bar does not appear to blink on
and off.
The NuGet addin still saves the project more often than it needs to.
The original implementation was based on how Visual Studio works, which
saves the project on adding a reference, adding an import or removing
an import. However saving the project once at the end may be a
performance improvement that can be looked at in the future.
|
|
load last autosaved version)
|
|
|
|
[CSharpBinding] Fixing NRE exception found while debugging other stuff
|
|
Bug 36299 - Popup window asking GitHub credentials opens several times.
|
|
This adds a mechanism that disables the comboboxes until history is
available. It sets the text of the comboboxes to Loading... and the
boxes to be insensitive, then switches back to normal behaviour when it
finishes loading.
|
|
|
|
|
|
This fixes the TFS connection heuristics to not cycle indefinitely if
the endpoint is not reachable. This fixes cloning private repositories
over https from github.
Bug 36760 - Cannot Checkout Git Repo
|
|
* Find Next
* Start Debugging
* Debug Current Project
* Go To Line
* Run Unit Tests
* VCS: Update
* VCS: Push
* Solution Options
* Project Options
* New File
* New Workspace
* Revert File
* 1 Column
* 2 Columns
* Open Log Directory
* Check for Updates
* Find Previous
* Find Next
* Jump to File
* Navigate To
* Go To Matching Brace
|
|
* Create Package
* Save As
* Tip of the Day
* Find in Files
|
|
|
|
|
|
Bug 36871 - [Roslyn]: Getting fatal error "A fatal error has occurred"
when Pressing to 'cmd' + '.' buttons.
|
|
Focus the searchbar whenever setting the category, to fix a bug with input on Windows.
Select the search text on focus as per 36765.
Send activated event to controller.
Bug 36765 - Windows toolbar - previous search text not selected when unified search text box gets focus
|
|
The searchbar (and possibly any other text box for that matter) needs to
force the gtk window to Present itself. This caused a weird issue on the
initial focus set that caused the window to reset its allocation.
Bug 36755 - Unable to start Xamarin Studio maximized
|
|
Change the namespace from ICSharpCode.PackageManagement to
MonoDevelop.PackageManagement
|
|
|
|
Older versions of RefactoringEssentials provided the action but it got
removed because of duplicates in VS.NET.
Now we're using the same action than VS.NET for that operation.
|
|
|
|
|
|
Fixed bug #33774 - Handle Windows scale factor in ASP.NET wizard
dialog
https://bugzilla.xamarin.com/show_bug.cgi?id=33774
Widgets should now be scaled based on the Windows scale factor.
There are still some alignment problems with the labels and the radio
buttons and check boxes when the scale factor is 1.5.
|
|
|
|
|
|
|
|
the file is closed and opened again.'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
option.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
