today i installed the new windows phone 8 sdk (w8phone sdk)... tried to include some of my base classes
from windows 8 apps... same core they say... but whoops?
no Windows.Security.Cryptography?
I used the SymmetricKeyAlgorithmProvider for end-to-end encryption of serialized data with WCF Services.
(http://msdn.microsoft.com/en-us/library/windows/apps/xaml/br241537.aspx)
Seems using .NET Framework Encryption is quite proprietary to the platforms/devices.
Anyone some advises for same functionality on Windows 8 Phone?
Thanks.
EDIT/UPDATE
I solved the problem by porting http://www.bouncycastle.org/ to separate Windows 8 and Windows Phone 8 Libs and a slight changed version of the little BC Engine from here: Encrypt/Decrypt using Bouncy Castle in C#
Windows.Security.Cryptography is a WinRT API. Windows Phone 8 still being mostly Silverlight uses the APIs from System.Security.Cryptography, which does not include the SymmetricKeyAlgorithmProvider.
You can still use the AesManaged API on Windows Phone, which may, or may not, be enough for your purpose.
Windows.Security.Cryptography is most likely just the x86 COM abstraction of the Microsoft cryptolib, which is the same as most of System.Security.Cryptography on .NET 3.5-4.0
Related
I've been doing a lot of reading of Microsoft blog posts relating to .NET Core 3, but none of them mention the Windows version requirements, which is leading to a lot of comments querying whether Windows 7 will be supported?
I did find a quote from Rich Lander in this theregister.co.uk article:
Lander says "Windows 7 is
supported with .NET Core 2. We haven’t locked the OS matrix for .NET
Core 3, but we don’t have any specific plans on changing it."
Is there a definitive statement on Windows 7 support .NET Core 3 from Microsoft anywhere?
PS: I appreciate that Windows 7 is End of Life, but I'm also mindful that XP's extended support period was lengthened. Judging by the number of our clients who are still running Windows 7 it seems possible that Win 7 might get an extension too.
Just came across this table in the dotnet core GitHub repo which suggests that Windows 7 is indeed supported for .NET Core 3.0:
Windows 7 is also still supported in NET Core 3.1
And in .NET 5
And in .NET 6
And in .NET 7
You can also run .NET Core on Windows 7 SP0 if you install KB2533623 (~1MB).
Tested it on .NET 5.0 self-contained WPF application. Works fine.
It is even better. According to dotnet core repo the upcoming unifying .NET 5 will support Windows 7 SP1 and 8.
I would like to use the UWP clipboard api of windows 10 in my windows phone 8.1 winrt app.
I couldn't load the Winmd file by using Assembly.Load(string assemblyname) method.
Is there another way to use it. Please some one point me in the right way. I'm not very experienced in reflection.
Thank you
No way to use functionality from the Windows 10 SDK in an app using the Windows 8.1 SDK.
Is there a way to integrate Microsoft Band with an existing Silverlight Windows Phone application? I have tried implementing an wrapper Windows Runtime Component for band functionality, but that does not seem to work.
The Microsoft Band SDK does not support Silverlight-based Windows Phone applications, only Windows Phone 8.1 (WinRT) based applications.
There is a build for Windows 8.1 but it was not build as a universal PCL. Contacted support but they said to ask here, to get a response from the developers.
NOTE: by universal I mean, Windows Store universal, that work on WP8.1 and W8.1
The latest GNSDK for Mobile release should support WP8.1. Please download the one with platform "Windows Phone 8."
Gracenote SDK is a native library. It is not an application. Just like any other third party library (like sqlite - check https://sqlite.org/download.html),
it porvideds winrt and windows phone libs.
How do you build the library to run on phone and winrt both ? Can you post link from MSDN on how to do it ?. I dont think you can do this for libraries which has native component/s to it.
Gracenote window phone libs are built using visual studio 2012 and should work for both windows phone 8.1 and windows phone 8.0.
I read that WinRT does not have a layer that support .NET applications here: seek to 1:55 seconds http://www.youtube.com/watch?v=TI0ABjSKAGU
I also read that .NET 4.5 framework provided support for Windows Runtime here Differences between .NET 4.0 and .NET 4.5 in High level in .NET.
Here is my confusion:
Does that mean that I can run my .NET application on Windows Runtime now? How WinRT supports my .NET app? I have an idea that .NET can only be used to create web applications which are usually consumed using webbrowsers. If WinRT had a browser then why WinRT had problems in running my .NET application?
WinRT is an OS/layer which is installed on ARM based machines and tablets (Surface tablet).
I want to know what type of .NET application I will be developing for WinRT given that I now have support for Windows Runtime in .NET 4.5 framework.
If you are developing an application for the Windows Store, you will be developing it using the Windows Runtime (WinRT). That is the only option today. After you've made that choice, you can choose between a C#/XAML or a HTML/WinJS user interface. You don't "choose" .NET 4.5. You're selecting the Windows Runtime.
There are two distinct platforms, and overlapping terminology:
Windows Runtime (usually abbreviated as WinRT) and .NET
The .NET platform has existed and been available for production development purposes since the release of Visual Studio 2002 and .NET 1.0. Using this platform, and its modern versions (4.5.1 with Visual Studio 2013), you can build what would be considered a traditional Windows executable or application. From Windows Services, desktop applications written for several different UI platforms (WinForms and WPF), and sophisticated web applications all can be created and are portable across all modern versions of Windows, with the exception of WindowsRT. WindowsRT runs traditionally on lower powered ARM processors, and cannot execute a traditional application written for .NET.
Unfortunately, the names and capabilities are very confusing. WinRT (Windows Runtime), which is the platform, can be used to create Windows Store applications. It cannot be used currently to build what would be considered a native desktop application. .NET 4.5 cannot be used to build a Windows Store application. The WinRT platform can target any modern Windows device, from tablet, to desktop. WinRT also runs on Windows RT, which are the lower powered, non-x86 chipsets like ARM.
All platforms share several languages: C#, VB, and C++.
The WinRT's libraries manifest as a layer that look identical to nearly identical in many cases to .NET libraries. In fact, the documentation can often be used for either in common cases. More confusingly, it's sometimes referred to as .NET for Windows Store apps. You'll see how it's not a complete .NET 4.5 implementation.
The confusion often comes from the fact that they are so similar. The underlying code for WinRT is not .NET. It is opaque (and mostly written in C++). It looks like .NET 4.5, and often performs/behaves like .NET 4.5, but it isn't the same platform as is used by a traditional .NET 4.5 application. While you can create code that can run as a portable class library and use functionality and APIs that are common to all platforms (.NET and WinRT), a WinRT application can not directly call .NET 4.5 code.
The Windows Runtime is a highly sandboxed and API-curated developer experience, much like is available on various phone platforms, like the Windows Phone Runtime, iOS, and Android. If you look at the "surface" area of the .NET platform and CLR, you'll see how large and complex it has become, and that there are a lot of capabilities that either don't make sense in the context of a Windows Store application, or simply aren't safe. I expect over several releases Microsoft will include additional features to the Windows Runtime from the core Windows OS. Those APIs may/may not mirror similar functionality found in .NET 4.5.
However, on a Windows 8+ system, a Windows .NET application can access a subset of the APIs available in the WinRT (the marketing folks at Microsoft refer to it as a "streamlined" set of APIs). For example, you cannot access the WinRT UI platform and create a desktop application that builds its interface using WinJS or XAML, which are only available in a WinRT application.
.NET Framework Support for Windows Store Apps and Windows Runtime