-
Similar Topics
-
By STF News
Continuing our overview of Tizen .NET development, today we will go through the basics of installing the Tizen extension for Visual Studio on a Mac computer.
Traditionally, you would develop Xamarin and .NET applications on a Windows machine. Now, cross platform developers can take advantage of the provided tools to create Tizen applications on MacOS.
The Tizen Tidbits video series covers core concepts of Tizen app development in ten minutes or less.
Stay tuned for more .NET development for the Samsung Galaxy Watch, and don’t forget to visit our developer portal to learn more about this and other topics.
View the full blog at its source
-
By STF News
You may have encountered the following error when launching a .NET application on your Tizen device, although the DLL file specified by the error message is already included in the application package (.tpk).
Note: You can view the log from the Tizen Log Viewer window or dlogutil.
Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly 'System.Collections.Immutable, Version=1.2.5.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified. File name: 'System.Collections.Immutable, Version=1.2.5.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' at TizenAppTemplate.App.OnCreate() at Tizen.Applications.CoreBackend.UICoreBackend.OnCreateNative(IntPtr data) at Tizen.Applications.CoreBackend.UICoreBackend.Run(String[] args) at Tizen.Applications.CoreApplication.Run(String[] args) at Tizen.Applications.CoreUIApplication.Run(String[] args) at TizenAppTemplate.App.Main(String[] args) onSigabrt called tpkroot └── bin ├── System.Collections.Immutable.dll ├── System.Runtime.CompilerServices.Unsafe.dll └── TizenAppTemplate.dll This error appears when the following conditions are met.
The application package contains one or more system DLLs (System.* or Tizen.*) The DLLs are newer than DLLs installed in the device image This usually happens when you reference a system package from your application. The following example shows an application project file (.csproj) that contains such a dependency.
<PropertyGroup> <OutputType>Exe</OutputType> <TargetFramework>tizen50</TargetFramework> </PropertyGroup> <ItemGroup> <PackageReference Include="System.Collections.Immutable" Version="1.7.0" /> </ItemGroup> In some cases, the file doesn't reference the system package directly. However, it may have such a dependency recursively in its dependency graph.
<ItemGroup> <!-- This library is dependent on System.Collections.Immutable 1.7.0. --> <PackageReference Include="SomeLibrary" Version="1.0.0" /> </ItemGroup> Why do I see this error?
As the error message implies, the error results from an AssemblyVersion mismatch. Your application expects a newer version of system DLL than the device has.
Note: AssemblyVersion, AssemblyFileVersion, and NuGet PackageVersion are all different properties. For example, the NuGet package System.Collections.Immutable 1.7.0 comes with System.Collections.Immutable.dll of version 1.2.0.5 (AssemblyVersion). Only AssemblyVersion is used by the runtime to verify DLL dependencies.
### Application-owned DLL $ sdb pull /opt/usr/globalapps/org.tizen.example.TizenAppTemplate/bin/System.Collections.Immutable.dll $ dotnet-ildasm System.Collections.Immutable.dll | grep '\.ver' | tail -n 1 .ver 1:2:0:5 ### Pre-installed DLL $ sdb pull /usr/share/dotnet.tizen/netcoreapp/System.Collections.Immutable.dll $ dotnet-ildasm System.Collections.Immutable.dll | grep '\.ver' | tail -n 1 .ver 1:2:0:4 The current implementation of the application launcher in Tizen (which hosts the .NET runtime) always prioritizes DLLs found in the system image and disregards application-owned DLLs, even though they are newer. It also ignores any properties defined in the application's .deps.json file.
In fact, this restriction is intentionally added in Tizen for performance reasons. The launcher prefetches several runtime components commonly used by applications (for reduced startup time) by assuming a unified set of Trusted Platform Assemblies across all applications. Because of the fundamental design of CoreCLR, a DLL cannot be loaded into the default LoadContext if there exists a DLL with the same name in Trusted Platform Assemblies.
For further details, you can read:
Framework-dependent deployments (FDD) CoreCLR hosting APIs AssemblyLoadContext Class Tizen's launcher implementation Possible solutions
Here are some solutions you can try:
Remove or downgrade the package
The first, most basic thing you can try is to eliminate the dependency itself. Check if the package is being used in the code and, if possible, reimplement the code without the package. You can otherwise downgrade the package from NuGets so that its DLL versions are compatible with all target devices. However, this is not always feasible if you cannot find a working version or you cannot control dependencies of libraries used by your application.
<ItemGroup> <!--<PackageReference Include="System.Collections.Immutable" Version="1.7.0" />--> <PackageReference Include="System.Collections.Immutable" Version="1.6.0" /> </ItemGroup> Handle AssemblyResolve events
Another workaround is to install a custom AssemblyResolve event handler inside your application. This handler is invoked when the runtime cannot find a DLL with a matching version. Note that if an application DLL has its native image, the native image is not automatically resolved by Assembly.LoadFile().
static void Main(string[] args) { AppDomain.CurrentDomain.AssemblyResolve += (object s, ResolveEventArgs eventArgs) => { var appDir = Path.GetDirectoryName(typeof(App).Assembly.Location); var assemblyName = eventArgs.Name.Split(',')[0]; var assemblyPath = Path.Combine(appDir, assemblyName + ".dll"); return File.Exists(assemblyPath) ? Assembly.LoadFile(assemblyPath) : null; }; ... app.Run(args); } Use this API with care since it can cause some unexpected behaviors, such as a type identity problem (see Best Practices for Assembly Loading). Also, you cannot use Assembly.Load() (with a full assemblyRef) or Assembly.LoadFrom(), because they implicitly load an assembly into the default LoadContext.
Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'System.Collections.Immutable, Version=1.2.5.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. Could not find or load a specific file. (0x80131621) File name: 'System.Collections.Immutable, Version=1.2.5.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' ---> System.IO.FileLoadException: Could not load file or assembly 'System.Collections.Immutable, Version=1.2.5.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. at System.Runtime.Loader.AssemblyLoadContext.InternalLoadFromPath(String assemblyPath, String nativeImagePath) at System.Runtime.Loader.AssemblyLoadContext.LoadFromAssemblyPath(String assemblyPath) at System.Reflection.Assembly.LoadFrom(String assemblyFile) ... onSigabrt called Use custom AssemblyLoadContext
For advanced scenarios, you can create your own AssemblyLoadContext in your application to isolate any specific DLLs. The following CustomAssemblyLoadContext class overrides Load() method to resolve DLLs explicitly from an application directory. See Understanding System.Runtime.Loader.AssemblyLoadContext for detailed information.
// Inherit AssemblyLoadContext. private class CustomAssemblyLoadContext : AssemblyLoadContext { protected override Assembly Load(AssemblyName assemblyName) { var appDir = Path.GetDirectoryName(typeof(App).Assembly.Location); var assemblyPath = Path.Combine(appDir, assemblyName.Name + ".dll"); return File.Exists(assemblyPath) ? LoadFromAssemblyPath(assemblyPath) : null; } } // In application code, var alc = new CustomAssemblyLoadContext(); var assembly = alc.LoadFromAssemblyName(new AssemblyName("SomeLibrary")); assembly.GetType("SomeLibrary.SomeClass").GetMethod("SomeMethod").Invoke(null, null); The sample code shown above may not work if the prefer_dotnet_aot manifest property is enabled in tizen-manifest.xml file, because application DLLs can have their native images in either bin or bin/.native_image. In such cases, consider using ApplicationInfo.ExecutablePath in TizenFX API instead of Assembly.Location.
If you need help, please contact me at [email protected]
View the full blog at its source
-
By STF News
So far this video series has focused on development of web apps with Tizen. Today we are going to cover the latest addition to the Tizen family: Tizen .NET. This option is perfect for developers that have previous experience with the Microsoft stack, or simply want to get ahead learning more of cross platform development with Xamarin.
The Tizen Tidbits video series covers in ten minutes, or less, core concepts of Tizen app development.
In upcoming videos, we will cover web and .NET app development for the Samsung Galaxy Watch, and will start creating small samples and modifying existing projects.
View the full blog at its source
-
By STF News
Previously, in order to use custom fonts in existing Xamarin.Forms applications, you had to add the font asset in each platform project and use the FontFamily property to apply the fonts. This was very cumbersome, because each platform required a different syntax for referencing a font file.
As we introduced in a previous blog post, using custom fonts in your Tizen .NET applications was not so simple, either.
Xamarin.Forms 4.5.0 introduced a new uniform way to specify custom fonts across platforms. You could define custom fonts on each platform and use them in the same way by including them as Application Resources, which was a feature available from Xamarin.Forms 4.5.0 Pre Release 1. We've added Tizen support to this feature, so you don't need to write code to use custom fonts.
This blog explains how to use custom embedded fonts in Xamarin.Forms Tizen applications.
Add the font file to your project in Visual Studio
To add fonts as resources, perform the following steps in the Visual Studio.
1. Create a folder to store the font files
To create a folder for storing the font files, right-click the project folder and select Add > New Folder.
Let's call it Resource.
2. Add a font file to your project
To add a font file to your project, right-click the Resource folder you just created and go to Add > Existing item..., or drag the file from File Explore (on Windows) or Finder (on Mac) and drop it into Resource folder. You can add TrueType font (.ttf) and OpenType font (.otf) files. To obtain sample font files, go here.
Note: Be sure to add the font file with Build Action: Resources. Otherwise, the font file will not be distributed as part of your app.
After you add the font file to your project as a Resource, you can begin assigning the font to VisualElement items that have the FontFamily property, such as Label, Entry, and so on. Font name can be specified in XAML or in C# code. As mentioned, you no longer need to know platform-specific rules for specifying FontFamily attributes. Whether it's using the full path and font name separated by a hash (#) as the font name (as in Android) or it's just using the font name (as in iOS), it works well.
Note: that the font file name and font name may be different. To discover the font name on Windows, right-click the .ttf file and select Preview. The font name can then be determined from the preview window.
Use your custom font in XAML
<Label Text="Custom Font 한글" FontFamily ="CuteFont-Regular" /> <Label Text="Custom Font 한글" FontFamily ="Dokdo" /> <Label Text="Custom Font 한글" FontFamily ="PTM55FT#PTMono-Regular" /> <Label Text="Custom Font 한글" FontFamily ="fa-regular-400.ttf#FontAwesome5Free-Regular" /> Use your custom font in C#
new Label { Text = "Custom Font 한글", FontFamily = "CuteFont-Regular" }; new Label { Text = "Custom Font 한글", FontFamily = "Dokdo" }; new Label { Text = "Custom Font 한글", FontFamily = "PTM55FT#PTMono-Regular" }; new Label { Text = "Custom Font 한글", FontFamily = "fa-regular-400.ttf#FontAwesome5Free-Regular" }; Screenshot
Now that you've reviewed the simple steps in this blog, check out the sample font files, see the many TrueType and OpenType fonts that are out there, and try custom fonts in your own Xamarin.Forms Tizen applications. For any questions or issues you may have, don't hesitate to contact us.
View the full blog at its source
-
By STF News
Previously, in order to use custom fonts in existing Xamarin.Forms applications, you had to add the font asset in each platform project and use the FontFamily property to apply the fonts. This was very cumbersome, because each platform required a different syntax for referencing a font file.
As we introduced in a previous blog post, using custom fonts in your Tizen .NET applications was not so simple, either.
Xamarin.Forms 4.5.0 introduced a new uniform way to specify custom fonts across platforms. You could define custom fonts on each platform and use them in the same way by including them as Application Resources, which was a feature available from Xamarin.Forms 4.5.0 Pre Release 1. We've added Tizen support to this feature, so you don't need to write code to use custom fonts.
This blog explains how to use custom embedded fonts in Xamarin.Forms Tizen applications.
Add the font file to your project in Visual Studio
To add fonts as resources, perform the following steps in the Visual Studio.
1. Create a folder to store the font files
To create a folder for storing the font files, right-click the project folder and select Add > New Folder.
Let's call it Resource.
2. Add a font file to your project
To add a font file to your project, right-click the Resource folder you just created and go to Add > Existing item..., or drag the file from File Explore (on Windows) or Finder (on Mac) and drop it into Resource folder. You can add TrueType font (.ttf) and OpenType font (.otf) files. To obtain sample font files, go here.
Note: Be sure to add the font file with Build Action: Resources. Otherwise, the font file will not be distributed as part of your app.
After you add the font file to your project as a Resource, you can begin assigning the font to VisualElement items that have the FontFamily property, such as Label, Entry, and so on. Font name can be specified in XAML or in C# code. As mentioned, you no longer need to know platform-specific rules for specifying FontFamily attributes. Whether it's using the full path and font name separated by a hash (#) as the font name (as in Android) or it's just using the font name (as in iOS), it works well.
Note: that the font file name and font name may be different. To discover the font name on Windows, right-click the .ttf file and select Preview. The font name can then be determined from the preview window.
Use your custom font in XAML
<Label Text="Custom Font 한글" FontFamily ="CuteFont-Regular" /> <Label Text="Custom Font 한글" FontFamily ="Dokdo" /> <Label Text="Custom Font 한글" FontFamily ="PTM55FT#PTMono-Regular" /> <Label Text="Custom Font 한글" FontFamily ="fa-regular-400.ttf#FontAwesome5Free-Regular" /> Use your custom font in C#
new Label { Text = "Custom Font 한글", FontFamily = "CuteFont-Regular" }; new Label { Text = "Custom Font 한글", FontFamily = "Dokdo" }; new Label { Text = "Custom Font 한글", FontFamily = "PTM55FT#PTMono-Regular" }; new Label { Text = "Custom Font 한글", FontFamily = "fa-regular-400.ttf#FontAwesome5Free-Regular" }; Screenshot
Now that you've reviewed the simple steps in this blog, check out the sample font files, see the many TrueType and OpenType fonts that are out there, and try custom fonts in your own Xamarin.Forms Tizen applications. For any questions or issues you may have, don't hesitate to contact us.
View the full blog at its source
-
-
Similar Tagged Content
-
By Alex
Three weeks ago, the company released in India the Samsung Z1, its first smartphone powered by Tizen, a homegrown alternative to Google Inc.’s Android operating system.
This week, Samsung is pushing the Samsung Z1 into Bangladesh, a neighbor of India with more than 150 million people and a similarly low rate of smartphone penetration.
After several missteps and rethinks, Samsung’s strategy for its Tizen smartphones is taking a clear shape: the company is aiming the fledgling platform squarely at first-time smartphone users, many of whom may not even have a bank account. The Samsung Z1 is selling in India for about $90.
To that end, Samsung has been touting the “lightweight” nature of the Tizen operating system, meaning that it requires relatively little computing power and can handle most tasks without requiring pricey high-end specifications.
That same lightweight approach has also allowed Samsung to use Tizen as the platform for many of the devices it is hoping will populate its “connected home,” from televisions to smart watches and home appliances.
Despite concerns that Samsung’s new smartphone would face stiff competition in India, where several local handset makers are touting low-end smartphones — some of them in partnership with Google — Samsung says that its Tizen smartphones have received “positive responses” there.
Positive enough, it seems, to at least push Tizen into a second country.
Source: http://blogs.wsj.com/digits/2015/02/06/samsung-extends-tizen-smartphone-to-bangladesh/
-
By Alex
Samsung to make the Tizen Z1 in India, but can the phone compete with rivals?
The Samsung Tizen-OS phone, the Z1, may seem like just another phone launch amongst dozens that take place every month in India, the hottest smartphone market in the world, where a little under 70 percent of the population still operate "dumb" feature phones.
But it's not. It has a multitude of narratives wrapped into it, the most important being Samsung's future in the country. The latest news that extends this conversation is the company's announcement yesterday that the Z1 will soon be manufactured in India.
Source: http://www.zdnet.com/article/samsung-to-make-the-tizen-z1-in-india-but-phone-faces/
-
-
