Skip to content

Conversation

@enricosada
Copy link
Contributor

@enricosada enricosada commented Jul 27, 2016

  • rebased to latests master
  • The project.json are in the same directory of the projects (no more .netcore suffix)
  • fixed error with .fsproj and project.json in same directory, thx nuget -_-"
  • cleanup fake build script
  • tests can be run with dotnet test inside tests\service directory
  • the normal build Release (or just Nuget.AddNetCore ) will build, run tests (failing atm) and merge packages

ref dotnet/msbuild#394

```
C:\Program Files (x86)\MSBuild\Microsoft\NuGet\Microsoft.NuGet.targets(140,5): Your project is not referencing the ".NETFramework,Version=v4.5" framework. Add a reference to ".NETFramework,Version=v4.5" in the "frameworks" section of your project.json, and then re-run NuGet restore
```
@enricosada
Copy link
Contributor Author

ok better now 😄

Test Run Summary
  Overall result: Failed
  Test Count: 132, Passed: 120, Failed: 6, Inconclusive: 0, Skipped: 6

So issue was references.

  • I added a sample .net core library in tests\projects\Sample_NETCoreSDK_FSharp_Library_netstandard1.6\obj\Debug\netstandard1.6
  • the precompile script of the test library build that project
  • the test read the references from the generated response file in obj\Debug\netstandard1.6\dotnet-compile-fsc.rsp

i think is enough to be future proof in the near term.

@enricosada
Copy link
Contributor Author

enricosada commented Jul 27, 2016

Down to only 2 failures:

  Test Count: 132, Passed: 124, Failed: 2, Inconclusive: 0, Skipped: 6
1) Failed : Tests.Service.ProjectAnalysisTests.Test project31 C# type attributes
  Expected: set\n  ["(DebuggerDisplayAttribute, [(type Microsoft.FSharp.Core.string, "Count = {Count}")], [])";\n   "(DebuggerTypeProxyAttribute, [], [])";\n   "(DefaultMemberAttribute, [(type Microsoft.FSharp.Core.string, "Item")], [])"]\nActual: set\n  ["(DefaultMemberAttribute, [(type Microsoft.FSharp.Core.string, "Item")], [])"]
  Expected and actual are both <Microsoft.FSharp.Collections.FSharpSet`1[System.String]>
  Values differ at index [0]
  Expected string length 88 but was 75. Strings differ at index 3.
  Expected: "(DebuggerDisplayAttribute, [(type Microsoft.FSharp.Core.strin..."
  But was:  "(DefaultMemberAttribute, [(type Microsoft.FSharp.Core.string,..."
  --------------^
at FsUnit.shouldEqual[a](a x, a y)
2) Failed : Tests.Service.ProjectAnalysisTests.Test project31 Format C# type attributes
  Expected: set\n  ["[<DebuggerDisplayAttribute ("Count = {Count}")>]";\n   "[<DebuggerTypeProxyAttribute (typeof<Mscorlib_CollectionDebugView<>>)>]";\n   "[<Reflection.DefaultMemberAttribute ("Item")>]"]\nActual: set ["[<Reflection.DefaultMemberAttribute ("Item")>]"]
  Expected and actual are both <Microsoft.FSharp.Collections.FSharpSet`1[System.String]>
  Values differ at index [0]
  Expected string length 48 but was 46. Strings differ at index 2.
  Expected: "[<DebuggerDisplayAttribute ("Count = {Count}")>]"
  But was:  "[<Reflection.DefaultMemberAttribute ("Item")>]"
  -------------^

I checked and the attributes exists in the .net core List<T>.
I dont know how to debug that.

@enricosada
Copy link
Contributor Author

enricosada commented Jul 28, 2016

Ok skipped (with Ignore) the failing test, so dotnet test pass.
There are others tests skipped like that for .NET Core

I removed the additional appveyor job, now .net core is ok and should remain always green

@enricosada
Copy link
Contributor Author

this pr is ready /cc @dsyme @matthid

@matthid
Copy link
Contributor

matthid commented Jul 29, 2016

Nice work, LGTM.

I would really appreciate merging this soon and keeping the build green. Whenever I come back to update to latest FSharp.Compiler.Service I need some hours to figure out how to compile the thing for dnc ...

"Microsoft.Build.Tasks.Core": "0.1.0-preview-00028-160627",
"Microsoft.Build.Utilities.Core": "0.1.0-preview-00028-160627",
"System.Runtime.Serialization.Json": "4.0.2",
"Microsoft.FSharp.Core.netcore": "1.0.0-alpha-*",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not "FSharp.Core": "4.0.1.7-alpha"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants