Missing the compiled messenger plugin for monotouch - mvvmcross - plugins

Attempting to use the latest compiled monotouch mvvmcross libraries. Following N+9 but it seems there is a core version of messenger plugin but no monotouch version. How do I fix it? i.e. couldnt find this for touch: Cirrious.MvvmCross.Plugins.Messenger

There isn't one.
The MvvmCross Messenger is a 'pure portable' plugin - it doesn't contain any platform specific extensions, just portable code.
The nuget installers take this into account automatically - as shown in the n=9 video and source code - http://mvvmcross.wordpress.com
You can read more about plugins - including about how to write and load them in https://github.com/MvvmCross/MvvmCross/wiki/MvvmCross-plugins

Related

can't load brother SDK to capacitor custom plug in

I have been searching all over and I have not found any good documentation in how can I create a custom ionic capacitor plug-in with an external SDK (Brother printer SDK). This SDK is located locally in my computer.
The Error I keep getting is the following.
No such module 'BRLMPrinterKit'
I'm building the plug in with
npm init #capacitor/plugin#latest
I follow the steps found in
How to embed third party framework on ionic capacitor custom plugin?
I was expecting to use the Brother printer SDK in the custom capacitor plug in. Any tip in how can I implement a custom plug in with any framework?
I don't know very well about ios plugins for ionic, but I recommend you to use this post to create the plugin step by step (I used it for android plugins):
https://devdactic.com/build-capacitor-plugin
I think you can use this other post to solve that specific issue: How to import framework into XCode project?
I know it's not the best answer, but I hope it helps.

Flutter web with incompatible plugins

I'm planning to use one of my Flutter app as a web application. Unfortunately one of the plugin I'm using is not compatible for web. In my case I would be happy to exclude that feature which is using the incompatible plugin, but I'm not sure how to exclude (also plugin registration in pubspec.yaml) when targeting platform which is not supported by the plugin?
This question sounds similar to Flutter - Conditional library import in flutter-web - which I found with a simple google search.

Can I create a library like a cocoapod or framework file for iOS or an aar file or gradle dependency for Android with Flutter?

I have a library our partners use to drop our UI and flow into their apps. Can I make a cocoapod or framework file or an aar file or gradle dependency with a flutter project?
Yes! For general information, see https://flutter.dev/docs/development/add-to-app
To create an AAR from a Flutter module that other Android apps can use without any direct dependency on Flutter, see Option A - Depend on the Android Archive (AAR)
To create a Framework from a Flutter module that other iOS apps can use without any direct dependency on Flutter, see Option B - Embed frameworks in Xcode
You can also find samples at
https://github.com/flutter/samples/tree/master/experimental/add_to_app, refer to the respective samples: android_using_prebuilt_module and ios_using_prebuilt_module
Now, if you are talking about integrating Flutter into an existing library (AAR or Framwork), then no, this is currently not supported, but is being explored:
https://github.com/flutter/flutter/issues/39027
note that this would be termed “add-to-library” as opposed to "add-to-app"
also mentioned, flutter/add-to-app:
Packing a Flutter library into another sharable library or packing multiple Flutter libraries into an application isn’t supported.

Upgraded App that uses SL Media Framework and MVVM-Lite from WP7 to WP7.1

I have a WP7 app that I recently upgraded to WP7.1 (including the MVVM-Lite assemblies) and the SL Media Framework player (SMF) stopped working. I turned on logging in the player and noticed that the decoder plugin it was looking for was not found. The SMF uses MEF to find the plugins and it was not able to find the plugin for my media.
I created a test project with just the SMF player and I was able to play SmoothStreaming and Progressive videos no problem. So one by one I added the referenced dlls that were in my real app into the test app - and when I added the MVVM-Lite 7.1 and Blend 7.1 assemblies (System.Windows.Interactivity and Microsoft.Expression.Interactions) - the MEF discovery of the plugins stopped working.
I then reverted the MVVM-Lite and Blend SDK assemblies back to v7 and the plugins were now discovered with no issues.
I am unaware of any use of MEF in the Blend SDK or MVVM-Lite but it appears there is an issue between SMF's MEF discovery when used with the Blend SDK 7.1 and MVVM-Lite 7.1 assemblies.
Any thoughts or insight into this? BTW - the SMF does not have a new version for WP7.1
thanks
Michael
I had the same problem. So, I started digging into this problem and I found the reason why is this happening.
The problem is System.Windows.Interactivity. SMF and MVVM Light are using different versions of this dll.
You have to make sure that Microsoft.SilverlightMediaFramework.Utilities.Phone project and your main project are refering to the same version.
In my case I updated SMF to reference version 3.8.5.0.
If you do not want to update the reference, then you can simply exclude the NavigationBehavior.cs class from Microsoft.SilverlightMediaFramework.Utilities.Phone project.
Hope it helps.

iPhone SDK - Converting project from 2.1 to 2.2.1

I just read in an online article that 2.2.1 does not support previous sdk. I wonder what that means? I just downloaded 2.2.1 and want to use updated/latest API's framework.
How can i convert my project so that it uses updated/latest API's/Frameworks in version 2.2.1? Are there any special steps required OR should i just 1.) delete 2.1 and 2.) install 2.2.1, and 3.) delete the Frameworks and reload them from iPhoneOS2.2.sdk directory instead, and that will do the magic.
Thanks.
It's safe to install. You don't have to "convert" anything. Your projects will continue to work. There are no new API's in 2.2.1. The documentation is a single page that tells you to refer to the 2.2 documentation.