aspnet / Tooling

Issue tracker and info on Visual Studio tooling for ASP.NET
Other
256 stars 124 forks source link

referencing third party dll's #731

Open lilpug opened 8 years ago

lilpug commented 8 years ago

Do we know the eta on when we can start referencing dll libraries correctly again? creating a Nuget local feed for private dll references is not really a fix and to be quite frank i have no idea why you would want to limit yourself to only Nuget feeds, this question needs seriously answering, the threads plus git issues just keep growing for this single issue,

examples "but there are a lot more even on external sites",

http://stackoverflow.com/questions/37448764/asp-net-core-rc2-project-reference-the-dependency-x-could-not-be-resolved "rc2 but still same issue in rmt" http://forums.asp.net/t/2100395.aspx?Can+t+Add+Net+4+6+Reference http://forums.asp.net/t/2098410.aspx?adding+library+references+to+a+ASPNET+core+net+framework+project http://forums.asp.net/p/2100387/6069520.aspx http://forums.asp.net/p/2098587/6065998.aspx

aspnet/Mvc#4682 https://github.com/aspnet/Home/issues/1672 aspnet/Home#1612 aspnet/Tooling#565 aspnet/Tooling#700 https://github.com/dotnet/core/issues/184

MV10 commented 8 years ago

Looks like it's finally at least being tracked.

https://github.com/aspnet/Tooling/issues/688

adraut commented 8 years ago

@MV10 That issue isn't the same thing. It is about references between a .net core class library and a regular .net project. What @lilpug is talking about is referencing .dll files in a .net core class library, which cannot be done today without extraneous workarounds

mlorbetske commented 8 years ago

Hi @lilpug assembly references should be supported directly again with the move to use csproj projects for .NET Core. As far as an ETA goes, I can't give a specific date just yet, but the roadmap (https://blogs.msdn.microsoft.com/dotnet/2016/07/15/net-core-roadmap/) does give a timeline.

lilpug commented 8 years ago

Hi @mlorbetske thank you very much for a general answer, its nice to know the issue has been noted and a solution will be coming sometime in the short future

thorne991 commented 8 years ago

Ok, there is a work around..... Anybody actually produced a "WORKING" example of this wonderful work around...? Otherwise it is all just "Well try this"...... Or even better, "It works on my machine".....

Can somebody produce a working example of getting this to work in any way shape or form? I am 3 days in and still no luck with stuff like "JUST PRODUCE A NUGET Package" .... No luck... Yes it will put it into your references but you cannot use any of the methods. Edit: Just re-read what I posted... guess I'm a bit cranky.... Sorry for the harshness of the above stuff.