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 "Add Reference" to .NET Core class library that uses .NET Framework from a traditional class library #231

Closed
ryanelian opened this Issue Jul 20, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@ryanelian
Copy link

ryanelian commented Jul 20, 2016

First of all, I would like to say that I love how .NET Core projects can automatically manage package dependencies. Brilliant.

Hence I began developing projects using ASP.NET MVC Core, albeit still using the full .NET 4.5 instead of .NET Core due to various reasons. So my class libraries project.json often ended up like this:

{
  "version": "1.0.0-*",

  "dependencies": {
  },

  "frameworks": {
    "net45": {
    }
  }
}

Which is great and works beautifully in MVC Core land. However, as soon as someone need Add Reference to my class libraries without being packaged into NuGet packages (actually I haven't tried packaging those classes into NuGet packages, but I don't see why they wouldn't work), this happens:

---------------------------
Microsoft Visual Studio
---------------------------
A reference to 'My.Class.Library' could not be added. An assembly must have a 'dll' or 'exe' extension in order to be referenced.
---------------------------
OK   
---------------------------

I realized that this scenario is the opposite of the ".NET Core project needs to reference the .NET 4.5 DLLs", but is it possible to have this feature for convenience?

@blackdwarf

This comment has been minimized.

Copy link

blackdwarf commented Jul 23, 2016

@ryanelian can you please open a new issue on aspnet/tooling and close this one? That repo will be a better place for this issue. Thanks!

@blackdwarf

This comment has been minimized.

Copy link

blackdwarf commented Jul 26, 2016

Actually, now that I look at the issue, I believe this should be mitigated with moving to csproj. Will close this. Please reopen if you feel this was in error.

@blackdwarf blackdwarf closed this Jul 26, 2016

@Daniel15

This comment has been minimized.

Copy link

Daniel15 commented Aug 24, 2016

I believe this should be mitigated with moving to csproj

@blackdwarf Is there a Github issue I can follow for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment