| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
When generating a PCL assembly from the intersection of project
assemblies the ApiIntersect build task would throw an exception since
it could not resolve the Mono.Android assembly. This problem has been
fixed in a more recent NuGet.Build.Packaging where the failure to
resolve has been converted to a warning.
System.Exception: Could not resolve Mono.Android, Version=0.0.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065
at ApiIntersect.FrameworkAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference name, Mono.Cecil.ReaderParameters parameters) [0x0001b] in <aac3e0d5bcd4473a96e385115da49b96>:0
at ApiIntersect.FrameworkAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference name) [0x00000] in <aac3e0d5bcd4473a96e385115da49b96>:0
at ICSharpCode.Decompiler.Ast.Transforms.IntroduceUsingDeclarations.Run (ICSharpCode.NRefactory.CSharp.AstNode compilationUnit) [0x00142] in <37b5ad8a7a94479fbc5b574a8fc6281a>:0
at ICSharpCode.Decompiler.Ast.Transforms.TransformationPipeline.RunTransformationsUntil (ICSharpCode.NRefactory.CSharp.AstNode node, System.Predicate`1[T] abortCondition, ICSharpCode.Decompiler.DecompilerContext context) [0x0002c] in <37b5ad8a7a94479fbc5b574a8fc6281a>:0
at ICSharpCode.Decompiler.Ast.AstBuilder.RunTransformations (System.Predicate`1[T] transformAbortCondition) [0x00000] in <37b5ad8a7a94479fbc5b574a8fc6281a>:0
at ICSharpCode.Decompiler.Ast.AstBuilder.RunTransformations () [0x00000] in <37b5ad8a7a94479fbc5b574a8fc6281a>:0
at ApiIntersect.MainClass.DumpTypes (System.Collections.Generic.List`1[T] types, System.String baseDir) [0x000a7] in <aac3e0d5bcd4473a96e385115da49b96>:0
at ApiIntersect.MainClass.Process (System.Collections.Generic.List`1[T] intersections, System.Collections.Generic.List`1[T] exclusions, Mono.Cecil.ReaderParameters readerParameters, System.String outputPath) [0x00319] in <aac3e0d5bcd4473a96e385115da49b96>:0
at ApiIntersect.MainClass.Main (System.String[] args) [0x0039f] in <aac3e0d5bcd4473a96e385115da49b96>:0
An updated NuGet.Build.Packaging has not been published to nuget.org
so only new projects will get the fixed version.
Fixes VSTS #635546 - [Nugetizer] Build error using Multiplatform Library
template when Xamarin.Android code is in the Android project
|
|
|
|
|
|
merge-integration-12
|
|
The Copyright NuGet package metadata in project options - NuGet
Package - Metadata was not being read nor written.
Fixes VSTS #807733 - NuGet Copyright metadata not saved
|
|
The Copyright NuGet package metadata in project options - NuGet
Package - Metadata was not being read nor written.
Fixes VSTS #807733 - NuGet Copyright metadata not saved
|
|
|
|
All services are now referenced from the IdeServices class
|
|
|
|
In project options - NuGet Package - Build the check box to enable creation
of a NuGet package at build time will show a warning label if there is no
associated package metadata defined for the project. This warning label was
not being read by voice over when the check box is selected. Now the
accessibility text is updated and includes the warning text if it is applies
so this is now read by voice over when the check box is selected.
Fixes VSTS #753475 - Accessibility: Voice Over is not reading the alert text
revealed after the "Create a NuGet Package" checkbox is checked.
|
|
In project options - NuGet Package - Metadata tabbing through the
UI controls would result in the label text being announced twice.
This was because an accessibility label was being set twice - once
as plain text, and then when associating the label with the main
UI element via a role.
|
|
In project options - NuGet Package - Metadata the language display
name is shown in the language combo box. Previously the language
code (e.g. 'en-GB') was displayed. The display name is more user
friendly and also matches the behaviour of Visual Studio on Windows
when it shows package metadata for .NET Standard projects.
|
|
Tabbing to the language combo box in project options - NuGet Package -
Metadata would not announce the label associated with the combo box
with Voice Over. The problem is that the combo box with an enabled
text entry does not work well with the accessibility library. To
fix this the combo box no longer allows free text entry. If no
language is selected then 'None' is displayed.
Fixes VSTS #753486 - Accessibility: NuGet Package Metadata: Voice
Over is not reading the label of the "Language" combo box.
Fixes VSTS #753489 - Usability: NuGet Package Metadata: Text area
inside the "Language" combo box does not serves any purpose and seems
not to be useful in this scenario.
|
|
The old autotools build infrastructure is largely redundant,
as projects are now built with msbuild. Remove as much as can
be done easily, along with some other obsolete stuff.
|
|
|
|
These tests all output into the same directory, they
should not all be local copying the same references
into it.
|
|
|
|
|
|
Downgrade to NuGet 4.8.0.5385
Fixes VSTS #749807 - Fallback folders not used with ASP.NET Core project
|
|
Update NuGet to version 4.9.0.5658
Fixes VSTS #743959 - Bump VSMac to NuGet 4.8 or later
|
|
Switched to using the NuGet libraries from nuget.org instead of
using those from mono/nuget-binary. Currently the git submodule
remains for nuget-binary since other parts rely on the nuget.exe
that is included in that repository.
Fixes VSTS #672853 - Update to Support NuGet 4.7
|
|
This disables searching in registry, AssemblyFoldersEx, etc.
|
|
[master] Disable failing test: CreateMultiPlatformProjectFromTemplateWithPCLOnly
|
|
|
|
https://github.com/mono/monodevelop/issues/5602 tracks fixing and reenabling.
|
|
The internal ProjectTemplate API now returns a task so the tests
have been updated to await the result.
|
|
The tests seem to work without this and the test project can now
avoid having a local copy of the .NET Core addin assembly.
|
|
|
|
The test was not setting the IncludeInPackage MSBuild metadata
for the readme.txt file so the build would fail since no items
were included in the NuGet package (.nupkg). Now the test uses
the project template wizard to set this property.
|
|
Some tests were not being run when the NUnit exclude was used even
though the platform should not have been excluded. Instead the tests
now use MonoDevelop's Platform class to detect the platform and then
Assert.Ignore if the platform is not supported. Also enabled the
build test BuildPackagingProjectFromTemplate which is currently failing
since no .nupkg file is generated.
|
|
Simplify resource ids
|
|
|
|
|
|
Remove redundant information, and make more information
redundant by setting good defaults in the MD props.
This lays some groundwork for the PackageConfig migration
and eventually SDK-style project format migration.
|
|
|
|
|
|
|
|
|
|
Stop autogenerating files and in future any changes to the generated UI files
can be made in the CS code itself
|
|
|
|
* Fix `make dist`
(cherry picked from commit 7732445e89434e17ff1e0217a640d841b29d5fc9)
* Don't strip assemblies from tarballs.
It'll make distro packagers cry, but the tarballs will actually work.
(cherry picked from commit b1820981f8acced4d4b721ce44ed5860ce8fb758)
* Include case-sensitivity fix from NRefactory
* Ensure BuildVariables.cs is up to date and in `make dist` tarballs
|
|
|
|
The old methods should be removed in the next cycle.
|
|
The former is only called when explicitly invoking widget.Destroy.
The latter is called properly (i.e. when you destroy a dialog, it'll
recursively destroy all children, thus hitting OnDestroyed)
|
|
CID113109
CID113124
CID113125
CID113128
CID113138
CID113141
CID113163
CID113174
CID113177
CID167841
CID167848
CID167867
CID167873
CID168029
CID168067
|
|
NuGet.Build.Packaging was bumped[1] to fix the build in mono-addins.
So, we pick up that change from mono-addins. And update
NuGet.Build.Packaging to v0.2.0 to be in sync.
bxc: #58815
--
1. https://github.com/mono/mono-addins/pull/88
|
|
|
|
Fixed bug #59461 - UI hang creating packaging project
https://bugzilla.xamarin.com/show_bug.cgi?id=59461
The VSTest addin checks the installed NuGet packages for test adapters
when a new solution is created. Returning the installed NuGet packages
for the packaging project was causing the UI thread to be blocked and
caused the IDE to hang.
|
