You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**NOTE** some ISPs have been know to use web filtering software that has caused issues with git repository cloning, if you experience issues cloning this repo please review <https://help.github.com/en/github/authenticating-to-github/using-ssh-over-the-https-port>
72
72
73
73
## Building in Visual Studio
@@ -86,6 +86,9 @@ Before opening our .sln/.slnf files in Visual Studio or VS Code, you need to per
86
86
> :bulb: Pro tip: you will also want to run this command after pulling large sets of changes. On the master
87
87
> branch, we regularly update the versions of .NET Core SDK required to build the repo.
88
88
> You will need to restart Visual Studio every time we update the .NET Core SDK.
89
+
> To allow executing the setup script, you may need to update the execution policy on your machine.
90
+
You can do so by running the `Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser` command
91
+
in PowerShell. For more information on execution policies, you can read the [execution policy docs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy).
89
92
90
93
2. Use the `startvs.cmd` script to open Visual Studio .sln/.slnf files. This script first sets the required
0 commit comments