How to manually install Telerik UI for Xamarin

In case you do not want to or can't use the MSI for some reason. UI for Xamarin offers means for manual installation. This will allow you to enable the Telerik Project Template as well as the Project Wizard in Visual Studio.

Visual Studio

Some additional work is required, however, to finalize the installers that will provide smooth out-of-the-box integration experience between UI for Xamarin and Visual Studio, in the face of our Project Template and Project Wizard.

Project Wizard in Visual Studio

If you are eager to try UI for Xamarin on Visual Studio and get the integration goodies set up, there’s still a relatively easy and quick and easy way to install them manually. This approach will also find its place in the cases where, for one reason or another, our organization does not allow usage of downloaded MSI installers. Here is the general flow when manual installation is used.

First, you need to log into your Telerik account and download the latest ZIP package. Unzip its content to any folder (for the purpose of this article C:\TelerikManualInstallation will be used) and manually install the Project Wizard by triggering the ProjectTemplateVS14.VSIX.vsix file.

Telerik account ZIP download

These steps will allow you to create projects using the Project Wizard. However, the projects will not build out of the box due to incorrect references.

What breaks the wizard?

When our components are installed using the MSI we know where the binaries are copied. Also we create a special RegistryKey during the installation. Later on, when customers use the Project Wizard to create new solution, we rely on that particular key to create all projects with correct references to our binaries. When this registry key does not exist all references inside the newly created projects will be incorrect.

How to fix the projects?

Manual reference update

One possible way to fix the issue is to manually update the references by deleting the existing ones and creating new ones pointing to the folder of the manual installation. This approach will resolve the binaries from the new folder and the references will be correct.

Another way to correctly reference the binaries is to open each of the created *.csproj files in a text editor and update the tag BinariesFolder with the new path. By default, that tag uses the custom registry key to find the path to the binaries folder. However, when a new solution is created, the same issue will exist and the same steps should be made again.

    <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
    <Platform Condition=" '$(Platform)' == '' ">x86</Platform>

See Also