Is there any library available that can be used in the PCL that target iOS, Android, and Windows Phone 8 application using Xamarin, for implementing AES 256 encryption.
In .NET Standard 1.3 you can now do aes encryption/decryption and hashing https://xamarinhelp.com/cryptography-in-xamarin-forms/
Have a look at this link.
The author has the same problem and came up with these alternatives:
PCL Contrib
Bouncy Castle PCL
PCL Crypto
He also gives another workaround;
The other work-around is to use some dependency injection with
platform-specific code in each platform library and using it in common
projects. Xamarin forms provide a minimum depedency feature using
DependencyService. The only issue here is writing platform-specific
code and it is time consuming.
For more information on the DependencyService check out the Xamarin documentation.
Related
Is there any dotnet core version of DocuSign.eSign Nuget package? or even source code I can fork?
DocuSign.eSign Nuget pacakge
Source code for C# client
There isn't any officially provided by DocuSign or alternatives that I'm aware of.
You could generate your own library with Swagger CodeGen and the DocuSign OpenAPI Specifications Swagger JSON
There is an unofficial fork of the C# SDK for .NET Core. Check the issues for the DocuSign C# SDK for a link.
Also, I'm looking to conduct 30 minute interviews with developers who are using DocuSign or considering to do so to get their opinions on how I can improve the developer products. Contact me via larry.kluger.docusign#gmail.com if you'd like more info.
After trying out both suggested solutions, it turns out that .net core SDK does not support the JWT Oauth workflow and it only support what's called legacy authentication method.
So, If you are trying to use JWT authentication using dotnet core SDK, you cannot
I am converting xamarin forms pcl to .net standard. In the project I use skia sharp and azure mobileservices.
My understanding was that if I reference these libraries in the .net standard class library and then add a reference to this .net standard class library in my android/ios/uwp projects all would be fine.
However it seems that I need to add the nuget packages for skiasharp and azure mobileservices to each project (android/ios/uwp). Is this indeed the case? if so, how is this better than using PCL?
I got the android project working, but I needed to add all the nuget packages to the android project.
I got the uwp project working without any nuget packages, which confuses me even further.
Using PCL and .NET Standard are basically the same - both are just API contracts or a subset of the full .NET Framework. But there is a MAJOR advantage to .NET Standard: .NET Standard has far more APIs - especially if you are using 1.3+ (netstandard1.3 has the System.IO APIs which aren't available in PCL).
With regards to NuGets, you typically still need to reference the NuGet package in all the app projects because some platforms have different implementations to take advantage of platform features. Think of .NET Standard as a subset of all the platform APIs - this is why SkiaSharp works just fine for some platforms. However, Android and iOS have a different implementation to take advantage of platform features.
Although you aren't doing Android development directly (since you are using Xamarin.Forms) you wouldn't have noticed something. If you JUST include the .NET Standard package, you get the basic SkiaSharp that can, for example, convert between a Xamarin.Forms color and a SkiaSharp color. However as a result of including the package in the android app, you can additionally convert from an Android color to a SkiaSharp color.
Personally, I always include all the NuGets into the app projects just to be safe.
Here are some docs that may help you:
https://learn.microsoft.com/en-us/dotnet/standard/net-standard
i have been searching on whether UWP projects can be implemented with Managed Extensibility Framework.
On the GitHub depository
of Prism, it says
MEF is supported with WPF for compatibility with previous versions.
It will not be added to Windows 10 UWP or Xamarin Forms.
(It is for Prism.Mef. But, can it not be for MEF generally?)
on Microsoft Developer Network it is said:
MEF is an integral part of the .NET Framework 4, and is available wherever the .NET Framework is used. You can use MEF in your client applications, whether they use Windows Forms, WPF, or any other technology, or in server applications that use ASP.NET.
Is UWP included in "any other technology" part or with the "in server applications that use ASP.NET" part?
I know .NET Core is used for UWP applications, but that ASP.NET part confuses me.
Briefly,is it possible to write UWP applications with MEF? Answers with sources will be appreciated. Thanks.
It is for Prism.Mef. But, can it not be for MEF generally?
For Prism.Mef only
Is UWP included in "any other technology" part or with the "in server applications that use ASP.NET" part?
UWP is included in "any other technology" part
Briefly,is it possible to write UWP applications with MEF?
Yes, by using the Microsoft.Composition NuGet package, we can easily integrate MEF in UWP app.
Here is an article for Windows Store app(8.1), it is similar with UWP app.
And this is a UWP MEF sample: Link
I'm creating a UWP program using the PRISM 6 library from GitHub which has support for using Unity for dependency injection. However the current release of Unity (including the latest code in GitHub) has no mention of UWP support.
Does anyone know if the current Unity release is compatible with UWP projects?
The current Unity release (4.0.1) is compatible and working on UWP.
Edit: Due to project restructuring, samples have moved to a separate repository. One of the samples that is using Unity is the SplitView sample. Simply derive your app from PrismUnityApplication.
I am trying to make an SIP based application running on Adobe AIR using Flex. Can I use the PJSIP library written in C for my Flex project?
Yes, you can by using AIR native extensions. Quoting the introduction:
Native Extensions for Adobe AIR are code libraries that contain native code wrapped with an ActionScript API. You can use native extensions in an AIR application to access platform features not supported by AIR, to benefit from native-code-level performance for critical algorithms, and to reuse existing native code libraries.