dotnet-installer/TestAssets/TestProjects/TestMicrosoftCSharpReferenceMissingFramework/project.json

{
  "version": "1.0.0",
  "dependencies": {},
  "frameworks": {
    "netcoreapp1.0": {
      "imports": "dnxcore50",
      "dependencies": {
        "Microsoft.NETCore.App": "1.0.0-rc2-*"
      }
    },
    "netcore50": {
      "dependencies": {
        "System.Private.Uri": "4.0.1-rc2-24022"
      }
    },
    "net99": {
      "dependencies": {
        "Microsoft.CSharp": "4.0.1-rc2-24022"
      }
    }
  }
}
Fix duplicate dependency issue (#2597) * Fix duplicate dependency issue If a package has the same name as a framework assembly in the dependency graph, we usually replace it with the framework assembly if the package provides no assets. If the framework assembly wasn't resolved, it would skip this logic and end up adding dupes to the list, which blows up later on. This is a tactical fix to solve the issue, we need to do some more thinking to determine how we want to resolve conflicts between framework assemblies, packages and dlls with the same name. 2016-04-21 16:05:55 +00:00			`{`
			`"version": "1.0.0",`
			`"dependencies": {},`
			`"frameworks": {`
			`"netcoreapp1.0": {`
			`"imports": "dnxcore50",`
			`"dependencies": {`
			`"Microsoft.NETCore.App": "1.0.0-rc2-*"`
			`}`
			`},`
Fixed netcore50 package based frameworks (#2630) 2016-04-22 04:47:20 +00:00			`"netcore50": {`
			`"dependencies": {`
Updating CoreFX to rc2-24022 2016-04-22 15:58:43 +00:00			`"System.Private.Uri": "4.0.1-rc2-24022"`
Fixed netcore50 package based frameworks (#2630) 2016-04-22 04:47:20 +00:00			`}`
			`},`
Fix duplicate dependency issue (#2597) * Fix duplicate dependency issue If a package has the same name as a framework assembly in the dependency graph, we usually replace it with the framework assembly if the package provides no assets. If the framework assembly wasn't resolved, it would skip this logic and end up adding dupes to the list, which blows up later on. This is a tactical fix to solve the issue, we need to do some more thinking to determine how we want to resolve conflicts between framework assemblies, packages and dlls with the same name. 2016-04-21 16:05:55 +00:00			`"net99": {`
			`"dependencies": {`
Updating CoreFX to rc2-24022 2016-04-22 15:58:43 +00:00			`"Microsoft.CSharp": "4.0.1-rc2-24022"`
Fix duplicate dependency issue (#2597) * Fix duplicate dependency issue If a package has the same name as a framework assembly in the dependency graph, we usually replace it with the framework assembly if the package provides no assets. If the framework assembly wasn't resolved, it would skip this logic and end up adding dupes to the list, which blows up later on. This is a tactical fix to solve the issue, we need to do some more thinking to determine how we want to resolve conflicts between framework assemblies, packages and dlls with the same name. 2016-04-21 16:05:55 +00:00			`}`
			`}`
			`}`
			`}`