Posted 11 Jan 2012
Link to this post
Yes, If you check of that box you should not have the debugger break on our internal exceptions (I wish there were some way we could hide this, but apparently not, see http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2486532-allow-the-debugger-to-stop-on-user-handled-and-thr)
As far as internet connectivity, then yes, the device/machine where our machine is running needs some kind of internet access. By default we try to get to our servers (at eqatec-monitor.com) using http, port 80 and any default proxy settings on the machine/device. If you are aware of any other settings that are needed to access the internet, for instance utilizing the connection to your developer PC) then that has to be configured. You can do so using the Proxy setting when creating the monitor instance (see http://api.eqatec.com/analytics/dotnet/html/P_EQATEC_Analytics_Monitor_AnalyticsMonitorSettings_ProxyConfig.htm)
This is usually a configuration issue on the device. A good preliminary test is checking if the device is able to connect to the internet (e.g. google.com) using e.g. the standard browser if available or using a very simple application that just creates a WebRequest and gets a response. Once the device is able to connect, our monitor library should be able to use same connection. Of course you may have internal router policies etc. that only limits connections to certain internet addresses. We use standard http and port 80 since that has the highest chance of being permitted inside corporate networks but your specific setup may be different.
Hope this helps. If you need further details or assistance, please don't hesitate to get back to us