Why do packaged projects with the binary configuration set to Development request for network access when run (i.e., the Windows firewall notification appears) whereas those set to Shipping do not? I created a Blank Project without the Starter Content pack to test this behavior.
Development builds has a lot of debug features built in. And some of features are implemented as network services (likely for purpose of remote debugging), even if you going to use them only on your local machine. For example, Insights seems to work this way.
I see. It would be helpful to get a list of steps someone would have to take such that a Development build did not require access to the network (e.g., what sort of plugins and features they would have to disable).
At the very least, any advice for someone trying to modify a project so that their Development build doesn’t try to access the network?