Setting up your environment for development

Pulling down the source code

The PnP Framework source code lives in the https://github.com/pnp/pnpframework repository. If you want contribute to it you'll need to issue pull requests against the dev branch and for doing that, you need to first fork the repo:

  • Click on the Fork button (top right on the https://github.com/pnp/pnpframework home page)
  • Create a fork in your account or organization of choice
  • Pull down your forked version via:
    • Clicking on the green Code button and copy the git URL
    • Ensure you've installed a Git client (e.g. https://git-scm.com/downloads)
    • Open your command prompt and navigate to the folder where you want to pull down the source code (e.g. c:\github)
    • Pull down your forked repo via git clone <the copied git url>

If you want to update your forked repo then you can either use the GitHub UI or command line, check out https://medium.com/@sahoosunilkumar/how-to-update-a-fork-in-git-95a7daadc14e for more instructions

Setting up your development environment

I want to use Visual Studio for development

Using Visual Studio requires you to:

I want to use Visual Studio Code for development

Using Visual Studio Code requires you to:

  • Download and install Visual Studio Code: https://visualstudio.microsoft.com/free-developer-offers/
  • Ensure you've installed the .NET 7.0 SDK
  • Open Visual Studio Code and install these extensions (click on the Extensions button in the vertical toolbar and search for it, then click on the Install link) and close it again once done
    • The C# extension (mandatory): this extension brings support for compiling and debugging C#
    • The .NET Core Test Explorer (optional): this extension always you to easily navigate the test cases and run a group of test cases
  • Navigate to the ./src/lib folder, right click and choose Open with Code or alternatively when using command line type code .

Making changes and testing the new code

The recommended approach for making changes and testing them is by writing the appropriate unit tests (see the Writing tests article).