- Prior to this change `outputPath` would always default to `null` which didn't work well with `VisualStudio` tooling. The tooling enables the user to specify a project's `outputPath` but more importantly defaults the project's `outputPath` to the root directory (instead of the project directory).
Modified the reporting channel factory to have a create for the adapter and a create for the runner channel. Also added an event to the create runner channel that people can listen and be notified when a test runner channel was created. I use this event to give the message handler access to the runner channel.
Added the new message handler to DotnetTest.
The change to default to Portable PDB by default has broken a number of downstream consumers. Moving back to full PDBs by default on Windows.
This leaves the option for portable PDB in place. Hence you can still enable it via the following entry in project.json:
``` json
"compilationOptions": {
"debugType": "portable"
}
```
- Handle unresolved projects better in build
- Move unresolved package marking to the resolver
- Added ToString to LibraryKey for easy diagnosis of errors
Adding an explicit reference to System.Net.NameResolution in our dotnet-projectmodel-server.Tests. The current build of Roslyn references an old version of System.Net.NameResolution which is the version that gets used during the test. Explicitly referencing the current CoreFX version for now. This should be reverted when the underlying bug gets fixed, or Roslyn moves to a newer CoreFX version.
Update .exe's project.json Target Framework from dnxcore50 to netstandardapp1.5.
Update .dll's project.json Target Framework from dnxcore50 to netstandard1.3.
Adding workaround for DataContractSerialization to src\dotnet\project.json to fix crossgen issue.
Build 23901 has a dependency issue that doesn't allow the runtime.any.System.Private.DataContractSerialization
package to be restored. When we move to a new build of CoreFX we should take this workaround out.
VS 2015 Update 2 CTP has been released which has support for debugging portable PDBs. Now is a good time to make the transition so a) we can root out any remaining issues with portable PDBs and b) have larger dogfooding of the VS debugging experience here.
closes#704
