Here are my 2 cents

Approach 1: synchronizing the app in the SDK with the showcase app
Pros:

• Very easy to debug SDK changes
  Cons:
• An extra step is required to syncronize the showcase app with the example app.
• When we synchronize the app, we can synchronize everything but the `csproj` files.
  • If we synchronize them as well, then we have to change all the dependencies from `nuget` to `project reference`
  • If we automatically parse the `csproj` to change the dependency automatically, we end up depending on `csproj` structure. If in the future it will change, we will have to change accordingly.
  • Again, if we parse and change it in a script, everytime we will add/remove/rename a module, we will have to update the script as well

Approach 2: using a local repository to override remote dependencies
Pros:

• No changes required to any project
• Standard way to override dependencies with no yet published deps
  Cons:
• An extra step is required to publish the dependencies locally. That can be done usually standard tools from VisualStudio/.NET.
• We have to verify if this works