Runtime-specific build fails for projects with P2P references #696

blackdwarf · 2017-01-20T06:05:49Z

[ Moved from dotnet/cli#4992 ]

Steps to reproduce

test_app.zip
in test_app\App:

dotnet restore
dotnet build -r win10-x64

Expected behavior

build succeeds

Actual behavior

build fails with output:

C:\Users\svbomer\AppData\Local\Temp\.NETStandard,Version=v1.4.AssemblyAttributes.cs(4,20): error CS0400: The type or namespace name 'System' could not be found in the global namespace (are you missing an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(6,12): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(7,12): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(8,12): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(9,12): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(10,12): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(11,12): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(12,12): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(13,12): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(14,12): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
C:\Users\svbomer\AppData\Local\Temp\.NETStandard,Version=v1.4.AssemblyAttributes.cs(4,71): error CS0518: Predefined type 'System.String' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
C:\Users\svbomer\AppData\Local\Temp\.NETStandard,Version=v1.4.AssemblyAttributes.cs(4,100): error CS0246: The type or namespace name 'FrameworkDisplayName' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
C:\Users\svbomer\AppData\Local\Temp\.NETStandard,Version=v1.4.AssemblyAttributes.cs(4,123): error CS0518: Predefined type 'System.String' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(6,55): error CS0518: Predefined type 'System.String' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(7,61): error CS0518: Predefined type 'System.String' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(8,59): error CS0518: Predefined type 'System.String' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(9,59): error CS0518: Predefined type 'System.String' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(10,68): error CS0518: Predefined type 'System.String' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(11,55): error CS0518: Predefined type 'System.String' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(12,53): error CS0518: Predefined type 'System.String' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(13,55): error CS0518: Predefined type 'System.String' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(14,63): error CS0518: Predefined type 'System.String' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
Library.cs(1,7): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
C:\Users\svbomer\AppData\Local\Temp\.NETStandard,Version=v1.4.AssemblyAttributes.cs(2,7): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
C:\Users\svbomer\AppData\Local\Temp\.NETStandard,Version=v1.4.AssemblyAttributes.cs(3,7): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(3,7): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
obj\Debug\netstandard1.4\Library.AssemblyInfo.cs(4,7): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
Library.cs(30,7): error CS0518: Predefined type 'System.Object' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
Library.cs(3,14): error CS0518: Predefined type 'System.Object' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
Library.cs(19,12): error CS0518: Predefined type 'System.Int32' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
Library.cs(24,24): error CS0518: Predefined type 'System.Int32' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
Library.cs(24,12): error CS0518: Predefined type 'System.Void' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]Library.cs(5,13): error CS0518: Predefined type 'System.Int32' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]Library.cs(6,13): error CS0518: Predefined type 'System.Int32' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]Library.cs(8,5): error CS0518: Predefined type 'System.Void' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
Library.cs(14,20): error CS0518: Predefined type 'System.Int32' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
Library.cs(14,5): error CS0518: Predefined type 'System.Void' is not defined or imported [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj] D:\cli\artifacts\win10-x64\stage2\sdk\1.0.0-preview5-004233\Sdks\Microsoft.NET.Sdk\build\Microsoft.NET.Sdk.targets(82,5): error : Assets file 'C:\Users\svbomer\active\projects\managed_linker\test_app\Library\obj\project.assets.json' doesn't have a target for '.NETStandard,Version=v1.4/win10-x64'. Ensure you have restored this project for TargetFramework='netstandard1.4' and RuntimeIdentifier='win10-x64'. [C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj]
D:\cli\artifacts\win10-x64\stage2\sdk\1.0.0-preview5-004233\Sdks\Microsoft.NET.Sdk\build\Microsoft.NET.Sdk.targets(82,5): error : Cannot find project info for 'C:\Users\svbomer\active\projects\managed_linker\test_app\Library\Library.csproj'. This can indicate a missing project reference. [C:\Users\svbomer\active\projects\managed_linker\test_app\App\test_app.csproj]

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.0-preview5-004233)

Product Information:
 Version:            1.0.0-preview5-004233
 Commit SHA-1 hash:  1fd99f1588

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.14393
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   D:\cli\artifacts\win10-x64\stage2\sdk\1.0.0-preview5-004233

The text was updated successfully, but these errors were encountered:

dasMulli · 2017-01-23T20:11:32Z

Jus repro'd it with csproj files compatible with the new implicit items:
repro.zip
Reproduces with CLI versions 1.0.0-rc4-004598 as well as 1.0.0-rc3-004517. (run dotnet restore and dotnet publish -r win7-x64 in the App directory)

This currently prevents creating self-contained applications that reference a library project.
Is this scenario expected to work in RC3? cc @dsplaisted @nguerrera

srivatsn · 2017-01-26T19:13:37Z

Is this the same as #527? @nguerrera

AlgorithmsAreCool · 2017-01-30T17:30:43Z

I attempted an upgrade to RC3 on my project and ran into this issue. Is a short term fix anticipated or should I roll back until later?

dasMulli · 2017-01-30T20:44:10Z

The problem seems to be that when dotnet build -r some-RID sets RuntimeIdentifier, this is also passed along to referenced projects. If a referenced project has not been restored for a runtime (like a library project), this fails with the following error:

…/1.0.0-rc3-004530/…/Microsoft.NET.Sdk.targets(76,5): error :
 Assets file '…' doesn't have a target for '.NETStandard,Version=v1.4/win10-x64'. 
Ensure you have restored this project for TargetFramework='netstandard1.4' and RuntimeIdentifier='win10-x64'. […/Lib/Lib.csproj]

@AlgorithmsAreCool Since I don't know a simple way to unset properties (is there any?), the only way I could make this work is by using and intermediate property:
Use dotnet build /p:AppRuntimeIdentifier=win10-x64 to build.
In the main application's csproj file:

<PropertyGroup>
  <RuntimeIdentifier>$(AppRuntimeIdentifier)</RuntimeIdentifier>
</PropertyGroup>

@srivatsn I don't think this is related to #527

srivatsn · 2017-01-30T21:01:37Z

Interesting. @DustinCampbell was talking about this issue as well. I suspect the fix needs to be a mix of CLI and SDK similar to what you've done. The CLI should set /p:RequestedRuntimeIdentifier or some such property and have the SDK apply it to a project only if it's "applicable". We'll need the same thing for -f as well.

@piotrpMSFT @livarcocc thoughts?

DustinCampbell · 2017-01-30T21:13:38Z

Yes, we need to fix this. Per our hallway conversation, we should do the same thing for TargetFramework as well. This becomes a significant problem when trying dotnet build an .sln file.

nguerrera · 2017-01-30T21:15:02Z

@rainersigwald

rainersigwald · 2017-01-30T21:19:15Z

Yes, setting a property at the command line overrides all projects that build in that invocation. Having an EntryPointRuntimeIdentifier or something similar sounds reasonable (albeit as another concept people have to know about).

DustinCampbell · 2017-01-30T21:21:17Z

@rainersigwald: I you recall, this is the thing you and I chatted about last Friday.

I don't think it's actually another concept. From the user perspective, MSBuild will do the thing it's always done. If you set RuntimeIdentifier or TargetFramework globally, it's applied globally. However, from the perspective of the CLI, setting the "--framework" or "--runtime" properties during "dotnet build" can be a bit smarter and do what the user very likely expects to happen.

rainersigwald · 2017-01-30T21:23:59Z

Yeah, it makes sense once you know the details--but understanding that dotnet build --runtime Whatever is more than just sugar over MSBuild /p:Runtime=Whatever is required. Still think it's the right thing to do.

If we had more time I might recommend renaming the inner per-project property to be a bit more esoteric and renaming the outer "overall requested" property to more closely match the CLI command line param . . . but that's a nit.

dasMulli · 2017-01-30T21:41:37Z

So, what I would expect to happen:
For all projects that specify RuntimeIdentifiers, it sets RuntimeIdentifier if not already set.
I guess it would look sth like:

<RuntimeIdentifier Condition=" '$(RuntimeIdentifier)' == '' and '$(EntryPointRuntimeIdentifier)' != '' and '$(RuntimeIdentifiers)' != '' ">$(EntryPointRuntimeIdentifier)</RuntimeIdentifier>

It should be possible to reference RID-specific and RID-agnostic projects that way.

If we had more time I might recommend renaming …

@rainersigwald Since this will (and should) probably stick around for at least a decade or two, I'd like there to be a proper naming strategy ❤️

nguerrera · 2017-01-30T21:52:11Z

@srivatsn @piotrpMSFT Since this issue is separate from the other RID issues on my plate and time is of the essence could someone else drive this into CLI + SDK?

DustinCampbell · 2017-01-30T23:06:30Z

@rainersigwald:

Yeah, it makes sense once you know the details--but understanding that dotnet build --runtime Whatever is more than just sugar over MSBuild /p:Runtime=Whatever is required. Still think it's the right thing to do.

That's fair, but people probably shouldn't be thinking of dotnet build as sugar over MSBuild. If that's all it were, there isn't much value from a CLI UI perspective.

AlgorithmsAreCool · 2017-01-30T23:30:04Z

I was able to work around my issue with by making the restore -r <RID> step explicit in my build pipeline for now.

srivatsn · 2017-02-01T06:26:42Z

@piotrpMSFT has graciously offered to help out with this. Assigning to Peter.

niemyjski · 2017-02-01T17:51:37Z

I'm also hitting this when trying to upgrade foundatio: https://github.com/exceptionless/foundatio/tree/feature/dotnet

AlgorithmsAreCool · 2017-02-01T21:01:04Z

@niemyjski are you specifying an RID when you build or publish? If so have you tried adding a dotnet restore -r <RID> step just before your build/publish in your build script?

TheRealPiotrP · 2017-02-02T02:19:47Z

Starting to take a look at this. Per @DustinCampbell's point, we want to address both:

Specify -r for a root project whose P2P dependencies are not RID specific
Specify -f or -r for a solution for which only some projects support that TFM or RID

Having looked at the SDK a bit, I'm less convinced now that the solution to these problems will be unified. This issue may end up being split into two, where we will want to fix both. More info to come.

TheRealPiotrP · 2017-02-02T07:00:45Z

odd. I just tried @dasMulli's repro on CLI 1.0.0-rc4-004748 on osx with -r osx.10.11-x64 and the publish operation was successful, producing what seems to be a working self contained app. I'll try this again on Windows when in the office tomorrow. Going to lok at -f for now.

dasMulli · 2017-02-02T08:11:27Z

@piotrpMSFT really odd.. it repros with both 1.0.0-rc4-004748 and 1.0.0-rc4-004755 on my Mac 😕

dasMulli · 2017-02-02T08:17:23Z

Another workaround that works is to reference the library with:

<ProjectReference Include="..\Lib\Lib.csproj" Properties="RuntimeIdentifier=" />

This would be easier to do with an update item from the SDK but I haven't explored what the effects are - probably loosing RID-specific items from projects. (did this ever work in project.json? RID-specific libraries?)

niemyjski · 2017-02-02T23:32:22Z

@AlgorithmsAreCool Nope, no rids at all.

Re-enable when dotnet/sdk#696 is resolved

TheRealPiotrP · 2017-02-07T08:33:35Z

Just thought I'd share that PR #828 should address the RID issue and does not introduce any new user gestures or concepts. We were able to keep the alternate property name as an internal contract between Referring projects and Referenced projects.

I'm trying a similar approach with the build sln -f issue... though that is proving considerably more involved.

niemyjski · 2017-02-07T20:14:32Z

Did this make its n? https://blogs.msdn.microsoft.com/visualstudio/2017/02/07/another-update-to-visual-studio-2017-rc/

TheRealPiotrP · 2017-02-08T02:51:41Z

No, it's not merged yet. I hope to have a CLI that exhibits this behavior available this week, however. Since -r is mostly a command-line consideration, this should unblock most affected folks.

The change impacts a lot of repos, so merging it will be a full-day dance I'm afraid.

srivatsn · 2017-02-16T23:58:28Z

Fixed with #836

…0190606.7 (dotnet#696) - Microsoft.AspNetCore.Mvc.Api.Analyzers - 3.0.0-preview7.19306.7 - Microsoft.AspNetCore.Mvc.Analyzers - 3.0.0-preview7.19306.7

dsplaisted added the Urgency-Soon label Jan 23, 2017

dsplaisted self-assigned this Jan 23, 2017

srivatsn added release blocking and removed release blocking labels Jan 25, 2017

srivatsn assigned nguerrera and unassigned dsplaisted Jan 27, 2017

srivatsn added this to the 1.0 RTM milestone Jan 27, 2017

srivatsn assigned TheRealPiotrP and unassigned nguerrera Feb 1, 2017

srivatsn added the Bug label Feb 1, 2017

dsplaisted mentioned this issue Feb 2, 2017

Publishing self-contained app fails if it has a project reference #796

Closed

natemcmaster pushed a commit to aspnet/IISIntegration that referenced this issue Feb 3, 2017

Disable standalone tests to workaround issues in MIcrosoft.NET.Sdk

03deef1

Re-enable when dotnet/sdk#696 is resolved

natemcmaster pushed a commit to aspnet/IISIntegration that referenced this issue Feb 3, 2017

Disable standalone tests to workaround issues in Microsoft.NET.Sdk

aec1bff

Re-enable when dotnet/sdk#696 is resolved

This was referenced Feb 3, 2017

Upgrade to VS 2017 aspnet/IISIntegration#322

Merged

Upgrade to VS 2017 aspnet/Entropy#194

Merged

vad710 mentioned this issue Feb 4, 2017

dotnet build with runtime specified does not create the right output #527

Closed

dasMulli mentioned this issue Feb 4, 2017

Conceptual Question - Are Runtime Identifiers applicable to .NET Standard Libraries? dotnet/standard#193

Closed

This was referenced Feb 7, 2017

Enable P2P's to determine their own compilation RID #828

Merged

Enable P2P's to determine their own compilation RID dotnet/msbuild#1674

Merged

TheRealPiotrP mentioned this issue Feb 7, 2017

"dotnet build" fails on non-Windows for projects that multi-target where Desktop is one of the targets frameworks. #826

Closed

rainersigwald mentioned this issue Feb 13, 2017

Solution-level error when a RuntimeIdentifier is specified #863

Closed

natidea mentioned this issue Feb 14, 2017

Use RID less targets to obtain compile assets #836

Merged

srivatsn closed this as completed Feb 16, 2017

TheRealPiotrP mentioned this issue Feb 17, 2017

SDK PR Validation CI and Signed Build CI should use same OS's #885

Closed

dasMulli mentioned this issue Apr 7, 2017

Error when running dotnet publish #1097

Closed

nguerrera mentioned this issue Oct 9, 2017

Double Evaluation Fix dotnet/msbuild#2595

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Runtime-specific build fails for projects with P2P references #696

Runtime-specific build fails for projects with P2P references #696

blackdwarf commented Jan 20, 2017

dasMulli commented Jan 23, 2017

srivatsn commented Jan 26, 2017

AlgorithmsAreCool commented Jan 30, 2017

dasMulli commented Jan 30, 2017 •

edited

Loading

srivatsn commented Jan 30, 2017 •

edited

Loading

DustinCampbell commented Jan 30, 2017

nguerrera commented Jan 30, 2017

rainersigwald commented Jan 30, 2017

DustinCampbell commented Jan 30, 2017

rainersigwald commented Jan 30, 2017

dasMulli commented Jan 30, 2017

nguerrera commented Jan 30, 2017

DustinCampbell commented Jan 30, 2017

AlgorithmsAreCool commented Jan 30, 2017

srivatsn commented Feb 1, 2017

niemyjski commented Feb 1, 2017

AlgorithmsAreCool commented Feb 1, 2017

TheRealPiotrP commented Feb 2, 2017

TheRealPiotrP commented Feb 2, 2017

dasMulli commented Feb 2, 2017

dasMulli commented Feb 2, 2017

niemyjski commented Feb 2, 2017

TheRealPiotrP commented Feb 7, 2017

niemyjski commented Feb 7, 2017

TheRealPiotrP commented Feb 8, 2017

srivatsn commented Feb 16, 2017

Runtime-specific build fails for projects with P2P references #696

Runtime-specific build fails for projects with P2P references #696

Comments

blackdwarf commented Jan 20, 2017

Steps to reproduce

Expected behavior

Actual behavior

Environment data

dasMulli commented Jan 23, 2017

srivatsn commented Jan 26, 2017

AlgorithmsAreCool commented Jan 30, 2017

dasMulli commented Jan 30, 2017 • edited Loading

srivatsn commented Jan 30, 2017 • edited Loading

DustinCampbell commented Jan 30, 2017

nguerrera commented Jan 30, 2017

rainersigwald commented Jan 30, 2017

DustinCampbell commented Jan 30, 2017

rainersigwald commented Jan 30, 2017

dasMulli commented Jan 30, 2017

nguerrera commented Jan 30, 2017

DustinCampbell commented Jan 30, 2017

AlgorithmsAreCool commented Jan 30, 2017

srivatsn commented Feb 1, 2017

niemyjski commented Feb 1, 2017

AlgorithmsAreCool commented Feb 1, 2017

TheRealPiotrP commented Feb 2, 2017

TheRealPiotrP commented Feb 2, 2017

dasMulli commented Feb 2, 2017

dasMulli commented Feb 2, 2017

niemyjski commented Feb 2, 2017

TheRealPiotrP commented Feb 7, 2017

niemyjski commented Feb 7, 2017

TheRealPiotrP commented Feb 8, 2017

srivatsn commented Feb 16, 2017

dasMulli commented Jan 30, 2017 •

edited

Loading

srivatsn commented Jan 30, 2017 •

edited

Loading