The Quino packages themselves are only available from an authenticated Azure NuGet feed. The following URL provides the packages (but you can't browse directly to it).
See How to use Authenticated NuGet Feeds for more information on including this URL in NuGet on a client.
Quino-Windows solutions depend on public packages available at Nuget.org. This source is configured by default in Visual Studio.
The Winform packages in the
Quino-Windows solution also depend on
DevExpress components. Products that depend on these packages will have to obtain a license and authenticated/licensed NuGet feed.
Symbols & Sources
The most recent 7.x and all 8.x versions incorporate SourceLink. Visual Studio will automatically download symbols (PDB files) and sources, as needed.
See Setting Breakpoints in external code under "Techniques" for additional information on debugging into Quino.
Cannot download from Azure
If there are authentication issues for some developers, then an alternative is to download the packages from the Azure web instead.
- Download the published artifacts associated with the Pipeline output of interest (e.g. 7.3.0 artifacts)
- Download individual packages from the Artifacts page
A developer can then drop downloaded packages into a folder and make them available as a local NuGet feed.
Visual Studio still loads sources from a local folder instead of requesting them from Azure/SourceLink.
The solution most likely still has debugging paths configured from versions of Quino before SourceLink were supported.
- Open the Solution Properties
Debug Source Files
- In the
Directories containing source code, clear out any Quino-related paths
- Restart the debugger
Does not download
If Visual Studio doesn't download anything at all or doesn't stop on any exception location other than in the solution's own code.
Check the following debugging settings:
- Switch to the
Enable Just My Code