If you get a parameter error message it means the D drive is being used by something else
Identify the tag/commit of the nuget package
Tag Method
If you go to Xamarin Forms on GitHub, you will notice that the Forms tags have a consistent naming scheme
RC is the initial release and SR marks each additional release. For example release-3.4.0-sr2 applies to 3.4.0.1029999
git checkout tags/release-3.4.0-sr2
Commit Method
Forms Releases lists the commits associated with each release
git checkout 588023e
Now you’re ready to step into the source code. Run your project and when you try to step into anything or view the call stack it’ll let you navigate to the files at d:/a/1/s
Working on a fix you want to submit?
The Control Gallery projects that are part of the main solution are a great place to setup and test your scenarios from.
If you submit a fix you’ll most likely need to add an issue here which gets loaded into the Control Gallery test runner.
Typically when I’m developing fixes I’ll start with loading my test cases inside the CreateDefaultMainPage method and then once I’ve reproduced and fixed the issue I move it over to an official UI test issue.
Compiling Issues
On windows everything should compile without needing to do anything
if you are getting errors try running git clean -xdf. Sometimes left over files from changing branches can cause issues
Current issues with multi targeting make VS Mac a bit trickier to work with.
Currently the Xamarin Debugger doesn’t support SourceLink style debugging. The internal wheels are turning on this and once it is ready Forms will add SourceLink support
Build scripts
Currently working on build scripts to help with nuget packaging and different build scenarios (https://github.com/xamarin/Xamarin.Forms/pull/5074)