Closed mburumaxwell closed 5 years ago
Hi mburumaxwell,
We are working on a migration guide. Here is a very short version of it: a. The Json schema in the twin: i. The attributes names/meaning remain the same for the most part. ii. None of the configuration is under a 'windows' node anymore (saved one level of nesting). iii. Error reporting is using a new schema. b. The UWP interface i. This version does not depend on sharing the Azure IoT Hub connection with a UWP application. ii. This means that users can get rid of the code in their UWP application that connected with the nt service (i.e. SystemConfigurator). iii. For cases where the UWP application relied on the SystemConfigurator, we are asking for customer feedback on what these cases are and we can work with them on resolving them one by one.
The new schema is not backward compatible as outlined in the first bullet. However, it is very close. It should require minimal changes on the Cloud Solution/Operator application part to adopt the new schema.
The device management client is a standalone service whose interface is Azure IoT Hub. You can still write your Azure application on the device using your preferred language. You might be referring to scenarios where the UWP application is invoking a device management functionality? If so, could you please outline what that functionality is? We'd like to work with you on understanding the scenario.
Also, feel free to contact me directly at gmileka at microsoft com for quick responses.
thanks, george
Hi,
Opening the iot-core-azure-dm-client repository states that the future is in this repository. I have a few questions: