I am using latest here.com map library which was modified on 11-02-2016. To this jar file the class MapLabeledMarker is not present whether is it deprecated? or I have to make use some other version library to use above class. Answers are much appreciated.
com.here.android.mpa.mapping.MapLabeledMarker ?
Are you using the Starter or Premium version of the HERE SDK for Android? The Starter version does not contain MapLabeledMarker, it is only available in the Premium version.
More info on HERE SDK versions: https://developer.here.com/plans/mobile-sdk
Related
I have been using Google.Cloud.Translation.V2 in a UWP app for a while. Its latest NuGet package is 3.1.0. Upgrading from 2.x to 3.x results in the following error:
NU1202: Package Google.Cloud.Translation.V2 3.1.0 is not compatible
with uap10.0.19041 (UAP,Version=v10.0.19041) / win10-x64-aot. Package
Google.Cloud.Translation.V2 3.1.0 supports:
net462 (.NETFramework,Version=v4.6.2)
netstandard2.1 (.NETStandard,Version=v2.1)
Does this mean the newer versions will no longer work with UWP apps?
Does this mean the newer versions will no longer work with UWP apps?
TLDR; UWP is not a supported platform
From this GitHub issue:
We don't currently support UWP, and even if using grpc-dotnet makes it technical work, it's unlikely that we will prioritize UWP support over other work. So when we have moved over to grpc-dotnet by default, you may be in a situation where you can try to use the libraries and quite possibly be successful, but we would still not support it.
Also shown in this comment:
To reiterate: UWP is not a supported platform for these libraries. You could potentially use the Google.Apis.* NuGet packages, which don't use gRPC, but again, UWP isn't a supported platform for those either.
Final note (from this comment):
You may find that the REST-based libraries for whichever APIs you're using (packages starting "Google.Apis") work, but again those aren't actually supported on UWP.
We are going to use Firebase C++ SDK for multiple projects, but we are not using cocoapods so we are manually downloading the Firebase SDKs as pointed out in the documentation from here:
https://firebase.google.com/docs/ios/setup#frameworks
https://firebase.google.com/docs/cpp/setup#available_libraries
The Firebase readme file from the downloaded C++ SDK (readme.md) states the following:
Important: Each version of the Firebase C++ SDK supports a specific version of the Firebase iOS SDK. Please ensure that you reference the Cocoapod versions listed above.
The download link from the documentation doesn't have multiple links for each version.
Edit: modified text and images with correct versions
Is there a place where we can download specific versions of the SKDs?
How can we make sure that the download versions are compatible with each other?
Just downloaded both sdks and from the readme:
- C++ SDK is version 5.6.1 and requires Firebase/Core Cocoapod (5.20.0)
- Objective-C SDK has Firebase version 5.20.2
The Objective-C library is a bigger version then requirement of the C++ one (5.20.2 > 5.20.0) but is this property enough to assure compatibility?
See below images for readmes:
readme.md - C++ SDK
README.md - Objective-C SDK
First off it seems that Google forgot to make a branch for the iOS version 5.20.2 (on git currently only this exists: https://github.com/firebase/firebase-ios-sdk/tree/release-5.20.0 )
Considering that only the last number was incremented, let's assume there aren't big changes between the two versions, so we can check 5.20.0.
Your issue is that in the C++ SDK's readme for the iOS part they don't specify exactly the obj-c counterparts but the pods version. You can use the pods files though to check if the versions correspond.
For example we can check "Firebase Auth": in the C++ SDK says that it uses the 5.20.0 pod for ios, which is this one: https://github.com/firebase/firebase-ios-sdk/blob/release-5.20.0/FirebaseAuth.podspec
FirebaseAuth.podspec
We can see in the file that the version of Firebase Auth for the obj-c 5.20.0 SDK is 5.4.2, as it is in your readme.
You can do the same for all necessary services to make sure the compatibility is maintained.
I have no idea unfortunately if you can check this in an automatic way.
From where does one obtain the latest versions of alexa-appkit-xx.xx.xx.jar and alexa-skills-kit-xx.xx.xx.jar?
You can download the latest jar for the alexa-skills-kit here:
https://mvnrepository.com/artifact/com.amazon.alexa/alexa-skills-kit
I don't see an appkit jar there, but if you mean the Alexa Voice Services SDK then that can be found here:
https://github.com/alexa/avs-device-sdk
for the latest updates and find a maven link have a look at
this information
Hope this helps you out a bit.
I have been using previous version of unity extension. Now I have to upgrade my project with a newer version of Unity Extension.
I have code in my previous version as :-
Microsoft.Practices.EnterpriseLibrary.Common.Configuration.Unity.UnityContainerExtensions.AddNewExtensionIfNotPresent<Microsoft.Practices.Unity.InterceptionExtension.Interception>(Context.Container);
this.Context.Container.AddExtension(new ContainerRegistration());
But in new version Unity is not found under Configuration, has it moved to a new method?
The Unity building block can be installed with NuGet. You can get more informations here, or by opening the package manager in Visual Studio and searching for Unity.
The class you're looking for are now in another namespace. For example, UnityContainerExtensions is in Microsoft.Practices.Unity. I'd recommend adding a using on top of the classes where you're dealing with the UnityContainer to simplify the reading.
Our company's svn cannot allow single file larger than 40mb, realm framework needs 140mb+，so how can I build realm-cocoa with source code on github?
You could instead use the dynamic framework, which is a lot smaller (28,5 MB), through being already linked, but you won't be able to support iOS 7 in that way.
Alternatively I would recommend using a dependency manager like CocoaPods, which helps you with the setup and integration. But as a Core Member of this project, I'm obviously biased in that regard.
If that shouldn't be available for you, then you could theoretically use SVN externals to checkout the realm-cocoa repo (GitHub supports SVN transports), add the Realm.xcodeproj to your Xcode project, set the iOS framework target as dependency target of your app target and link to Realm.framework. But please not that this is not an officially supported way of integration.