Scripty
Scripty copied to clipboard
daveaglick
Empty Roslyn project in net standard library.
Using the MSBuild task in a .NET Standard class library, Project.Analysis.Documents is empty, as far as I can tell there's nothing in the Roslyn project at all.
Dunno if this is anything on Scripty's end or if anything can be done about it, but figured it was worth making known.
If there's stuff in the project, it should be in the Roslyn workspace, and Roslyn shouldn't have any issues dealing with .NET Standard/Core projects. In other words, there should be documents in the collection.
Can you provide any more information? What does the project structure look like?
Hi,
I came here expecting this exact kind of bug report. My understanding is that Roslyn is not capable of working with SDK-style csproj. See here. It has blocked me from updating my own software libraries to work correctly in the new world.
Hmm...I wonder if the custom workspace the Mono folks built for VS Mac would work
What custom workspace did they build? I'd be interested in trying it. Would love to get my IL Viewer working again.
@JosephWoodward I'm going off of this comment: https://github.com/dotnet/roslyn/issues/20275#issuecomment-309100824 Apparently OmniSharp also has it's own workspace (a little further down). Been meaning to check either/both of those out.
Scripty has other issues with MSBuild workspace like that it can't be used as an MSBuild task because MSBuild won't let you nest execution. Would love to get the workspace (and thus Scripty itself) in-proc with the build task.
@daveaglick That's right, OmniSharp have their own adhoc workspace that they've built from the ground up which resolves all dependencies. It's pretty comprehensive. I've considered trying to build one but having looked at it I wouldn't know where to start.