xamarin
/
xamarin-macios
зеркало из
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
xamarin-macios/msbuild/Xamarin.Mac.Tasks/Xamarin.Mac-Full-FrameworkL...

191 строка
25 KiB
XML
Исходник Обычный вид История

Build MSBuild targets & assemblies.
2016-04-21 16:40:25 +03:00
<?xml version="1.0" encoding="utf-8"?>
[msbuild/tests] Ensure our FrameworkList files have correct assemblies (#5367) One mono bump (https://github.com/xamarin/xamarin-macios/commit/6f2ebedb74fe8da250c8f53b61ffae2eb86fc711#diff-e801bb766cbaad95b50b1487b865f971) changed our `Xamarin.iOS-FrameworkList.xml.in` (and the tvOS and watchOS ones) and added 2 files ``` <File AssemblyName="System.Buffers" Version="4.0.99.0" /> <File AssemblyName="System.Memory" Version="4.0.99.0" /> ``` Around the same time this change was made in the IDE: https://github.com/mono/monodevelop/blob/e355f65870da4847d77ed1f3f2d07d1f78889cec/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Assemblies/TargetFramework.cs#L260 That means that VSMac, when creating a new cache file listing the assemblies, won’t scan the assemblies in those directories `/Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS`. This resulted in an incomplete cache file missing most assemblies leading to the IDE showing red checkmarks for known and installed assemblies. Ideally the FrameworkList files we ship should have a list of all the assemblies with PublicKeyToken and friends (the framework shouldn't be lazy and expect the IDEs to generate that file for us). This commit ships a test using the same logic as the IDE to populate the FrameworkList file. The test will report any missing assembly and print the xml element that should be added to the file. E.g: `<File AssemblyName="FSharp.Core" Version="3.98.4.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />` Then it's only a matter of copy/pasting that (: Note: even though this is the msbuild tests for iOS land I'm also scanning the Xamarin.Mac files here for simplicity. We also scan all assemblies in `/Facades`. Discussed in slack but adding all the facades assemblies doesn't compromise the project in the IDE (e.g: we still can't add incorrect assemblies) and it's required for some NuGet conflict resolution. See: https://github.com/xamarin/xamarin-macios/commit/ac8fd9e60aba0fae174eb7175a54d42a3c6b61f1
2019-01-11 21:59:22 +03:00
<FileList Name="Xamarin.Mac" TargetFrameworkDirectory="%TargetFrameworkDirectory%">
[xm][msbuild] Fix full profile FrameworkList file (#5674) * Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/801867 System.Memory.dll not being copied anywhere when Roslyn package is referenced The issue was that the XM FrameworkList was shared for the 2 profiles and there are differences. The Full profile for instance doesn't have `System.Memory` and that causes some issues with Nuget package references. * Updated tests to report issues against the XM Full and Mobile Framework lists * Now using 2 separate XM FrameworkList files (updated makefile) since the list of assemblies is different and that's expected by the mono team.
2019-02-27 20:38:38 +03:00
<File AssemblyName="FSharp.Core" Version="3.100.4.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="I18N.CJK" Version="4.0.0.0" PublicKeyToken="0738eb9f132ed756" ProcessorArchitecture="MSIL" />
<File AssemblyName="I18N.MidEast" Version="4.0.0.0" PublicKeyToken="0738eb9f132ed756" ProcessorArchitecture="MSIL" />
<File AssemblyName="I18N.Other" Version="4.0.0.0" PublicKeyToken="0738eb9f132ed756" ProcessorArchitecture="MSIL" />
<File AssemblyName="I18N.Rare" Version="4.0.0.0" PublicKeyToken="0738eb9f132ed756" ProcessorArchitecture="MSIL" />
<File AssemblyName="I18N.West" Version="4.0.0.0" PublicKeyToken="0738eb9f132ed756" ProcessorArchitecture="MSIL" />
<File AssemblyName="I18N" Version="4.0.0.0" PublicKeyToken="0738eb9f132ed756" ProcessorArchitecture="MSIL" />
<File AssemblyName="Microsoft.CSharp" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="Mono.CSharp" Version="4.0.0.0" PublicKeyToken="0738eb9f132ed756" ProcessorArchitecture="MSIL" />
<File AssemblyName="Mono.CompilerServices.SymbolWriter" Version="4.0.0.0" PublicKeyToken="0738eb9f132ed756" ProcessorArchitecture="MSIL" />
<File AssemblyName="Mono.Data.Sqlite" Version="4.0.0.0" PublicKeyToken="0738eb9f132ed756" ProcessorArchitecture="MSIL" />
<File AssemblyName="Mono.Data.Tds" Version="4.0.0.0" PublicKeyToken="0738eb9f132ed756" ProcessorArchitecture="MSIL" />
<File AssemblyName="Mono.Messaging" Version="4.0.0.0" PublicKeyToken="0738eb9f132ed756" ProcessorArchitecture="MSIL" />
<File AssemblyName="Mono.Posix" Version="4.0.0.0" PublicKeyToken="0738eb9f132ed756" ProcessorArchitecture="MSIL" />
<File AssemblyName="Mono.Security" Version="4.0.0.0" PublicKeyToken="0738eb9f132ed756" ProcessorArchitecture="MSIL" />
[msbuild/tests] Ensure our FrameworkList files have correct assemblies (#5367) One mono bump (https://github.com/xamarin/xamarin-macios/commit/6f2ebedb74fe8da250c8f53b61ffae2eb86fc711#diff-e801bb766cbaad95b50b1487b865f971) changed our `Xamarin.iOS-FrameworkList.xml.in` (and the tvOS and watchOS ones) and added 2 files ``` <File AssemblyName="System.Buffers" Version="4.0.99.0" /> <File AssemblyName="System.Memory" Version="4.0.99.0" /> ``` Around the same time this change was made in the IDE: https://github.com/mono/monodevelop/blob/e355f65870da4847d77ed1f3f2d07d1f78889cec/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Assemblies/TargetFramework.cs#L260 That means that VSMac, when creating a new cache file listing the assemblies, won’t scan the assemblies in those directories `/Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS`. This resulted in an incomplete cache file missing most assemblies leading to the IDE showing red checkmarks for known and installed assemblies. Ideally the FrameworkList files we ship should have a list of all the assemblies with PublicKeyToken and friends (the framework shouldn't be lazy and expect the IDEs to generate that file for us). This commit ships a test using the same logic as the IDE to populate the FrameworkList file. The test will report any missing assembly and print the xml element that should be added to the file. E.g: `<File AssemblyName="FSharp.Core" Version="3.98.4.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />` Then it's only a matter of copy/pasting that (: Note: even though this is the msbuild tests for iOS land I'm also scanning the Xamarin.Mac files here for simplicity. We also scan all assemblies in `/Facades`. Discussed in slack but adding all the facades assemblies doesn't compromise the project in the IDE (e.g: we still can't add incorrect assemblies) and it's required for some NuGet conflict resolution. See: https://github.com/xamarin/xamarin-macios/commit/ac8fd9e60aba0fae174eb7175a54d42a3c6b61f1
2019-01-11 21:59:22 +03:00
<File AssemblyName="OpenTK" Version="0.0.0.0" PublicKeyToken="84e04ff9cfb79065" ProcessorArchitecture="MSIL" />
[xm][msbuild] Fix full profile FrameworkList file (#5674) * Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/801867 System.Memory.dll not being copied anywhere when Roslyn package is referenced The issue was that the XM FrameworkList was shared for the 2 profiles and there are differences. The Full profile for instance doesn't have `System.Memory` and that causes some issues with Nuget package references. * Updated tests to report issues against the XM Full and Mobile Framework lists * Now using 2 separate XM FrameworkList files (updated makefile) since the list of assemblies is different and that's expected by the mono team.
2019-02-27 20:38:38 +03:00
<File AssemblyName="System.ComponentModel.Composition" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ComponentModel.DataAnnotations" Version="4.0.0.0" PublicKeyToken="31bf3856ad364e35" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Configuration.Install" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Configuration" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Core" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Data.Linq" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
Bump mono to 2019-08@528103728fc2aedb7b6062e11255d39a0ed3f31c to add missing NS2.1 APIs (#7147) See https://github.com/mono/mono/issues/17064. The 2019-08 version of the fix adds a new assembly with NS2.1 APIs that we stubbed out in 2019-06: System.Data.DataSetExtensions.dll
2019-10-02 14:59:39 +03:00
<File AssemblyName="System.Data.DataSetExtensions" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
[xm][msbuild] Fix full profile FrameworkList file (#5674) * Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/801867 System.Memory.dll not being copied anywhere when Roslyn package is referenced The issue was that the XM FrameworkList was shared for the 2 profiles and there are differences. The Full profile for instance doesn't have `System.Memory` and that causes some issues with Nuget package references. * Updated tests to report issues against the XM Full and Mobile Framework lists * Now using 2 separate XM FrameworkList files (updated makefile) since the list of assemblies is different and that's expected by the mono team.
2019-02-27 20:38:38 +03:00
<File AssemblyName="System.Data.Services.Client" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Data" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.EnterpriseServices" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IO.Compression.FileSystem" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IO.Compression" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IdentityModel.Selectors" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IdentityModel" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Json" Version="4.0.0.0" PublicKeyToken="31bf3856ad364e35" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Messaging" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.Http.WinHttpHandler" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
[msbuild/tests] Ensure our FrameworkList files have correct assemblies (#5367) One mono bump (https://github.com/xamarin/xamarin-macios/commit/6f2ebedb74fe8da250c8f53b61ffae2eb86fc711#diff-e801bb766cbaad95b50b1487b865f971) changed our `Xamarin.iOS-FrameworkList.xml.in` (and the tvOS and watchOS ones) and added 2 files ``` <File AssemblyName="System.Buffers" Version="4.0.99.0" /> <File AssemblyName="System.Memory" Version="4.0.99.0" /> ``` Around the same time this change was made in the IDE: https://github.com/mono/monodevelop/blob/e355f65870da4847d77ed1f3f2d07d1f78889cec/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Assemblies/TargetFramework.cs#L260 That means that VSMac, when creating a new cache file listing the assemblies, won’t scan the assemblies in those directories `/Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS`. This resulted in an incomplete cache file missing most assemblies leading to the IDE showing red checkmarks for known and installed assemblies. Ideally the FrameworkList files we ship should have a list of all the assemblies with PublicKeyToken and friends (the framework shouldn't be lazy and expect the IDEs to generate that file for us). This commit ships a test using the same logic as the IDE to populate the FrameworkList file. The test will report any missing assembly and print the xml element that should be added to the file. E.g: `<File AssemblyName="FSharp.Core" Version="3.98.4.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />` Then it's only a matter of copy/pasting that (: Note: even though this is the msbuild tests for iOS land I'm also scanning the Xamarin.Mac files here for simplicity. We also scan all assemblies in `/Facades`. Discussed in slack but adding all the facades assemblies doesn't compromise the project in the IDE (e.g: we still can't add incorrect assemblies) and it's required for some NuGet conflict resolution. See: https://github.com/xamarin/xamarin-macios/commit/ac8fd9e60aba0fae174eb7175a54d42a3c6b61f1
2019-01-11 21:59:22 +03:00
<File AssemblyName="System.Net.Http" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
[xm][msbuild] Fix full profile FrameworkList file (#5674) * Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/801867 System.Memory.dll not being copied anywhere when Roslyn package is referenced The issue was that the XM FrameworkList was shared for the 2 profiles and there are differences. The Full profile for instance doesn't have `System.Memory` and that causes some issues with Nuget package references. * Updated tests to report issues against the XM Full and Mobile Framework lists * Now using 2 separate XM FrameworkList files (updated makefile) since the list of assemblies is different and that's expected by the mono team.
2019-02-27 20:38:38 +03:00
<File AssemblyName="System.Net" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Numerics.Vectors" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Numerics" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Reflection.Context" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime.Serialization.Formatters.Soap" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime.Serialization" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ServiceModel.Internals" Version="0.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ServiceModel.Web" Version="4.0.0.0" PublicKeyToken="31bf3856ad364e35" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ServiceModel" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Transactions" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Web.Services" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Windows" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Xml.Linq" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Xml.Serialization" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Xml" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
[msbuild/tests] Ensure our FrameworkList files have correct assemblies (#5367) One mono bump (https://github.com/xamarin/xamarin-macios/commit/6f2ebedb74fe8da250c8f53b61ffae2eb86fc711#diff-e801bb766cbaad95b50b1487b865f971) changed our `Xamarin.iOS-FrameworkList.xml.in` (and the tvOS and watchOS ones) and added 2 files ``` <File AssemblyName="System.Buffers" Version="4.0.99.0" /> <File AssemblyName="System.Memory" Version="4.0.99.0" /> ``` Around the same time this change was made in the IDE: https://github.com/mono/monodevelop/blob/e355f65870da4847d77ed1f3f2d07d1f78889cec/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Assemblies/TargetFramework.cs#L260 That means that VSMac, when creating a new cache file listing the assemblies, won’t scan the assemblies in those directories `/Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS`. This resulted in an incomplete cache file missing most assemblies leading to the IDE showing red checkmarks for known and installed assemblies. Ideally the FrameworkList files we ship should have a list of all the assemblies with PublicKeyToken and friends (the framework shouldn't be lazy and expect the IDEs to generate that file for us). This commit ships a test using the same logic as the IDE to populate the FrameworkList file. The test will report any missing assembly and print the xml element that should be added to the file. E.g: `<File AssemblyName="FSharp.Core" Version="3.98.4.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />` Then it's only a matter of copy/pasting that (: Note: even though this is the msbuild tests for iOS land I'm also scanning the Xamarin.Mac files here for simplicity. We also scan all assemblies in `/Facades`. Discussed in slack but adding all the facades assemblies doesn't compromise the project in the IDE (e.g: we still can't add incorrect assemblies) and it's required for some NuGet conflict resolution. See: https://github.com/xamarin/xamarin-macios/commit/ac8fd9e60aba0fae174eb7175a54d42a3c6b61f1
2019-01-11 21:59:22 +03:00
<File AssemblyName="Xamarin.Mac" Version="0.0.0.0" PublicKeyToken="84e04ff9cfb79065" ProcessorArchitecture="MSIL" />
[xm][msbuild] Fix full profile FrameworkList file (#5674) * Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/801867 System.Memory.dll not being copied anywhere when Roslyn package is referenced The issue was that the XM FrameworkList was shared for the 2 profiles and there are differences. The Full profile for instance doesn't have `System.Memory` and that causes some issues with Nuget package references. * Updated tests to report issues against the XM Full and Mobile Framework lists * Now using 2 separate XM FrameworkList files (updated makefile) since the list of assemblies is different and that's expected by the mono team.
2019-02-27 20:38:38 +03:00
<File AssemblyName="mscorlib" Version="4.0.0.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
[msbuild/tests] Ensure our FrameworkList files have correct assemblies (#5367) One mono bump (https://github.com/xamarin/xamarin-macios/commit/6f2ebedb74fe8da250c8f53b61ffae2eb86fc711#diff-e801bb766cbaad95b50b1487b865f971) changed our `Xamarin.iOS-FrameworkList.xml.in` (and the tvOS and watchOS ones) and added 2 files ``` <File AssemblyName="System.Buffers" Version="4.0.99.0" /> <File AssemblyName="System.Memory" Version="4.0.99.0" /> ``` Around the same time this change was made in the IDE: https://github.com/mono/monodevelop/blob/e355f65870da4847d77ed1f3f2d07d1f78889cec/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Assemblies/TargetFramework.cs#L260 That means that VSMac, when creating a new cache file listing the assemblies, won’t scan the assemblies in those directories `/Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS`. This resulted in an incomplete cache file missing most assemblies leading to the IDE showing red checkmarks for known and installed assemblies. Ideally the FrameworkList files we ship should have a list of all the assemblies with PublicKeyToken and friends (the framework shouldn't be lazy and expect the IDEs to generate that file for us). This commit ships a test using the same logic as the IDE to populate the FrameworkList file. The test will report any missing assembly and print the xml element that should be added to the file. E.g: `<File AssemblyName="FSharp.Core" Version="3.98.4.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />` Then it's only a matter of copy/pasting that (: Note: even though this is the msbuild tests for iOS land I'm also scanning the Xamarin.Mac files here for simplicity. We also scan all assemblies in `/Facades`. Discussed in slack but adding all the facades assemblies doesn't compromise the project in the IDE (e.g: we still can't add incorrect assemblies) and it's required for some NuGet conflict resolution. See: https://github.com/xamarin/xamarin-macios/commit/ac8fd9e60aba0fae174eb7175a54d42a3c6b61f1
2019-01-11 21:59:22 +03:00
<File AssemblyName="Microsoft.Win32.Primitives" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="Microsoft.Win32.Registry.AccessControl" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="Microsoft.Win32.Registry" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.AppContext" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Collections.Concurrent" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Collections.NonGeneric" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Collections.Specialized" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Collections" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ComponentModel.Annotations" Version="4.2.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ComponentModel.EventBasedAsync" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ComponentModel.Primitives" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ComponentModel.TypeConverter" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ComponentModel" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Console" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Data.Common" Version="4.2.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Data.SqlClient" Version="4.2.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Diagnostics.Contracts" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Diagnostics.Debug" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Diagnostics.FileVersionInfo" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Diagnostics.Process" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Diagnostics.StackTrace" Version="4.1.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Diagnostics.TextWriterTraceListener" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Diagnostics.Tools" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Diagnostics.TraceEvent" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Diagnostics.TraceSource" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Diagnostics.Tracing" Version="4.2.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
Add System.Drawing.Common.dll to Xamarin.Mac-Full-FrameworkList.xml.in
2019-03-14 17:49:25 +03:00
<File AssemblyName="System.Drawing.Common" Version="4.0.0.0" PublicKeyToken="cc7b13ffcd2ddd51" ProcessorArchitecture="MSIL" />
[msbuild/tests] Ensure our FrameworkList files have correct assemblies (#5367) One mono bump (https://github.com/xamarin/xamarin-macios/commit/6f2ebedb74fe8da250c8f53b61ffae2eb86fc711#diff-e801bb766cbaad95b50b1487b865f971) changed our `Xamarin.iOS-FrameworkList.xml.in` (and the tvOS and watchOS ones) and added 2 files ``` <File AssemblyName="System.Buffers" Version="4.0.99.0" /> <File AssemblyName="System.Memory" Version="4.0.99.0" /> ``` Around the same time this change was made in the IDE: https://github.com/mono/monodevelop/blob/e355f65870da4847d77ed1f3f2d07d1f78889cec/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Assemblies/TargetFramework.cs#L260 That means that VSMac, when creating a new cache file listing the assemblies, won’t scan the assemblies in those directories `/Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS`. This resulted in an incomplete cache file missing most assemblies leading to the IDE showing red checkmarks for known and installed assemblies. Ideally the FrameworkList files we ship should have a list of all the assemblies with PublicKeyToken and friends (the framework shouldn't be lazy and expect the IDEs to generate that file for us). This commit ships a test using the same logic as the IDE to populate the FrameworkList file. The test will report any missing assembly and print the xml element that should be added to the file. E.g: `<File AssemblyName="FSharp.Core" Version="3.98.4.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />` Then it's only a matter of copy/pasting that (: Note: even though this is the msbuild tests for iOS land I'm also scanning the Xamarin.Mac files here for simplicity. We also scan all assemblies in `/Facades`. Discussed in slack but adding all the facades assemblies doesn't compromise the project in the IDE (e.g: we still can't add incorrect assemblies) and it's required for some NuGet conflict resolution. See: https://github.com/xamarin/xamarin-macios/commit/ac8fd9e60aba0fae174eb7175a54d42a3c6b61f1
2019-01-11 21:59:22 +03:00
<File AssemblyName="System.Drawing.Primitives" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Dynamic.Runtime" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Globalization.Calendars" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Globalization.Extensions" Version="4.1.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Globalization" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IO.Compression.ZipFile" Version="4.0.1.0" PublicKeyToken="b77a5c561934e089" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IO.FileSystem.AccessControl" Version="4.0.2.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IO.FileSystem.DriveInfo" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IO.FileSystem.Primitives" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IO.FileSystem.Watcher" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IO.FileSystem" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IO.IsolatedStorage" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IO.MemoryMappedFiles" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IO.Pipes" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IO.UnmanagedMemoryStream" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.IO" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Linq.Expressions" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Linq.Parallel" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Linq.Queryable" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Linq" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.AuthenticationManager" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.Cache" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
[xm][msbuild] Fix full profile FrameworkList file (#5674) * Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/801867 System.Memory.dll not being copied anywhere when Roslyn package is referenced The issue was that the XM FrameworkList was shared for the 2 profiles and there are differences. The Full profile for instance doesn't have `System.Memory` and that causes some issues with Nuget package references. * Updated tests to report issues against the XM Full and Mobile Framework lists * Now using 2 separate XM FrameworkList files (updated makefile) since the list of assemblies is different and that's expected by the mono team.
2019-02-27 20:38:38 +03:00
<File AssemblyName="System.Net.Http.Rtc" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
[msbuild/tests] Ensure our FrameworkList files have correct assemblies (#5367) One mono bump (https://github.com/xamarin/xamarin-macios/commit/6f2ebedb74fe8da250c8f53b61ffae2eb86fc711#diff-e801bb766cbaad95b50b1487b865f971) changed our `Xamarin.iOS-FrameworkList.xml.in` (and the tvOS and watchOS ones) and added 2 files ``` <File AssemblyName="System.Buffers" Version="4.0.99.0" /> <File AssemblyName="System.Memory" Version="4.0.99.0" /> ``` Around the same time this change was made in the IDE: https://github.com/mono/monodevelop/blob/e355f65870da4847d77ed1f3f2d07d1f78889cec/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Assemblies/TargetFramework.cs#L260 That means that VSMac, when creating a new cache file listing the assemblies, won’t scan the assemblies in those directories `/Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS`. This resulted in an incomplete cache file missing most assemblies leading to the IDE showing red checkmarks for known and installed assemblies. Ideally the FrameworkList files we ship should have a list of all the assemblies with PublicKeyToken and friends (the framework shouldn't be lazy and expect the IDEs to generate that file for us). This commit ships a test using the same logic as the IDE to populate the FrameworkList file. The test will report any missing assembly and print the xml element that should be added to the file. E.g: `<File AssemblyName="FSharp.Core" Version="3.98.4.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />` Then it's only a matter of copy/pasting that (: Note: even though this is the msbuild tests for iOS land I'm also scanning the Xamarin.Mac files here for simplicity. We also scan all assemblies in `/Facades`. Discussed in slack but adding all the facades assemblies doesn't compromise the project in the IDE (e.g: we still can't add incorrect assemblies) and it's required for some NuGet conflict resolution. See: https://github.com/xamarin/xamarin-macios/commit/ac8fd9e60aba0fae174eb7175a54d42a3c6b61f1
2019-01-11 21:59:22 +03:00
<File AssemblyName="System.Net.HttpListener" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.Mail" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.NameResolution" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.NetworkInformation" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.Ping" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.Primitives" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.Requests" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.Security" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.ServicePoint" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.Sockets" Version="4.2.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.Utilities" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.WebHeaderCollection" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.WebSockets.Client" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Net.WebSockets" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ObjectModel" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Reflection.Emit.ILGeneration" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Reflection.Emit.Lightweight" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Reflection.Emit" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Reflection.Extensions" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Reflection.Primitives" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Reflection.TypeExtensions" Version="4.1.2.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Reflection" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Resources.Reader" Version="4.0.2.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Resources.ReaderWriter" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Resources.ResourceManager" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Resources.Writer" Version="4.0.2.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime.CompilerServices.VisualC" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime.Extensions" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime.Handles" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime.InteropServices.RuntimeInformation" Version="4.0.3.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime.InteropServices.WindowsRuntime" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime.InteropServices" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime.Numerics" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime.Serialization.Formatters" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime.Serialization.Json" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime.Serialization.Primitives" Version="4.2.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime.Serialization.Xml" Version="4.1.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Runtime" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.AccessControl" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Claims" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.Algorithms" Version="4.3.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.Csp" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.DeriveBytes" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.Encoding" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.Encryption.Aes" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.Encryption.ECDiffieHellman" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.Encryption.ECDsa" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.Encryption" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.Hashing.Algorithms" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.Hashing" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.Primitives" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.ProtectedData" Version="4.0.2.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.RSA" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.RandomNumberGenerator" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Cryptography.X509Certificates" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Principal.Windows" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.Principal" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Security.SecureString" Version="4.1.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ServiceModel.Duplex" Version="4.0.3.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ServiceModel.Http" Version="4.1.2.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ServiceModel.NetTcp" Version="4.1.2.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ServiceModel.Primitives" Version="4.2.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ServiceModel.Security" Version="4.0.2.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ServiceProcess.ServiceController" Version="4.2.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Text.Encoding.CodePages" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Text.Encoding.Extensions" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Text.Encoding" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Text.RegularExpressions" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Threading.AccessControl" Version="4.0.2.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Threading.Overlapped" Version="4.1.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Threading.Tasks.Parallel" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Threading.Tasks" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Threading.Thread" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Threading.ThreadPool" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Threading.Timer" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Threading" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.ValueTuple" Version="4.0.3.0" PublicKeyToken="cc7b13ffcd2ddd51" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Xml.ReaderWriter" Version="4.1.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Xml.XDocument" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Xml.XPath.XDocument" Version="4.1.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Xml.XPath" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Xml.XmlDocument" Version="4.0.1.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Xml.XmlSerializer" Version="4.0.10.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
<File AssemblyName="System.Xml.Xsl.Primitives" Version="4.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />
Fix version numbers in FrameworkList.xml files (#7161) The existing test only checked that an assembly was mentioned in the file, but not that its version etc matches. Updated the test and fixed the differences.
2019-10-04 21:26:28 +03:00
<File AssemblyName="netstandard" Version="2.1.0.0" PublicKeyToken="cc7b13ffcd2ddd51" ProcessorArchitecture="MSIL" />
[msbuild/tests] Ensure our FrameworkList files have correct assemblies (#5367) One mono bump (https://github.com/xamarin/xamarin-macios/commit/6f2ebedb74fe8da250c8f53b61ffae2eb86fc711#diff-e801bb766cbaad95b50b1487b865f971) changed our `Xamarin.iOS-FrameworkList.xml.in` (and the tvOS and watchOS ones) and added 2 files ``` <File AssemblyName="System.Buffers" Version="4.0.99.0" /> <File AssemblyName="System.Memory" Version="4.0.99.0" /> ``` Around the same time this change was made in the IDE: https://github.com/mono/monodevelop/blob/e355f65870da4847d77ed1f3f2d07d1f78889cec/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Assemblies/TargetFramework.cs#L260 That means that VSMac, when creating a new cache file listing the assemblies, won’t scan the assemblies in those directories `/Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS`. This resulted in an incomplete cache file missing most assemblies leading to the IDE showing red checkmarks for known and installed assemblies. Ideally the FrameworkList files we ship should have a list of all the assemblies with PublicKeyToken and friends (the framework shouldn't be lazy and expect the IDEs to generate that file for us). This commit ships a test using the same logic as the IDE to populate the FrameworkList file. The test will report any missing assembly and print the xml element that should be added to the file. E.g: `<File AssemblyName="FSharp.Core" Version="3.98.4.0" PublicKeyToken="b03f5f7f11d50a3a" ProcessorArchitecture="MSIL" />` Then it's only a matter of copy/pasting that (: Note: even though this is the msbuild tests for iOS land I'm also scanning the Xamarin.Mac files here for simplicity. We also scan all assemblies in `/Facades`. Discussed in slack but adding all the facades assemblies doesn't compromise the project in the IDE (e.g: we still can't add incorrect assemblies) and it's required for some NuGet conflict resolution. See: https://github.com/xamarin/xamarin-macios/commit/ac8fd9e60aba0fae174eb7175a54d42a3c6b61f1
2019-01-11 21:59:22 +03:00
</FileList>