Consider merging the microsoft/dotnet-framework-docker-samples GitHub repo into the microsoft/dotnet-framework-docker GitHub repo

[MichaelSimons]

The primary motivation behind this change is visibility. The belief is that having all assets related to the microsoft/dotnet-framework Docker repo within one GitHub repo will help increase the visibility of everything. If a user navigates to from microsoft/dotnet-framework to the microsoft/dotnet-framework-docker GitHub repo to view the Dockerfiles, there is a higher chance they will see the samples if there are within the same repo. Having the samples in the same GitHub repo as the Dockerfiles will also help increase the visibility of incoming issues and PRs related to the samples.

The samples do cover usage scenarios beyond microsoft/dotnet-framework. For example the samples cover aspnet and wcf. This could be viewed as a positive as ASP.NET and WCF are based on the full .NET FX images. Seeing the ASP.NET and WCF samples could help bring visibility to the fact that the those images exist and are based on the .NET FX images.

[MichaelSimons]

This was addressed by microsoft/dotnet-framework-docker#126