Xiangzhi Sheng 90f29c79cb Improve the fault tolerance of device connection failure ... Currently, the simulator may meet connection failure randomly. It will cause the device failed to send and recevie any message. IoT Hub team suggested to re-create the DeviceClient object as a workaround. But it looks not enough, since sometime the it may take quite long time the reconnect to IoTHub even with the new created DeviceClient. In this code change, we are going to improve the fault tolerance from angles below: 1. Upgrade the Device Client SDK to latest version 2. Add simulator scope check. If 50% devices was found in status "down", the whole simulator process will restart. It will happen only if the simulator was running as a WebJob in cloud environment. 3. [BugFix] Use “finally" statement to ensure the transport object was released 4. Add more trace log		2017-04-13 10:42:52 +08:00
..
Cooler	Set the default value of TelemetryInterval to 15 seconds	2017-02-22 15:17:17 +08:00
DataInitialization	Refine code style by auto-format	2017-02-22 10:53:09 +08:00
Properties	Splitting RemoteMonitoring WebJobs into two project	2015-10-19 14:27:36 -07:00
SimulatorCore	Improve the fault tolerance of device connection failure	2017-04-13 10:42:52 +08:00
BulkDeviceTester.cs	Restart crashed simulator task	2017-01-16 17:03:38 +08:00
DeviceManager.cs	Improve the fault tolerance of device connection failure	2017-04-13 10:42:52 +08:00
Program.cs	Improve the fault tolerance of device connection failure	2017-04-13 10:42:52 +08:00
Simulator.WebJob.csproj	Improve the fault tolerance of device connection failure	2017-04-13 10:42:52 +08:00
SimulatorModule.cs	[BugFix] Default sample devices were not set as "Running" by default	2016-12-22 17:59:00 +08:00
app.config	Improve the fault tolerance of device connection failure	2017-04-13 10:42:52 +08:00
packages.config	Improve the fault tolerance of device connection failure	2017-04-13 10:42:52 +08:00
settings.job	Splitting RemoteMonitoring WebJobs into two project	2015-10-19 14:27:36 -07:00