Closed smaillet closed 5 years ago
Currently blocked by this.
@smaillet @StephenStrickland there are two changes you need to add:
in the folder with solution file you need to add nuget.config
with contents as follows (specifically important is the NuGet feed for CoreFx experimental repo):
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<add key="api.nuget.org" value="https://api.nuget.org/v3/index.json" />
<add key="corefxlab" value="https://dotnet.myget.org/F/dotnet-corefxlab/api/v3/index.json" />
</packageSources>
</configuration>
and in your Consumer.csproj you need to have also this reference:
<DotNetCliToolReference Include="dotnet-codegen" Version="0.4.11" />
You can reference this (my) project for a working example using NuGet packages: https://github.com/amis92/CodeGenerationBugDemo (it's a BugDemo but it works as is, to repro the bug follow README).
Let's call it resolved via https://github.com/jaredthirsk/CodeGeneration.Roslyn.Walkthrough - the actual sample is to be included in this repo will be tracked in #41
Repro steps
1) Load TestRoslynGenerator solution TestRoslynGenerator.zip into VS2017 1) I've tried with 15.4.1 and 15.5.0 Preview 2 same results 2) Build the solution (F6)
Expected
successful build
Actual
Error MSB6006 "dotnet" exited with code 1
Additional Details
After enabling full diagnostics in MSBuild I found the call to dotnet.exe and a message that provides some further hint on the problem:
I don't pretend to understand the dotnet.exe tooling well enough to know what that means.
Suggestion
Provide complete standalone sample solution(s) that are built and validated as part of CI builds so it is easier for users to try and can catch issues in the builds