Xamarin licensing issue (can I use specific component) - xamarin.ios

I saw this SO question asking for a PDF viewer for MonoTouch, which is just what I need. First I tried the Xamarin code sample suggested by poupou, but this needs a lot of extra work to use. So I decided to try the mTouch-PDFViewer suggested by Alex.
So I went to the download page and on to the GitHub for this component and cloned the repository. The problem is that the Visual Studio solution opens with a message saying I need a different license for Xamarin than I have. I only have a Xamarin Indie license and am therefore not able to build this library.
Is there a way around this? If I copied all the code into the Xamarin Studio, would it work then or can't I use this component at all due to licensing problems? Will it work in the app as long as I get hold of the dll file or do I need the more expensive license?
I have sent an email to the support email address for the mTouch-PDFViewer asking if the dll is available somewhere, but I was wondering in general if the licensing limits the use of dlls or just the ability to compile the code.

Indie license does not have Visual Studio support. An Indie license requires you to use Xamarin Studio on a Mac. There should not be any restrictions on using specific components.
Also, for basic PDF viewing, iOS has excellent built in support, which you might try before using a 3rd party component.

Related

Where can you find the Microsoft C++ Redistributable: Change Log / Bug Fixes

Background
Prior to release, we are required to review the Change Log / Bug Fixes for all third-party dependencies.
Question
Do you know where I can find the: Microsoft's Visual C++ Redistributes change log?
Visual Studio has release notes, but this does not specifically reference the C++ Redistributable.
The Distributed Code sub-section does mention Visual C++ Runtime Files, but I don't see a change log.
Any input you can provide would be greatly appreciated.
Related Resources
Microsoft Support
Can download redistributable? Yes
Has change logs? NO
Visual Studio Subscriptions downloads
Can download redistributable? Yes
Has change logs? NO
Microsoft Developer Community bug list
If you really want to get down in the weeds, this website is an option... but be prepared to spend a lot of time looking. I personally find that the search engine for this website is not great.

How to use makeappx to create msixbundle files that can be uploaded to the store according to the appxmanifest file?

For some reason(about the digital signature of the desktop bridge app, see here), I can't use visual studio to package my project. Makeappx seems to be able to do this, but those commands are too complex for me. Is there an easier way to achieve this?
Or to put it another way, how can I directly refer to the EXE file (which I can sign) rather than just the project in the application package project?
If Visual Studio is too complicated I recommend you get the free Express edition from Advanced Installer.
In the link include you can find a video that shows how to build an MSIX package (for bundle just change the radio button option from Builds page).
Additional info -
Publishing an MSIX package in the MS store.
Disclaimer: I work on the team building Advanced Installer.

Using flutter mobile packages in flutter web

I am using flutter web and I want to use some packages that are available for the mobile in the web version of flutter. The pubspec of flutter web look a bit different from that of flutter mobile but this is not the real problem. What I am concerned about is that is it possible to add the packages availble for mobile into that of the web. If yes, what is the proper way to do so?
This is not currently possible (as of June 2019) for any package which is dependent on the mobile OS. The reason for this is that the plugins on mobile use platform channels to communicate with platform-dependent code implementations for Android and iOS written in java/kotlin for android or objc/swift for iOS.
The only way those packages would ever work on the web is if a web-specific implementation were written for them which I assume would either use an emscripten-compiled library or more likely some sort of javascript bridge to call the relevant browser APIs.
From the flutter for web readme:
flutter_web does not have a plugin system yet. Temporarily, we provide access to dart:html, dart:js, dart:svg, dart:indexed_db and other web libraries that give you access to the vast majority of browser APIs. However, expect that these libraries will be replaced by a different plugin API.
For any plugin that is 100% dart code, you should be able to just include it in your pubspec.yaml the same way you would in flutter - under dependencies.
yes you can by take source code packages from github and take codes inside lib file inside package and put it in your project and fix errors may happen inside files by change path import to:
import 'package:flutter_web/material.dart';
and some more changes may need to do it.
it will work 100% and so easy :)

how to migrate visual studio C# app to monotouch

I have an existing application developed using Microsoft Visual Studio 2010 C#. I just purchased Xamarin's Monotouch product which allows me to use their IDE MonoDev to create iPhone/iPad applications from scratch by coding C#. Right now I don't want to code a new application. I want take my existing C# application import the source into monodev/monotouch and have the result run on the iPhone/iPad. My existing C# application is designed for deployment on Android phones/tablets using Xamarin's Android product. It works great! I have begun wading into the Xamarin documentation, samples, tutorials etc. But I need to port the existing application to iPhone/iPad right now, right away. I really don't have the luxery to spend time learning from scratch. I've got to belive someone has already gone down this migration path. If you have can we talk, email, or do you know if there is a guide describing the specific steps to take to accomplish this?
TIA
Xamarin MonoTouch does not allow you to run any C# application and run it immediately on an iPhone. The UI layer is native, so the C# code that constructs the UI must use the Xamarin bindings onto the Apple UI APIs.
The 'standard' migration process is to create an empty MonoDevelop project then start adding your existing C# business logic files, resolving any compilation issues as they arise.

Obfuscation tool with click-once support

I have found a lot of obfuscation tools with no clickonce support.
Could you provide vendors with click once support?
I would like to deploy obfuscated software at once without adding ANY extra line of code (pre-buid, post build etc)
p.s. I believe that is software related
I can't speak for other obfuscation products, but this has been a request of customers of Dotfuscator.
An integrated method for obfuscating ClickOnce applications is not currently available but will be coming in the next major release of Dotfuscator. I know this, because the task is currently assigned to me :) .
If there is anything in particular that you would like to see please feel free to let me know and I'll make sure to keep it in mind as I work on it.
You can create the manifests outside of Visual Studio using mageui (run mageui from the visual studio command prompt). It requires a little more work, but you can create the manifests with the dll's post-compile. If you want to make it easier after the initial setup, you can create a nant build file to do all the steps for you using mage (command line equivalent to mageui).
I produce a piece of software called ClickOnceMore which can be used to create ClickOnce manifests from obfuscated assemblies. Its more user friendly than Mage and MageUI and has a command line version that can be included as part of a build process. I have several customers who use it in conjunction with obfuscators, particularly Dotfuscator.
You can find the software here: http://www.clickoncemore.net
The Dotfuscator software included in Visual Studio 2010 will obfuscate your code and re-sign the manifests for you. Prior versions would obfuscate, but then you had to re-sign the manifests yourself.

Resources