Tri Nguyen's Blog

Run Xamarin project from command line

2019-09-21T00:00:00+00:00

Update 2019, Oct 21: Add Build Archive for Xamarin.iOS

I feel pleasant working on Xamarin projects with VSCode in parallel with Jetbrains Rider IDE. It's neccessary to find a way to build and run Xamarin.iOS and Xamarin.Android apps using command line and generate those scripts as tasks in VSCode for quick development.

Run Xamarin.Android project from command line</h2>
msbuild /t:Build && msbuild /t:Install && adb shell monkey -p APP_PACKAGE_NAME 1 </code></pre> Notes</h3> It is required to ensure that devices or simulator is already running. Invoke adb devices should have some result. Simulator can be run using Android SDK tool emulator. Example: ./emulator -avd Pixel_2_29</code> </li> There are built-in MSBuild targets that take care of everything, from building to deploying. Have a look at this docs: https://docs.microsoft.com/en-us/xamarin/android/deploy-test/building-apps/build-process#build-targets</a> </li> </ul> msbuild /t:Build msbuild /t:Rebuild msbuild /t:Clean msbuild /t:Install msbuild /t:Uninstall msbuild /t:UpdateAndroidResources </code></pre> adb shell monkey</code> is used to launch the installed app</li> UpdateAndroidResources is useful when having trouble with the generated code in Resources.designer.cs or when editting resources file (i.e. strings.xml)</li> </ul> Run Xamarin.iOS project from command line</h2> Example build and run Xamarin.iOS app on iPhone XR, iOS 12.4 simulator msbuild /t:Build && /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/bin/mlaunch --launchsim=bin/iPhoneSimulator/Debug/YOUR_IOS_PROJECT_NAME.app --device::v2:runtime=com.apple.CoreSimulator.SimRuntime.iOS-12-4,devicetype=com.apple.CoreSimulator.SimDeviceType.iPhone-XR </code></pre> Notes</h3> msbuild /t:Build for building the Xamarin.iOS app bundle, output file YOUR_IOS_PROJECT_NAME.app in bin/iPhoneSimulator/Debug folder. There is no need for generating IPA file during development </li> mlaunch used for installing and launching the Xamarin.iOS app bundle on device or simulator. This is still closed source maintained by Xamarin team. But reading the help page would help using the tool /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/bin/mlaunch -h </li> </ul> Explain steps to work with mlaunch</h3> Locate mlaunch tool which usually locates at /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/bin/mlaunch </li> Get list of simulators and save the runtime and devicetype value </li> </ul> mlaunch --listsim simulators.xml # simulators.xml is a temporary file that store all available simulators. Select a simulator (i.e iPhone XR), and keep the associated value of *SimRuntime* and *SimDeviceType* for later usage, </code></pre> Construct argument and launch the app</li> </ul> mlaunch --launchsim=IOS_APP_PATH --device::v2:runtime=SIM_RUNTIME,devicetype=SIM_DEVICE_TYPE # *IOS_APP_PATH* is the path to *YOUR_IOS_PROJECT_NAME.app* file generated after *msbuild* step. The *--device* argument is constructed using the *SIM_RUNTIME* and *SIM_DEVICE_TYPE* value from the above step. </code></pre> The message Press enter to terminate the application message will be shown when the app launch on simulator.</li> </ul> Others script for Xamarin.iOS</h3> Generate Xcode Archive for publishing (suggest build Solution file rather than Project file)</li> </ul> msbuild /t:Build /p:Configuration=Release /p:Platform=iPhone /p:ArchiveOnBuild=True </code></pre>



TinyTimer for macOS
2019-08-18T00:00:00+00:00
TinyTimer - A simple Timer for macOS, access quickly from MenuBar, get more focused on the task</p>

Built with Swift and Xcode</li>
Open-source: https://github.com/trinnguyen/tinytimer</a></li>
Download: TinyTimer v1.1.1.zip</a></li>
</ul>
Features</h2>

Start, Pause, Stop from MenuBar</li>
Quickly start a Timer with recent settings and default items at 1 hour, 2 hours, 4 hours</li>
Custom input time</li>
</ul>


Migrate Xamarin Components
2018-03-07T00:00:00+00:00
New release of Visual Studio 4 Mac 7.4 on March 2018 has introduced new changes on C# editing which bring the significant improvement on typing responsiveness but forces old Xamarin projects to remove the Xamarin Components.</p>
</p>
The message:</p>
“We’ve detected that your solution is currently using Xamarin Components, which is no longer supported. Please remove the used Components manually and reopen the solution.”</em></p>
We can Fix it by removing the Xamarin Component and replaced by the Nuget package or another library/DLL</p>
Remove the Component</h1>
VS4Mac 7.4 removes the Components section of the Solution Pad so we have to work manually with the .csproj file to remove the Component, for example, CorePlot Component</a></p>

Open your .csproj file with an XML editor (Visual Studio Code/ Atom,…), find the section `XamarinComponentReference`</strong>, under a parent XML node called `ItemGroup`</strong>, remove this entire node from the file</li>
</ul>
</p>

Still, inside .csproj file, find the reference to the DLL and delete it by searching for the component name, for example: “CorePlot”, should found a node <Reference Include="CorePlotiOS"></code>,simply delete entire node</li>
</ul>
</p>

Now back to VS4Mac and reopen your solution</li>
</ul>
Adding the library back:</h2>

If you could find the appropriate NuGet package for that, would be great!</li>
Or look for another alternate library, in my case, considering OxyPlot</li>
Create your owned package if the library is a binding to a native (ObjC/Java) library</li>
Or keeping the DLL from Components folder and add the reference to it (not recommended)</li>
</ul>


1Password Extension for Xamarin.iOS apps
2017-02-09T00:00:00+00:00
</p>
1Password is one of my favorite application on Mac and iPhone. It’s working pretty well across devices, browsers (Chrome/Safari in my cases). With one unique master password, 1Password enables different strong, complex passwords to all online socials.</p>
There is a bunch of iOS applications on Store that use 1Password login side already, see here: https://blog.agilebits.com/1password-apps</a> . Most of the popular apps are named here. Below are how it looks on Dropbox and Pluralsight (notice the 1Password icon?)</p>

</p>
 </p>
How do we add this extension to our iOS application? There is “1Password Extension for iOS Apps” that helps iOS developers support using 1Password login inside their applications, check out https://github.com/AgileBits/onepassword-app-extension</a>, but only for Objective-C and Swift. Well, how about Xamarin?</p>
Xamarin.iOS Binding for 1Password Extensions</h2>
Yes, I made the bindings library for it, check this Nuget package: 1PasswordExtension for Xamarin.iOS</a></p>
The source code is hosted on Github: https://github.com/trinnguyen/onepassword-app-extension-xamarin</a></p>
Anyone who is curious about how it is built can look at there and built their own DLL too, it fetches the latest Release of the original Objective-C library to build CocoaTouch framework.</p>
The binding ApiDefinitions class is generated by using Objective Sharpie with CocoaPods components, I hope to have some time to write about it later.</em></p>
Integrate to 1Password to your Xamarin.iOS app</h2>
1. Install Nuget package and add assets</h3>
Simply install the Nuget package (bindings of 1Password Extension) to Xamarin.iOS project</p>
Install</span>-</span>Package Xamarin</span>.</span>1</span>PasswordExtension
</span></code></pre>
Add 1Password.xcassets</strong> catalog**** to the application bundle, these images are provided by 1Password Team to help user recognize the button. This resource can be found on my Github repo</a> or the original library</a></p>
</p>
2. Add LSApplicationQueriesSchemes in Info.plist</h3>
1Password extension uses UIApplication.CanOpenURL</em> to check whether the app extension is available, with value “org-appextension-feature-password-management</em>“, thus any application that supports password management actions can be visible.</p>
One iOS 9+, application need to whitelist org-appextension-feature-password-management</strong> in LSApplicationQueriesSchemes</strong></p>

Open your Info.plist</strong> file, tab Source</strong></li>
Add new row: LSApplicationQueriesSchemes</strong> (array) with item: org-appextension-feature-password-management</strong></li>
</ul>
</p>
Play with source code</h3>
There are 4 use cases that normally integration works, for details check out document of the original library</a>. In this article, I will show how it works on Xamarin with C# code</p>
A demo Xamarin.iOS application is provided on my Github repo</a>, covers 3 use cases. For webView, check below sample code.</p>
check app Extension is available</h4>
Hide 1Password button if the App Extension is not visible (1Password app is not installed on iOS device yet)</p>
this.onePasswordButton.Hidden = !OnePasswordExtension.SharedExtension.IsAppExtensionAvailable;</pre>
Use Case #1: Native App Login</h4>
if </span>(</span>OnePasswordExtension</span>.</span>SharedExtension</span>.</span>IsAppExtensionAvailable</span>)
</span>{
</span>	</span>OnePasswordExtension</span>.</span>SharedExtension</span>.</span>FindLoginForURLString</span>(</span>"</span>https://www.acme.com</span>"</span>, </span>this</span>, </span>sender</span>, (</span>NSDictionary </span>loginDictionary</span>, </span>NSError error</span>) =</span>&</span>gt</span>;</span> 
</span>	{
</span>		</span>if </span>(</span>loginDictionary </span>== </span>null </span>|| </span>loginDictionary</span>.</span>Count </span>== </span>0</span>)
</span>		{
</span>			</span>if </span>(</span>error</span>.</span>Code </span>!= </span>AppExtensionErrorCodes</span>.</span>CancelledByUser</span>)
</span>			{
</span>				</span>System</span>.</span>Diagnostics</span>.</span>Debug</span>.</span>WriteLine</span>(</span>@"</span>Error invoking 1Password App Extension for find login: </span>{</span>0</span>}</span>"</span>, </span>error</span>);
</span>			}
</span>			</span>return</span>;
</span>		}
</span>
</span>		</span>this</span>.</span>usernameTextField</span>.</span>Text </span>= (</span>NSString</span>)</span>loginDictionary[AppExtensionLoginDictionarykeys</span>.</span>UsernameKey]</span>;
</span>		</span>this</span>.</span>passwordTextField</span>.</span>Text </span>= (</span>NSString</span>)</span>loginDictionary[AppExtensionLoginDictionarykeys</span>.</span>PasswordKey]</span>;
</span>	}</span>)</span>;	
</span>}
</span></code></pre>
Use Case #2: New User Registration</h4>
NSDictionary </span>newLoginDetails </span>= </span>new NSDictionary</span>(
</span>	</span>AppExtensionLoginDictionarykeys</span>.</span>TitleKey</span>, </span>"</span>ACME</span>"</span>,
</span>	</span>AppExtensionLoginDictionarykeys</span>.</span>UsernameKey</span>, </span>this</span>.</span>usernameTextField</span>.</span>Text </span>?? </span>""</span>,
</span>	</span>AppExtensionLoginDictionarykeys</span>.</span>PasswordKey</span>, </span>this</span>.</span>passwordTextField</span>.</span>Text </span>?? </span>""</span>,
</span>	</span>AppExtensionLoginDictionarykeys</span>.</span>NotesKey</span>, </span>"</span>Saved with the ACME app</span>"</span>,
</span>	</span>AppExtensionLoginDictionarykeys</span>.</span>SectionTitleKey</span>, </span>"</span>ACME Browser</span>"</span>,
</span>	</span>AppExtensionLoginDictionarykeys</span>.</span>FieldsKey</span>, </span>new NSDictionary</span>(</span>"</span>firstname</span>"</span>, </span>this</span>.</span>firstnameTextField</span>.</span>Text </span>?? </span>""</span>,
</span>													</span>"</span>lastname</span>"</span>, </span>this</span>.</span>lastnameTextField</span>.</span>Text </span>?? </span>""</span>)
</span>);
</span>
</span>// The password generation options are optional, but are very handy in case you have strict rules about password lengths, symbols and digits.
</span>NSDictionary </span>passwordGenerationOptions </span>= </span>new NSDictionary</span>(
</span>	</span>// The minimum password length can be 4 or more.
</span>	</span>AppExtensionPasswordGeneratorOptions</span>.</span>MinLengthKey</span>, </span>8</span>,
</span>
</span>	</span>// The maximum password length can be 50 or less.
</span>	</span>AppExtensionPasswordGeneratorOptions</span>.</span>MaxLengthKey</span>, </span>30</span>,
</span>
</span>	</span>// If YES, the 1Password will guarantee that the generated password will contain at least one digit (number between 0 and 9). Passing NO will not exclude digits from the generated password.
</span>	</span>AppExtensionPasswordGeneratorOptions</span>.</span>RequireDigitsKey</span>, </span>true</span>,
</span>
</span>	</span>// If YES, the 1Password will guarantee that the generated password will contain at least one symbol (See the list bellow). Passing NO with will exclude symbols from the generated password.
</span>	</span>AppExtensionPasswordGeneratorOptions</span>.</span>RequireSymbolsKey</span>, </span>true</span>,
</span>
</span>	</span>// Here are all the symbols available in the the 1Password Password Generator:
</span>	</span>// !#$%^&*()_-+=|[]{}'\";.,&gt;?/~`
</span>	</span>// The string for AppExtensionPasswordGeneratorOptions.ForbiddenCharactersKey should contain the symbols and characters that you wish 1Password to exclude from the generated password.
</span>	</span>AppExtensionPasswordGeneratorOptions</span>.</span>ForbiddenCharactersKey</span>, </span>"</span>!#$%/0lIO</span>"
</span>);
</span>OnePasswordExtension</span>.</span>SharedExtension</span>.</span>StoreLoginForURLString</span>(</span>"</span>https://www.acme.com</span>"</span>, </span>newLoginDetails</span>, </span>passwordGenerationOptions</span>, </span>this</span>, </span>sender</span>, (</span>NSDictionary </span>loginDictionary</span>, </span>NSError error</span>) =</span>&</span>gt</span>;</span>
</span>{
</span>	</span>if </span>(</span>loginDictionary </span>== </span>null </span>|| </span>loginDictionary</span>.</span>Count </span>== </span>0</span>)
</span>	{
</span>		</span>if </span>(</span>error</span>.</span>Code </span>!= </span>AppExtensionErrorCodes</span>.</span>CancelledByUser</span>)
</span>		{
</span>			</span>System</span>.</span>Diagnostics</span>.</span>Debug</span>.</span>WriteLine</span>(</span>"</span>Failed to use 1Password App Extension to save a new Login: </span>{</span>0</span>}</span>"</span>, </span>error</span>);
</span>		}
</span>		</span>return</span>;
</span>	}
</span>
</span>	</span>this</span>.</span>usernameTextField</span>.</span>Text </span>= (</span>NSString</span>)</span>loginDictionary[AppExtensionLoginDictionarykeys</span>.</span>UsernameKey] </span>?? </span>""</span>;
</span>	</span>this</span>.</span>passwordTextField</span>.</span>Text </span>= (</span>NSString</span>)</span>loginDictionary[AppExtensionLoginDictionarykeys</span>.</span>PasswordKey] </span>?? </span>""</span>;
</span>	</span>this</span>.</span>firstnameTextField</span>.</span>Text </span>= (</span>NSString</span>)((</span>NSDictionary</span>)</span>loginDictionary[AppExtensionLoginDictionarykeys</span>.</span>ReturnedFieldsKey]</span>)</span>[</span>"</span>firstname</span>"</span>] </span>?? </span>""</span>;
</span>	</span>this</span>.</span>lastnameTextField</span>.</span>Text </span>= (</span>NSString</span>)((</span>NSDictionary</span>)</span>loginDictionary[AppExtensionLoginDictionarykeys</span>.</span>ReturnedFieldsKey]</span>)</span>[</span>"</span>lastname</span>"</span>] </span>?? </span>""</span>;
</span>	</span>// retrieve any additional fields that were passed in newLoginDetails dictionary
</span>}</span>)</span>;
</span></code></pre>
Use Case #3: Change Password</h4>
string changedPassword </span>= </span>this</span>.</span>freshPasswordTextField</span>.</span>Text </span>?? </span>""</span>;
</span>string oldPassword </span>= </span>this</span>.</span>oldPasswordTextField</span>.</span>Text </span>?? </span>""</span>;
</span>string confirmationPassword </span>= </span>this</span>.</span>confirmPasswordTextField</span>.</span>Text </span>?? </span>""</span>;
</span>
</span>// Validate that the new password and the old password are not the same.
</span>if </span>(</span>oldPassword</span>.</span>Length </span>&</span>gt</span>; </span>0 </span>&& </span>oldPassword</span>.</span>Equals</span>(</span>changedPassword</span>)</span>)</span>
</span>{
</span>	</span>this</span>.</span>ShowChangePasswordFailedAlertWithMessage</span>(</span>"</span>The old and the new password must not be the same</span>"</span>);
</span>	</span>return</span>;
</span>}
</span>
</span>// Validate that the new and confirmation passwords match.
</span>if </span>(</span>!</span>changedPassword</span>.</span>Equals</span>(</span>confirmationPassword</span>))
</span>{
</span>	</span>this</span>.</span>ShowChangePasswordFailedAlertWithMessage</span>(</span>"</span>The new passwords and the confirmation password must match</span>"</span>);
</span>	</span>return</span>;
</span>}
</span>
</span>NSDictionary </span>loginDetails </span>= </span>new NSDictionary</span>(
</span>	</span>AppExtensionLoginDictionarykeys</span>.</span>TitleKey</span>, </span>"</span>ACME</span>"</span>, </span>// Optional, used for the third schenario only
</span>	</span>AppExtensionLoginDictionarykeys</span>.</span>UsernameKey</span>, </span>"</span>aUsername</span>"</span>, </span>// Optional, used for the third schenario only
</span>	</span>AppExtensionLoginDictionarykeys</span>.</span>PasswordKey</span>, </span>changedPassword</span>,
</span>	</span>AppExtensionLoginDictionarykeys</span>.</span>OldPasswordKey</span>, </span>oldPassword</span>,
</span>	</span>AppExtensionLoginDictionarykeys</span>.</span>NotesKey</span>, </span>"</span>Saved with the ACME app</span>"</span>// Optional, used for the third schenario only
</span>);
</span>
</span>// The password generation options are optional, but are very handy in case you have strict rules about password lengths, symbols and digits.
</span>NSDictionary </span>passwordGenerationOptions </span>= </span>new NSDictionary</span>(
</span>	</span>// The minimum password length can be 4 or more.
</span>	</span>AppExtensionPasswordGeneratorOptions</span>.</span>MinLengthKey</span>, </span>8</span>,
</span>
</span>	</span>// The maximum password length can be 50 or less.
</span>	</span>AppExtensionPasswordGeneratorOptions</span>.</span>MaxLengthKey</span>, </span>30</span>,
</span>
</span>	</span>// If YES, the 1Password will guarantee that the generated password will contain at least one digit (number between 0 and 9). Passing NO will not exclude digits from the generated password.
</span>	</span>AppExtensionPasswordGeneratorOptions</span>.</span>RequireDigitsKey</span>, </span>true</span>,
</span>
</span>	</span>// If YES, the 1Password will guarantee that the generated password will contain at least one symbol (See the list bellow). Passing NO with will exclude symbols from the generated password.
</span>	</span>AppExtensionPasswordGeneratorOptions</span>.</span>RequireSymbolsKey</span>, </span>true</span>,
</span>
</span>	</span>// Here are all the symbols available in the the 1Password Password Generator:
</span>	</span>// !#$%^&*()_-+=|[]{}'\";.,&gt;?/~`
</span>	</span>// The string for AppExtensionPasswordGeneratorOptions.ForbiddenCharactersKey should contain the symbols and characters that you wish 1Password to exclude from the generated password.
</span>	</span>AppExtensionPasswordGeneratorOptions</span>.</span>ForbiddenCharactersKey</span>, </span>"</span>!#$%/0lIO</span>"
</span>);
</span>
</span>OnePasswordExtension</span>.</span>SharedExtension</span>.</span>ChangePasswordForLoginForURLString</span>(</span>"</span>https://www.acme.com</span>"</span>, </span>loginDetails</span>, </span>passwordGenerationOptions</span>, </span>this</span>, </span>sender</span>, (</span>NSDictionary </span>loginDictionary</span>, </span>NSError error</span>) =</span>&</span>gt</span>;</span>
</span>{
</span>	</span>if </span>(</span>loginDictionary </span>== </span>null </span>|| </span>loginDictionary</span>.</span>Count </span>== </span>0</span>)
</span>	{
</span>		</span>if </span>(</span>error</span>.</span>Code </span>!= </span>AppExtensionErrorCodes</span>.</span>CancelledByUser</span>)
</span>		{
</span>			</span>System</span>.</span>Diagnostics</span>.</span>Debug</span>.</span>WriteLine</span>(</span>"</span>Error invoking 1Password App Extension for find login, </span>{</span>0</span>}</span>"</span>, </span>error</span>);
</span>		}
</span>		</span>return</span>;
</span>	}
</span>
</span>	</span>this</span>.</span>oldPasswordTextField</span>.</span>Text </span>= (</span>NSString</span>)</span>loginDictionary[AppExtensionLoginDictionarykeys</span>.</span>OldPasswordKey]</span>;
</span>	</span>this</span>.</span>freshPasswordTextField</span>.</span>Text </span>= (</span>NSString</span>)</span>loginDictionary[AppExtensionLoginDictionarykeys</span>.</span>PasswordKey]</span>;
</span>	</span>this</span>.</span>confirmPasswordTextField</span>.</span>Text </span>= (</span>NSString</span>)</span>loginDictionary[AppExtensionLoginDictionarykeys</span>.</span>PasswordKey]</span>;
</span>}</span>)</span>;
</span></code></pre>
Use Case #4: Web View Filling</h4>
OnePasswordExtension</span>.</span>SharedExtension</span>.</span>FillItemIntoWebView</span>(</span>webView</span>, </span>this</span>, </span>sender</span>, </span>false</span>, (</span>bool success</span>, </span>NSError error</span>) =</span>&</span>gt</span>;</span> 
</span>{
</span>	</span>if </span>(</span>!</span>success</span>)
</span>	{
</span>		</span>System</span>.</span>Diagnostics</span>.</span>Debug</span>.</span>WriteLine</span>(</span>"</span>Failed to fill into webview: </span>{</span>0</span>}</span>"</span>, </span>error</span>);
</span>	}	
</span>}</span>)</span>;
</span></code></pre>


OpenCV for Xamarin.iOS
2017-02-07T00:00:00+00:00
Updated: 3 years ago I've worked on a Xamarin cross-platforms applications via iOS, Android, Windows Phone 8 which required using OpenCV for face detector and recognition. Even OpenCV has official frameworks for both iOS (ObjC) but it is pretty hard to make fully binding on Xamarin.iOS because most parts of framework are written on C/C++.</p>
Below tutorial is a workaround solution, but effectively, for getting native OpenCV for Xamarin.iOS.</p>
Overview</h2>
The idea is creating iOS Static library (CocoaTouch library) as a wrapper for specific functions (by requirements). This wrapper is written on Objective-C and implemented by communicating with OpenCV C++ classes.</p>
Let's go through a sample spec: detect faces from any image</p>


iOS Static Library</strong>: Simple library with one function: Detect faces on an image with OpenCV, export .a file for using on Xamarin</p>
</li>

Xamarin.iOS Binding project</strong>: Create a C# wrapper for static library, iOS Application: demo how binding and function of static library, detect faces on an image and draw them with red rectangle on image</p>
</li>
</ul>
Step by step: OpenCV on Xamarin.iOS</h2>
First, create iOS Static Library</strong></h3>
Should have an Objective-C library for wrapping all features that will work with OpenCV:</p>

Download opencv2.framework</strong> from OpenCV site (http://opencv.org/downloads.html)</li>
XCode: Create iOS Static Library project with a Objective-C class that contains required functions (can be multiple classes for management), named FaceDetector</strong></li>
</ul>
@interface </span>OpenCVUtils </span>: </span>NSObject
</span>+ (cv:</span>:</span>Mat)</span>cvMatFromUIImage:</span>(UIImage </span>*</span>)</span>image</span>;
</span>+ (UIImage </span>*</span>)</span>UIImageFromCVMat:</span>(cv:</span>:</span>Mat)</span>cvMat</span>;
</span>+ (</span>CGRect</span>) </span>cgRectFromCVRect:</span>(cv:</span>:</span>Rect) </span>cvRect</span>;
</span>@end
</span></code></pre>
- (</span>id</span>) initWithFaceCascade</span>:</span>(</span>NSString*</span>) filePath;
</span>- (</span>NSArray*</span>) detectFaces</span>:</span>(UIImage</span>*</span>) image;
</span>@end
</span></code></pre>

Build iOS Static Library and get libFaceDetector.a</strong> file</li>
</ul>
Second, Create Xamarin.iOS Binding</h3>

Xamarin Studio: New Solution -> iOS -> Unified API -> iOS Binding Project</li>
Drag libFaceDetector.a</strong> to Binding project</li>
Back to opencv2.framework</strong> file, open it, go to opencv2.framework -> Versions -> A -> opencv2. Rename this file to opencv2.a. Drag this to Binding project. (This binary file is required as reference from libFaceDetector.a)</li>
Open opencv2.linkwith.cs</strong>, add LinkerFlags</strong> and Frameworks</strong></li>
</ul>
[</span>assembly</span>: </span>LinkWith</span> ("</span>opencv2</span>.</span>a</span>", </span>LinkTarget</span>.</span>ArmV7</span> | </span>LinkTarget</span>.</span>ArmV7s</span> | </span>LinkTarget</span>.</span>Simulator</span>, </span>ForceLoad</span> = </span>true</span>, </span>LinkerFlags</span>="-</span>lc</span>++", </span>Frameworks</span>="</span>Accelerate AssetsLibrary AVFoundation CoreGraphics CoreImage CoreMedia CoreVideo QuartzCore UIKit Foundation</span>")]
</span></code></pre>

ApiDefinition.cs</strong> : Define interfaces for working with libFaceDetector.a . Can create manually if experienced with Xamarin.iOS Binding Metadata or using Objective Sharpie (command line tool)</li>
</ul>
interface FaceDetector {
</span> </span>//- (id) initWithFaceCascade:(NSString*) filePath;
</span> [</span>Export </span>(</span>"</span>initWithFaceCascade:</span>"</span>)]
</span> IntPtr </span>Constructor </span>(string filePath);
</span>
</span> </span>//- (NSArray*) detectFaces:(UIImage*) image;
</span> [</span>Export </span>(</span>"</span>detectFaces:</span>"</span>)]
</span> </span>NSArray </span>DetectFaces</span>(UIImage image);
</span>}
</span></code></pre>

Create Xamarin.iOS project, add reference to above Xamarin.iOS Binding project, try use C# wrapper classes</li>
</ul>

</span>UIImage </span>srcImage </span>= </span>UIImage</span>.</span>FromBundle</span>(</span>"</span>lena1</span>"</span>);
</span>NSArray </span>arrFaces </span>= </span>_faceDetector</span>.</span>DetectFaces</span>(</span>srcImage</span>);
</span>
</span></code></pre>
Source code</h3>
Get the full source code: https://github.com/trinnguyen/xamarin.ios-opencv</a></p>

Tri Nguyen's Blog

Run Xamarin project from command line

Others script for Xamarin.iOS</h3> Generate Xcode Archive for publishing (suggest build Solution file rather than Project file)</li> </ul> msbuild</span> /t:Build /p:Configuration=Release /p:Platform=iPhone /p:ArchiveOnBuild=True </span></code></pre>

TinyTimer for macOS

Features</h2> Start, Pause, Stop from MenuBar</li> Quickly start a Timer with recent settings and default items at 1 hour, 2 hours, 4 hours</li> Custom input time</li> </ul>

Migrate Xamarin Components

1Password Extension for Xamarin.iOS apps

Integrate to 1Password to your Xamarin.iOS app</h2> 1. Install Nuget package and add assets</h3> Simply install the Nuget package (bindings of 1Password Extension) to Xamarin.iOS project</p>

1. Install Nuget package and add assets</h3> Simply install the Nuget package (bindings of 1Password Extension) to Xamarin.iOS project</p>

OpenCV for Xamarin.iOS

Source code</h3> Get the full source code: https://github.com/trinnguyen/xamarin.ios-opencv</a></p>

Others script for Xamarin.iOS</h3>

Generate Xcode Archive for publishing (suggest build Solution file rather than Project file)</li> </ul>
`msbuild</span> /t:Build /p:Configuration=Release /p:Platform=iPhone /p:ArchiveOnBuild=True </span></code></pre>`

Features</h2>

Start, Pause, Stop from MenuBar</li>
Quickly start a Timer with recent settings and default items at 1 hour, 2 hours, 4 hours</li>
Custom input time</li> </ul>

Source code</h3>
Get the full source code: https://github.com/trinnguyen/xamarin.ios-opencv</a></p>