Packaging a .NET Core application & pbuilder

[Alistair J R Young <avatar@arkane-systems.net>]

I'm currently working on packaging a .NET Core utility for contrib (ITP here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968331; current version of the package here: https://mentors.debian.net/package/systemd-genie/ for those interested), and am in the stage of dotting Is and crossing Ts right now, and I have a best practice query, if you'll indulge me.

I have been making sure my source package will build properly using pbuilder, which it does, but it does so with two caveats:

1. I have a hook script (see below) whose job is to get the dotnet-sdk-3.1 package from Microsoft's repository into the base tgz; and 

#!/bin/sh
apt-get install -y wget ca-certificates
wget https://packages.microsoft.com/config/debian/10/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
dpkg -i packages-microsoft-prod.deb
rm packages-microsoft-prod.deb
apt-get update
apt-get install -y dotnet-sdk-3.1

2. I run pbuilder with the --use-network yes option, since the .NET Core build process expects to be able to pull the referenced NuGet packages at build time.

Are these acceptable caveats for a source package in contrib, or do I need to find ways to eliminate one or both? Is there any established guidance for packaging .NET Core apps (I looked, but have been unable to find any) that would cover this?

Thanks and regards,

Alistair