-
Notifications
You must be signed in to change notification settings - Fork 60
Walkthrough appears to be broken, have other issues #46
Comments
I looked under the section for "Packaging up your code generator for others' use", which doesn't apply to me since I'm not at the point yet of packaging my code for others, and I found a hint, which is to add UPDATE: Fix was to update the version to match the latest Nuget package I used:
|
So, I got it working! At least via a project reference as you can see in my repo. I still get compile warnings: 'System.Net.Http' could not be found, in the net462 projects. |
It looks like you figured it out. I've fixed the README for the comments you mentioned. If I'm missing anything else, please open a new issue or send a PR. |
I made a repo for this repro: https://github.com/jaredthirsk/CodeGeneration.Roslyn.Walkthrough
Minor issues with the walkthrough instructions:
"This must be done in a library that targets netstandard1.3 or net46 (or later)": I created a new NETStandard 1.3 project and added CodeGeneration.Roslyn but it says "Package CodeGeneration.Roslyn 0.4.11 is not compatible with netstandard1.3 (.NETStandard,Version=v1.3). Package CodeGeneration.Roslyn 0.4.11 supports: netstandard1.5 (.NETStandard,Version=v1.5)
One or more packages are incompatible with .NETStandard,Version=v1.3."
"You may need to define this property in your .NET SDK netstandard project to workaround the problem with the Microsoft.Composition NuGet package:" Why would I need to follow this instruction? What is the symptom that would show me I need to do this? (What does the Microsoft.Composition package have to do with anything?)
Breaking problem:
I created a .NETStandard 1.5 library that references my NETStandard 1.5 generator library but I get this build output:
It's hiding the actual error. If I run msbuild from the developer command prompt, here is the output:
(I tried using bold to highlight errors but it doesn't work inside a code block. So search for ** to see interesting parts.)
The text was updated successfully, but these errors were encountered: