Short, sweet and useful. Thanks!
Strong Authentication: Building Apps That Leverage Virtual Smart Cards in Enterprise, BYOD, and Consumer EnvironmentsJul 06, 2013 at 11:52 AM
You are correct, I am waiting for smartcard access from a WinRT API.
Is it a matter of policy that it is prevented, or a lack of resources?
Strong Authentication: Building Apps That Leverage Virtual Smart Cards in Enterprise, BYOD, and Consumer EnvironmentsJun 27, 2013 at 4:07 PM
Please address if you can send an APDU to a real smart card in a reader similar to the API SCardTransmit().
According to Windows Phone API reference there are 11,000 Windows Runtime API members supported on Windows 8. The phone supports a subset of 2,800. The Phone also has 600 members not supported on Windows 8.
Search for "Windows Store Apps" "Windows Phone 8" "API is not implemented" to see some examples.
Windows Phone 8 and Windows 8 platform comparison shows the libraries supported in the Common native API: DirectX 11.1, XAudio2, MediaEngine, STL, CRT, and WinSock.
Really a great session. I especially like:
- isocpp.org as a unifying website.
- String literals
- Initializer lists
- "await" for C++
- Bjarne's book is coming soon.
Something things I don't like:
- "Windows Store Apps" documentation that omits how to achieve a goal in C++.
- The documentation assumption that you are individually familiar with C# and XAML when explaining how to combine C++ and XAML.
- Sridhar Poduri's book "Programming Windows 8 Apps using Microsoft Visual C++" is not available yet.
- Key "Windows Store Apps:" functionality implemented in .NET rather than in language independent that C++ can use.
Some questions I have:
- I'm not sure how to search JUST the Microsoft documentation that pertains to C++ and "Windows Store App" development for a keyword. (I could in a PDF or windows help file).
- I am not sure yet if you really can take ANY C++/CX and XAML program from Win8 to Win Phone 8. There usually is some fine print.
I would be interested in comments from Mr Stroustrup on these C++ compiler extensions by Microsoft:
1) The use of "Ref" classes
Person^ p = ref new Person("Clark Kent");
and their declaration.
2) The use of Platform Strings at the library interface
using namespace Platform;
std::wstring wstr1( L"Test" );
String^ str10 = ref new String( wstr1.c_str(), wstr1.length() );
Will there will be an compiler that produces ARM code that supports these extensions?
My adoption decision depends on:
1) Better documentation on how to use the combination of XAML, WinRT and C++/CX.
2) Platform targets. My current belief is that the Windows phones will never allow C++, tablets will be Win 8, and WinRT won't apply to the installed base of Windows 7 computers.