I was confused related ICU4J , if i want to upgrade my application version to Support Android N . How can i migrate from previous Android SDK to Android ICU API . For Example if i have used Calendar in my Application Using java.util.Calendar , will i implement that again with Android ICU API ? or there is shortest way ?
you don't have to implement that again for android N. but just change way of use.
explained in documentation
Migrating to android.icu APIs from other Android SDK APIs
use android.icu.util.Calendar instead of java.util.Calendar
for support older version then Android N you have to add ICU4J libraries
While migrating from icu4j to android N. You don't have to implement it again in android N. But you need to change only the imports & remove the ICU4J from your external library as per the document.
If you are already using the ICU4J APIs in your app, and the android.icu APIs meet your requirements, then migrating to the framework APIs requires you to change your Java imports from com.ibm.icu to android.icu.
You may then remove your own copy of ICU4J files from the APK.
When you migrating from ICU4J to android N please note below point.
Note:
The ICU4J framework APIs use the android.icu namespace instead of
com.ibm.icu.
This is to avoid namespace conflicts in APKs that contain their own
com.ibm.icu libraries.
Like all new APIs, if you want you app to work on earlier versions of Android you should not use them (unless you protect the calls behind version checks).
If you only intend to target the N release, then you can use the android.icu ICU4J APIs.
Related
Looks like there three connector nuget packages available from steeltoe https://www.nuget.org/packages/Steeltoe.Connector.ConnectorCore/
https://www.nuget.org/packages/Steeltoe.Connector.CloudFoundry/
https://www.nuget.org/packages/Steeltoe.CloudFoundry.ConnectorCore/. I have an ASP.NET Core application in .net core 3.1. Which one I should select now? Also can i get detailed documentation of each of these packages. Looks like Steeltoe.Connector.ConnectorCore need .netcore3.1 and the other two simply requires .nestandard2.0. Any idea why is it so? Ideally all reusable libraries target .netstandard2.X, if I am not wrong
For Steeltoe 3.0 use Steeltoe.Connector.ConnectorCore and Steeltoe.Connector.CloudFoundry - https://steeltoe.io/docs/3/connectors/usage#cloud-foundry
For Steeltoe 2.x use Steeltoe.CloudFoundry.ConnectorCore.
As far as the targeting goes, Steeltoe 3.0 is focused on .NET Core 3.1+, so we aren't intentionally building compatibility for anything older on that branch. There may be some cases where we're targeting netcoreapp3.1 and could be targeting netstandard2.0... We've already dialed back several packages, though it doesn't look like ConnectorCore has been adjusted yet, we'd have to look at it to see if we can.
If you use anything that came before .NET Core 3.1, you should use Steeltoe 2.x, which is still maintained.
Can we use ninja to build UWP apps and hence create the appx package for the same?
I don't feel there is an online article for the same. I know how to do it using VS and Make.
In theory: Yes
Notable one thing: Ninja just official support C++, I can't find any result Ninja support other programming languages
With C++ we have 2 options:
C++/CX: You should activate flag /ZW for Windows Metadata
C++/WinRT: With WinRT you just compile without any restrict, this doesn't need Windows Metadata anymore
C++/CX: we have long story behind Windows Runtime development before C++ 11/14 became official so Microsoft add their own implementation features to MSVC. So with C++/CX you can compile with very old SDK like 10240, 10586, ... and in theory it also work with Windows 8.0/8.1 SDK, Windows Phone 8.0/8.1 SDK. Another attemp try to compile UWP with C++/CX on FastBuild (system build like Ninja) is successful, you can read as a reference here: https://github.com/fastbuild/fastbuild/issues/623
C++/WinRT is reunion attempt make Windows Runtime back to standard C++ 17. C++/WinRT can also compile with Clang/GCC. Base on answer from Kenny Kerr (creator of C++/WinRT): C++/WinRT is not limit with old SDK, but he recommended to use newer SDK like 17134. Link his answer https://stackoverflow.com/a/53193711/8707331.
Some useful links for C++ UWP:
https://github.com/MicrosoftDocs/cpp-docs/blob/master/docs/porting/how-to-use-existing-cpp-code-in-a-universal-windows-platform-app.md
https://modernwindows.wordpress.com/2015/05/28/modern-c-and-clang/
you can create uwp apps in following ways:
c# and xaml
web technologies like html, css and js. and you can use any
third party js libraries with it. you can even use hosted web apps
as uwp apps or latest technologies like pwas can also be shipped as
uwp apps. more here : https://developer.microsoft.com/en-us/windows/pwa
c++ and xaml : with this approach you can use c++ libraries (if they comply by uwp platform) the reason you do not have much support online for this is because majority of uwp developers use c# and xaml approach.
There are some work around for that, and one of them is to create a Desktop app and then package that in MSIX packaging , which packages a windows Desktop app into a uwp app and you can even distribute it through Microsoft store.
CMake can't be used to generate UWP package. However, you could use make.exe or Visual Studio to generate UWP package. For more you could refer to Create an app package with the MakeAppx.exe tool and Package a UWP app with Visual Studio.
I post the following question at LunarG, as Issue #565, about Vulkan SDK redistributable parts for ready to go applications developed with Vulkan. I'd like to share it with Stack Overflow developers.
Let's say I have Vulkan application demo and wish to send it to
potential clients, in order to evaluate it. If I'd develop it using
SDK, what is the correct way to deploy it :
a) include the compatible SDK installer in a multi-install process ?
b) include some SDK's dlls and companion files ? Which ones ?
It also raises another question: Can I re-distribute SDK files ?
Karl Schultz, from LunarG, replied with the following:
On Windows, many IHVs include the Vulkan loader DLL in their install
packages, placing it in system32/vulkan-1.dll. So, in many cases, your
app might just work fine as long as the user has installed drivers
with Vulkan support.
You might also consider shipping only the RunTimeInstaller, which is
found in the SDK. This would let the user install the run time
(loader) as part of your application install. The RTI includes version
checking so that it doesn't clobber a newer version installed by IHV
drivers, or vice-versa. In short, this is probably the best way to go.
It would be better to include the RTI as part of the "multi-install
process" rather than include the entire SDK.
If your application needs layers or some other specific item from the
SDK, then you'd have to include those explicitly somehow.
Please check the licensing-related files within the SDK concerning
redistribution.
I've recently made a Windows Forms Application in VS 2010 Express. When running on my machine it works fine but on other machines it needs to install the .NET framework first. Is there anyway around this? By including the library in my executable? By not using the .NET framework?
I would really appreciate some help.
Typically this kind of problem would be handled by your Windows Forms Application's installation package.
Opinions vary but I'd suggest the safest/most polite thing to do is to treat .NET as a prerequisite. If .NET is not present, display a message that it is required before the install will succeed and perhaps point to a Microsoft download page like this one or this one. The risk is that you point them to an obsolete download page or that the page moves and invalidates your link.
That said, I would have expected most machines to have some version of the .NET Framework installed (by Windows Update for example) so it's a bit surprising that you're being told it needs to be installed.
I suggest you follow the instructions in How to: Determine Which .NET Framework Versions Are Installed to check one of your failing machines to confirm that .NET is not installed (very unlikely) or to determine which version (or versions) of .NET is (are) installed.
Update 6/21/2015 From the comment below, we have evidence of two systems without .NET installed so my "very unlikely" comment above is a bit off base!
Update 7/4/2015 I have a bad habit of forgetting that not everyone configures their Windows systems exactly the same way I configure mine. From this blog post it seems that the .NET Framework is 'only' a Recommended Update.
I would like to know if it was possible to use JNI for an BB10 app. I'm kinda new with this thing and I saw somewhere that is possible.
Because I've an android app but I need to had some special features to make it run properly on BB10 and for that I need to use JNI.
Is it possible ? If yes, is it possible to find a sample or some doc about it somewhere ?
I assume you are asking about running an Android appliction on BB10. Support for JNI does not exist on any of the current official BB10 versions (up to and including 10.2.0). However version 10.2.1 includes a completely different Android runtime that is able to run APK directly including applications that use JNI. I haven't seen any official documentation of this yet however.