Skip to content
This repository has been archived by the owner on Apr 11, 2020. It is now read-only.

Will shared projects be supported in xproj projects? #217

Closed
TomasHubelbauer opened this issue Oct 13, 2015 · 5 comments
Closed

Will shared projects be supported in xproj projects? #217

TomasHubelbauer opened this issue Oct 13, 2015 · 5 comments

Comments

@TomasHubelbauer
Copy link

TomasHubelbauer commented Oct 13, 2015

In ASP .NET 4.5 one could hack the csproj file to include:

<Import Project="..\SharedProject\SharedProject.projitems" Label="Shared" />

This would work just fine and as expected. Under references, the shared project would be visible, the code would be shared and so on. It is still a hack, but it feels only like a lack of tooling.

In ASP .NET 5, the xproj file can still be patched, but the shared project doesn't appear under References and the code is not shared.

Will this change in the future? Are there plans to add support for shared projects to xproj projects? Preferably with the References dialog offering the Shared projects tab.

Redirected here from aspnet/dnx#2973.

@sayedihashimi
Copy link
Contributor

We have an item on our backlog to investigate how to share files. We were hoping to get started on that by now, but we got side tracked by httpplatformhandler work. I'll check with the team and see when we might be able to get to that.

For now it sounds like you've found a way to workaround.

@TomasHubelbauer
Copy link
Author

For now it sounds like you've found a way to workaround.

For csproj, yes. For xproj, no; the reference system there is all reworked. Could you please confirm the item on your backlog covers xproj as well? (Or xproj only, I can live with patching csproj, but xproj I will not make work by patching.) Thanks.

EDIT: Sorry, I just read the linked issue, which answers my question. Please ignore.

@sayedihashimi
Copy link
Contributor

TFS Bug#231254

@sayedihashimi
Copy link
Contributor

Sorry for the delay here. We've had a lot of updates over the past few months and I believe that this is working now in VS2017 RC. Can you try with the latest VS2017 and try again? I'll close this now, but please reopen if this issue still persists.

@TomasHubelbauer
Copy link
Author

No worries. I'm not going to try it myself anytime soon because it's not high on my priority list now but I welcome anyone coming across this with a bit of time to please confirm or deny.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants