Repo / project restructurings

[zspitz]

Before:

• Can visualizers be written using .NET Core 3? This would allow Merge visualizer output assemblies into single assembly #80 without Costura, and Consider adding AdonisUI for visuals #51
• Can VS 2017 be supported this way? Do we need to?
  One possibility - multitarget .NET Framework and .NET Core; the .NET Framework version should be merged using Costura and packaged for VS 2017

ATM it seems that debugger-side dlls written in .NET Core for visualizers are not seen by Visual Studio. We'll have to do this in .NET Framework, and merge using Costura.

---

During repo restructure:

• Expression test objects
  • separate project within repo
  • add wiki page on ExpressionTreeToString
  • wrap as nuget package (#89)
    • project url should point to above wiki page
  • trivially enables Convert all tests against expression objects into a single TheoryData #88
• move library into separate repo -> ExpressionTreeToString
  • move Shared into ExpressionTreeToString
  • use test objects library to run tests
  • migrate to SDK project format; NRT
• visualizer
  • rename current repo, solution, projects to ExpressionTreeVisualizer
  • remove Visualizer.2017; merge Visualizer.Shared and Visualizer.2019 into ExpressionTreeVisualizer
  • migrate to SDK project format (Upgrade to SDK-style project #97); NRT
  • split off debuggee code into separate projects
    • build should go into separate subfolders based on target framework
    • ZIP up all files, preserving this subfolder structure
    • For .NET Framework debuggee, use Costura to merge into a single DLL
    • Check the possibility for other debuggee versions
  • create solution for CI; will build and run tests but not the "playground" projects; modify appveyor.yml
    • create a post-build project in the original solution, not the CI solution; copies the output DLLs to the relevant folders
  • merge library dll using Costura
  • use test objects library to run tests
• migrate wiki to new repos
  • add changelog, roadmap, solution structure, and contributing pages
• remove files from old repo; add links to new repos

After:

• visualizer
  • separate ExpressionTreeControl (displays viewmodel) from VisualizerWindow (manages DataContext using TransferData)
    • break dependency of Package project on Visualizer project; reference shared projects directly
  • MVVM, then Enable visualizer tests to be run by AppVeyor #79 can be done using the test object library
  • deploy viewmodels + views (including serialization models) as Nuget package
    • move all the code to a .NET Core 3.1 project (UI.Core); modifications made to this project
    • add a post-build step to copy all files into UI.Fx targeting .NET Framework
    • ideally, multitarget .NET Framework, .NET Core (.NET Standard?)
  • remove dependency on MultiSelectTreeView
  • create separate build output for VS 2019 -- ZIP file with subfolder structure for multiple frameworks -- and VS 2017 -- ZIP file with single dll
• Update external links -- RubberDuck, MS docs
  • https://github.com/agileobjects/ReadableExpressions/issues/47

---

Some more details:

domains:
serialization models
visualizer object source
view models + views
visualizer

visualizer:
serialization models into multitarget debuggee dlls
everything else into NET Framework debugger dll
	reference to some debuggee dll is required, for use of serialization models

wpf control library:
(deploy as nuget package)
serialization models + view models + views
	constructor for view model from actual type (not serialization model)

test projects reference wpf control library
	(it will have a dependency on WPF, use .NET Core 3)

[zspitz]

PR for MS Docs is here.