Regarding Setup guidelines [ASP .NET CORE]

[ks1990cn]

Hi,

I've found guidelines which are mentioned in following:
https://github.com/getsentry/sentry-dotnet/blob/13c3ee93e889539db6a6dc45871d800a28d5dea3/CONTRIBUTING.md

While trying to setup, here are questions:

1. dotnet workload restore, needs to be run in powershell at root path where sln files are present?

2. If yes, it was taking so long than expected and no activity was observed after hitting enter.

If I setup the code, will I be able to run complete application locally including the monitoring client application?

[jamescrosswell]

dotnet workload restore, needs to be run in powershell at root path where sln files are present?

You can optionally pass a solution file as a parameter to dotnet workload restore. If you're in the repo root directory, you can run sudo dotnet workload restore Sentry.sln (or just dotnet workload restore Sentry.sln on Windows).

If yes, it was taking so long than expected and no activity was observed after hitting enter.

Yeah workload restore can be slow. You only have to do this when setting up the repo typically (or if target frameworks get added to the repo, which is pretty infrequent).

If I setup the code, will I be able to run complete application locally including the monitoring client application?

Yeah I can debug any of the samples and step into the Sentry source code with breakpoints etc. You could do that without cloning the repository as the Sentry NuGet packages are fully symbolicated with Source Link, so Visual Studio and Rider will download the source code and let you step into it.

The main advantage of cloning the Sentry repository and running it locally is that you can then also make changes to the source code and test those out (either with the Sample applications we provide or with your own application).