New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Project to expose information on Resources #7772
Comments
So, traditionally the Workspace API hasn't included emit-only information, since we don't have a properties to put them anywhere. That said, the scenario isn't terribly unreasonable. @mattwar, thoughts? |
We already jumped that shark with additional documents. |
So now that we're shark jumping masters, no concerns with this, at least from the design perspective? |
ping @mattwar is this something you think we should do? |
I think there is a reasonable argument to be made. But I don't think there is enough benefit to justify doing this over other work. |
I'm currently working on some stuff and hoping to use the I'd be interested in taking a look at implementing support for additional types of MSBuild items (including resources). It doesn't look like it'll be to hard - basically just mechanically duplicating the code that supports AdditionalFiles I'd like to add explicit support for:
I think that covers the main MSBuild project items that weren't already available. Would a PR that added support for these items similarly to how AdditionalFiles is handled get consideration? Related to this issue, but probably a separate discussion - it would be nice if the MSBuild workspace/project were leaky and I could access either the |
Would need a real API request for this that we can take through API review. |
I need to emit and run projects from Roslyn workspaces. By default, resources are not emitted into the DLL that
Compilation.Emit()
produces. There's an argument that accepts multipleResourceDescription
to be embedded into the emitted DLL. However, the Workspace API doesn't offer any information about resources that will allow me to built the appropriateResourceDescription
.It would be nice if this information was exposed within
Project
.Original Stack Overflow Question
The text was updated successfully, but these errors were encountered: