I want to identify the current profile of windows phone.Is it is silent/ring.How can I check it.Please give suggestion.
This is not possible with the current Windows Phone SDK.
You can vote for this API to be added to a future version of the SDK here: Extend the API to query phone volume and vibration settings, maybe even set them.
As of wp SDK 8 you can't, nor can you adjust the volume or view/change current profile.
see this link
You can do these sort of things with windows store apps so perhaps it will come with the blue.
Humm seems I took to long to post but as olivier stated its high on the wanted list
user1021583 have you thought about running back over your questions and marking answers? you seem to have a lot of questions and none are marked as answers
Related
I have some users who have added some devices and I don't want to register them with as the apple developer device or have them part of the provisioning profile. Is there a way to remove unprovisioned apple devices? I am getting dangerously close to the 100 mark and I have 1 device that I do need to register with the app center. The alternative question would be is there a way to update the provisioning profile without letting app center do the registration?
Any help would be appreciated
As of today, there is no way to do either of things mentioned in my question. The AppCenter team is going to be looking at adding these features in the near future.
Follow the feature request here:
https://github.com/microsoft/appcenter/issues/951
You can remove devices. You have to go to Account settings -> My Devices -> choose a device and remove it.
This may not work for everyone but I was able to work around this limitation of AppCenter by deleting the Tester from the Distribution Group. The Unprovisioned devices associated with that Tester were also removed from the Distribution Group.
There is a new option for the End User in Windows 10 Creator's Update Edition. The End User can change properties for an EXE on the compatibility tab to "Override High DPI Scaling Behavior" and set it to System (Enhanced). I tested it and it works well for some classic win32 apps.
I want to to do this by code through an API call or through the manifest. There is no information on that. Is that possible?
From the comment I got, it want to clarify that this is a NEW CREATORS UPDATE FEATURE and I particularly want to know how to set the "SYSTEM (ENHANCED)" choice for override feature through manifest or code.
I found the answer in another SO post:
Enhanced system DPI scaling with VS2017
The correct clue is to investigate the new GDI Scaling manifest that is vastly improved in Creator's Update. That is used in System (Enhanced) setting.
None of the answers or comments came close. They kept referring to old articles. Moreover, someone marked the question negative:( Sad.
DPI_AWARENESS_CONTEXT_UNAWARE_GDISCALED is a now a valid DPI_AWARENESS_CONTEXT in the latest Windows 10 SDK headers (17134 as of this writing), in windef.h:
define DPI_AWARENESS_CONTEXT_UNAWARE_GDISCALED ((DPI_AWARENESS_CONTEXT)-5)
So you should call IsValidDpiAwarenessContext and SetProcessDpiAwarenessContext to take advantage of GDI Scaling at runtime, if you wish to avoid having to do this in the manifest.
This confirms that gdiScaling is mutually exclusive from Per monitor V2.
The details are covered in this blog post:
<dpiAware>True/PM</dpiAware>
<dpiAwareness>PerMonitorV2, PerMonitor</dpiAwareness>
For more details on various manifest issues, see Manifest Madness
I've started the process of porting over the toolkit version myself today and want to see if anybody has done this previously. I haven't been able to find resource off of the microsoft forums. I noticed one person has done this here or at least is part way into porting.
I'll update with specific technical difficulties as I go along.
Seems like something a lot of people would need to use in their universal phone apps since its a part of the design practices for wp development.
I saw the commercial library for iAd's from Monte but he isn't developping it anylonger due to the coming of InnerActive Ads in Livecode, right? So, I have created an InnerActive account and tried the only lesson I found on Livecode Lessons. That didn't work. So I posted a comment there which is awaiting moderation for quite some time now. I also mailed Inneractive, got a ticket replied, but no answer from them either.
If anyone has Ads with Inneractive running please tell/show us how you did it. I am calling mobileAdRegister with my appID and that seems okay. Then I try mobileAdCreate and mobileAdSetTopVisible and 'the result' tells me 'could not create ad'.
Dictionairy then tells me the app does not have Internet permissions or the registered app key is not valid. But I do check for internet connection and I'm sure I'm using my valid appID..
Regards, Amsterfrank
I have tested ads in the current release of LiveCode and they do indeed seem to be broken.
The LiveCode quality control team is aware of this and are currently investigating what could be the cause of this. A report on this issue can be viewed here-
http://quality.runrev.com/show_bug.cgi?id=11224
A workaround for now is to use an older version of LiveCode. After running a few tests, the last version of LiveCode that does not exhibit the mobile ad bug is LiveCode 6.0.0. This is available to download from here-
http://downloads.livecode.com/livecode/
With that being said, I would recommend holding off until the issue is resolved in a more current releases as there have been many bug/enhancements to LiveCode since 6.0.0
According to http://support.microsoft.com/kb/883792 , MS can detect installed AV using either WMI or a manual method involving registry keys that MS knows about. Is there an API to access this functionality?
This Google search yields this MSDN documentation which appears to be what you're looking for, the Windows Security Center API. The documentation says Vista only, but I believe this API is also available through the Windows XP SP2 SDK.
If you can't find documentation for it and you want to do some manual digging, you can try executing Process Monitor from SysInternals and then launch the Security Center. It'll show you what keys are read, and what files are accessed.
You can use the Win32 Registry access APIs if you knew the keys.