Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, November 5, 2017 4:37 PM
I need to be able to shutdown/restart and set the timezone of an IOT device through C# and I've found this information which is exactly what I want (/en-us/uwp/api/Windows.System.ShutdownManager#Windows_System_ShutdownManager_BeginShutdown_Windows_System_ShutdownKind_Windows_Foundation_TimeSpan_)
If I try to update my manifest like it says, it doesn't like the iot namespace, and I can't access these functions in code either.
I'm guessing I need to install this SDK, but can't seem to find anything about it, and the link on the docs above don't specify anything
All replies (11)
Tuesday, November 14, 2017 3:39 AM âś…Answered
Just downloaded the IOT samples form GitHub. I tried to load the IoTCoredDefaultApp, but vs 2017 tells me there a problem loading the project file ...\IoTCoreDefaultApp\IoTCoreDefaultApp.csproj : error : Object reference not set to an instance of an object.
So, I can't even open this project, let alone compile it!
I did however seem to fix the issue, seem that you have to only reference the windowsIoT extension v10.0.10586.0, the other two versions I had on my system seemed to cause issues. The system management capability also showed up in the UI, and would added it without having to edit the xml.
Monday, November 6, 2017 6:25 AM | 1 vote
Dear friend,
When you setup the Visual Studio, have you installed the latest Windows 10 SDK and Universal Windows App Development Tools, this is very important.
Please refer to the doc on windowsondevices.com
https://developer.microsoft.com/en-us/windows/iot/getstarted
Keep Fighting
Monday, November 6, 2017 2:30 PM
I reinstalled everything (updated). I think the problem was actually having to add a reference to the extension, I was looking for a NuGet package to add as a reference.
Wednesday, November 8, 2017 2:12 AM
After adding the reference to the extension package, I was able to add the code to access system management functions, but it still gives me an error when I add <iot:Capability Name="systemManagement" /> to the Capability section of the Package.appxmanifest file.
How do I fix this?
Wednesday, November 8, 2017 2:28 AM
Dear friend,
Please check your Windows 10 IoT Core version and Windows 10 SDK version. Make sure that they are updated to the latest version.
Keep Fighting
Wednesday, November 8, 2017 2:30 AM
I ran the 2017 installer and it updated everything, What is the latest version? I'm referencing 10.0.14393.0
Wednesday, November 8, 2017 2:33 AM
Hello,
Try to install Windows 10 SDK for Fall Creators Update (10.0.16299.15) from here: https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk
Keep Fighting
Wednesday, November 8, 2017 2:35 AM
Yeah, but that would be for the windows 10 creators update, this is code that will be run on an IOT device, not a windows 10 creators version, and it needs to work with the current IoT release of win 10.
Wednesday, November 8, 2017 2:38 AM
When I go to install this, I get a message box that I need to uninstall the 10.0.16299.15 update before installing the latest version of the kit, so that would lead me to believe that I do have the latest sdk installed.
Wednesday, November 8, 2017 3:21 AM | 1 vote
I find a sample of <iot:Capability Name="systemManagement" /> here:
https://developer.microsoft.com/en-us/windows/iot/samples/externalprocesslauncher
please download form github and try.
I compile this project with no error.
Keep Fighting
Wednesday, November 15, 2017 2:01 AM | 1 vote
Hi, ebarke
The IoT sample in GitHub is targeting 16299. Windows SDK Reference is version 16299. So if you have not installed Windows 10 SDK v16299, the project can not open and compile. You can update your visual studio 2017 to latest version and install related Windows 10 SDKs.
Best Regards,
Michael
MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].