AdminClint Rutkas [MSFT]
(Admin, Windows Developer)
My feedback
-
1 vote
-
5 votes
What SDK are you targetting? we need more information to help debug
-
1 vote2 comments · Universal Windows Platform » Dev Center + Microsoft Store · Flag idea as inappropriate… · Admin →
verifying, believe https://github.com/dotnet/corert/issues/5470 is the issue which is marked fixed. Verifying it is in 17134 SDK (April 2018 Update).
looking into it
-
9 votes2 comments · Universal Windows Platform » SDK - Tools + Templates · Flag idea as inappropriate… · Admin →
what parts of tshell make it interesting? What tools are you looking for here
-
5 votes21 comments · Universal Windows Platform » Desktop Bridge ('Centennial') · Flag idea as inappropriate… · Admin →
Markus, can you
- Run cleanup again
- Ensure the base image expansion is gone. These should be empty,
- dir C:\ProgramData\Microsoft\Windows\Images\
- dir C:\ProgramData\Microsoft\Windows\Images\Windows_InsiderPreview_DAC_16299
- If above not empty, then delete manually (might need to be admin and take ownership of the files first)
- Then run setup again and send us the log if it fails (crutkas@microsoft.com)@Markus, thanks for reminding me, pinging that thread again
thanks, we're looking into this right now.
Can you run this: we have a theory what may be causing this powershell command? Replace your pathToBaseImage with where your wim file lives
$pathToBaseImage = "C:\Users\jwhites\Downloads\Windows_InsiderPreview_DAC_16299.wim" # set this manually
$pathToBaseImage = (get-item $pathToBaseImage).fullname
$image = Get-WindowsImage -ImagePath $pathToBaseImage -Index 1
# Check for presence of CExecSvc to validate that this is a container base image.
$imageContents = Get-WindowsImageContent -ImagePath $pathToBaseImage -Index 1
if (!$imageContents.Contains('\Windows\System32\CExecSvc.exe'))
{
echo "missing \CExecSvc.exe"
}
if (!$imageContents.Contains('Windows\System32\CExecSvc.exe'))
{
echo "missing CExecSvc.exe"
} -
3 votes
Can you provide a repro?
@robloo, can you provide a repro on GitHub we can grab? we're having issues repro'ing it
passing it by the team.
-
2 votesworking on it · 2 comments · Universal Windows Platform » Desktop Bridge ('Centennial') · Flag idea as inappropriate… · Admin →
There is a workaround but it will require a small amount of work. two characters weren't not properly escaped [ and ]. Since you have an MSI, you'll have to regenerate that without those in the path.
Once you do that, the converter will work.This will be fixed in the next update.
-
1 vote
Bug has been filed. Currently being investigated. I’m marking this as “on backlog” due to that but I don’t have more of an update past that right now.
FYI: the VS community link discusses a workaround
-
76 votes13 comments · Universal Windows Platform » Dev Center + Microsoft Store · Flag idea as inappropriate… · Admin →
Can you include in this user voice entry the specific details of what is missing? we are working on improving these reports, and the more specific information we have about issues the more we will be able to add.
@dmitry, hockeyapp is different than Dev Center reporting. Soon with Visual Studio Mobile Center, they'll have better crash reporting / analytics as well for UWP.
-
4 votes1 comment · Universal Windows Platform » Windows Community Toolkit · Flag idea as inappropriate… · Admin →
I would highly suggest keeping this in sync with the Xamarin one.
-
1 vote1 comment · Universal Windows Platform » Web Browser Control APIs · Flag idea as inappropriate… · Admin →
Can you explain a bit more by what you mean here.
What is your target and min SDK and Windows. Build?
-
4 votes
Thanks for feedback! We are looking at addressing this issue for Fall Creators Update and improving the behavior. This behavior is to aid in boosting confidence in speech results.
what build of windows are you on?
-
343 votes56 comments · Universal Windows Platform » XAML/Controls/Composition · Flag idea as inappropriate… · Admin →
An always happy Friday as I just got the TFS complete email :) As this hasn’t hit an insider preview SDK, i’m going to mark this still as “working on it” still BUT … this will be coming to an insider build near you!
This item heart is markup extensions. There is one item that will not be there however that is relevant to markup extensions, IServiceProvider. I created a new item for that but we are working on this item [https://wpdev.uservoice.com/forums/110705-universal-windows-platform/suggestions/19416094-iserviceprovider-for-markup-extensions-for-wpf-par]. We have created a new one and we are working on that (that includes IProvideValueTarget and INameScope) but feel we have enough to ship this and mark this larger work item done and we do point out in reference to more work items need to happen, namely the work around IServiceProvider.
Also XamlServices.Load / Save isn’t directly related to markup extenstion so we’re viewing that…
@geert, yes, W10M will be getting it as well.
@Mike-EEE, please read the first and second item in our posting guidelines. https://wpdev.uservoice.com/knowledgebase/articles/778137
@mike, not everything is on github. That is one signal of many. We can and do a lot of analysis. That is why we know 70% of all nuget packages should be ready for .NET Standard 2.0.
Per Christophe, we’re gathering scenarios to make the right choices in implementation and prioritization. As of now, you haven't provided a scenario for YOUR applications.
@Mike-EEE providing scenarios helps us prioritize and understand edge cases. We're trying to drive the conversation. This is totally part of that conversation. Christophe is part of the XAML team :)
@mike, We are keeping one request per topic as well. I can't promise everything will be in here as it is being spec'ed out currently as a lot is in that list. More to share soon.
-
18 votesworking on it · 3 comments · Universal Windows Platform » XAML/Controls/Composition · Flag idea as inappropriate… · Admin →AdminClint Rutkas [MSFT]
(Admin, Windows Developer)
shared this idea
·
-
8 votes
HttpListener is part of .NET Standard 2.0. Once UWP will be updated to support .NET Standard 2.0, it will gain this capability. I don’t believe we’ve shared any timelines for this update on UWP yet.
Immo Landwerth,
Program Manager .NETI'm asking when this will hit a public SDK branch.
-
6 votes14 comments · Universal Windows Platform » Sensor / Bluetooth / Printer / Settings APIs · Flag idea as inappropriate… · Admin →
Can you go more into the scenario on how you’d use this API?
Issue here is the "why" and the scenario around the need for the API. Also what about all the other devices that may act differently. At a platform level, how would this work for a Surface Hub versus a desktop vs a laptop vs a HoloLens vs an Xbox?
Understanding the why and the scenario around why you're asking for this helps aid in coming up with a solution that is appropriate for the platform.
Thanks!
That sounds like an OS feature request, how would you as a developer use this.
Your feature also suggests that a device would have multiple sensors below to get the zones.
-
3 votes2 comments · Universal Windows Platform » Desktop Bridge ('Centennial') · Flag idea as inappropriate… · Admin →
Hi, we think we know what is causing this but can you provide a repro [GitHub totally works] so we can be sure we can trace the issue properly?
Thanks!
@Fireflower, can you send me an email, crutkas@microsoft.com?
-
55 votes10 comments · Universal Windows Platform » XAML/Controls/Composition · Flag idea as inappropriate… · Admin →
Tim Heuer did a quick write up. Keeping it open until the documentation is on Docs.
https://github.com/timheuer/type-converter-sample
http://timheuer.com/blog/archive/2017/02/15/implement-type-converter-uwp-winrt-windows-10-xaml.aspx@Rolf - To support older versions of Windows 10 would still require a system update :) Most devices have been upgraded to Anniversary Update and we're great pickup already for Anniversary Update. I'd be willing to bet you'll see a similar adoption curve.
-
2 votes1 comment · Universal Windows Platform » File IO / Data Store APIs · Flag idea as inappropriate… · Admin →
Great idea, can you explain your payload a bit that causes you to go above 100kb? Having use cases and scenarios is extremely helpful
-
16 votes11 comments · Universal Windows Platform » Dev Center + Microsoft Store · Flag idea as inappropriate… · Admin →
If you believe you can massively profit from it, why would getting a company account be a blocker?
ok, i now understand what the ask here is. You want non-Company based accounts to have access to restricted APIs.
Reason being is you're asking for a restricted ability to help protect end users. If you feel you can profit from adding that ability, create a company account and do the extra few steps to be verified. https://docs.microsoft.com/en-us/windows/uwp/publish/opening-a-developer-account
I'll update the title
Did you see https://docs.microsoft.com/en-us/windows/uwp/packaging/app-capability-declarations. Talks about getting permission.
Says anyone can request access for it.
This should be possible for side loaded apps. What restricted API are you trying to use?
We created a bug on this. thank you for making us aware