CODEWITHSUNDEEP
.net.net-core
SiberianGuy
SiberianGuy

Reputation: 25302

What's the point of running .NET core app over full framework?

I'm trying to wrap my head around all the possible variations of .NET frameworks and the ways to use them.

You can easily run your application over full .NET frameworks like this:

{
  “version”: “1.0.0-*”,
  “buildOptions”: {
    “emitEntryPoint”: true
  },

  “dependencies”: {
    “Microsoft.NETCore.App”: {
      “type”: “platform”,
      “version”: “1.0.0”
    }
  },

  “frameworks”: {
    “net452"
  }
}

But what's the point of doing so? My rough understanding is that by doing so you loose .NET Core interoperability feature (not able to run on Mac or Linux) but on the other hand you can reference not only .NET Core assemblies but good old .NET assemblies too (which is great as many .NET core libraries are still alpha/beta). Am I right about that? Anything else that I miss?

Upvotes: 0

Views: 94

Answers (1)

Franck Jeannin
Franck Jeannin

Reputation: 6844

You are right. You also get slightly different behavior. I recently used .NET classic to debug a GetHashCode related issue. Is there a way to make .NET Core GetHashCode deterministic

Upvotes: 1

Related Questions