0 Comments

I followed this guide: https://medium.com/@tsjdevapps/use-fontawesome-in-a-xamarin-forms-app-2edf25311db4

Where you manually have to edit a XML file to get it to work in iOS and add the font for each platform you want to support. So for FontAwesome (regular, bold, brands) and UWP, Android, iOS. That gives 9 files!

which eventually works:

<Label Text="&#xf0f3;" FontFamily="{StaticResource FontAwesomeRegular}" FontSize="Large" TextColor="Red" />
         <Label Text="&#xf26e;" FontFamily="{StaticResource FontAwesomeSolid}" FontSize="Large" TextColor="Red" />
         <Label Text="&#xf26e;" FontFamily="{StaticResource FontAwesomeBrands}" FontSize="Large" TextColor="Red" />


BUT: If you would just update to Xamarin Forms 4.5.0.530 or higher

you can add a line for a font. (so 3 times something like this for FontAwesome)

[assembly: ExportFont("FontAwesome5Regular400.otf", Alias = "FontAwesome")]

to your app.xaml.cs

and use

<Label Text="&#xf0f3;" FontFamily="FontAwesome" FontSize="Large" TextColor="Green" />

in your mainpage.xaml


good luck!

Post on LinkedIn
0 Comments

Make sure you have Windows 10 with the anniversary update or newer.

You can verify this by pressing the winkey + R and type ‘winver’ and hit enter. The anniversary update has buildnr 14393. And make sure that you have the “Bash on Ubuntu on Windows” feature enabled.

Xmllint is not included by default, so you have to install it first.

sudo apt install libxml2-utils

You can read more about xmllint on http://xmlsoft.org/

in order to format a large XML file which has no line breaks you have to use xmllint like this:

xmllint --format input_xml_file.xml > pretty_output_xml_file.xml

You use the format option on the input_xml_file.xml and redirect the output (>) to a new file with the name pretty_output_xml_file.xml

This is a lot faster than opening the file in notepad++ and use the xml plugin to format it.

Hope it helped. Good luck!

snip_20170411144653

Post on LinkedIn
0 Comments

This is my solution explorer:

solution-explorer

and this is my nuget package manager:

nuget

So The XmlSerializer is installed. Somehow the Newtonsoft.Json gives a yellow icon in the solution explorer. But no errors from that lib in the output window.

I thought that the nuget packagemanager or visual studio would auto restore all packages for me. Somehow it was fixed by manually running dotnet restore from the cli.

The whole tooling for .net core is still work in progress and I really liked working with preview 2 (1.0.1) in vs code with the project.json files.

Switching back to the csproj file makes it imho harder to work with vs code and makes using Visual Studio 2017 (community) almost required.

I really enjoyed working through the jonhilton tutorial for dotnet core.

But that does not work anymore, because 1.1 is out and project.json is gone.

I have used dotnet migrate to move from project.json to projectname.csproj and it returned zero errors/issues. But did not launch. No project was found according to msbuild. And after changing task.json it gave a lot of reference issues. So I started over in Visual Studio 2017 RC and have a lot more setup by default and less issues.

I see that the whole development of dotnet core is moving forward fast. But I really enjoyed the development experience with vs code and the jonhilton tutorial. I hope that it will come back, or that someone will make a similar tutorial for vs code with dotnet 1.1 and mvc (and kestrel, because vs2017 has iis express as default webserver)

Looking forward to all the new bits and pieces and will keep updating vs code (insider) and dotnet core.

I hope the suggestion of the manual dotnet restore helped someone.

 

good luck!

Post on LinkedIn