<script type="text/javascript" src="scripts/common.js" charset="utf-8"></script>
<script type="text/javascript" src="scripts/core.js" charset="utf-8"></script>
<script type="text/javascript" src="scripts/search.js" charset="utf-8"></script>
- <title>What's New</title>
+ <title>Overview</title>
</head>
-<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
+<body onload="prettyPrint()" style="overflow: auto;">
<div id="toc-navigation">
+
+ <div id="toc_border"><div id="toc">
+ <p class="toc-title">Content</p>
+ <ul class="toc">
+ <li><a href="#runtime">Managed Runtime Advantages</a></li>
+ <li><a href="#features">Tizen .NET Features and Components</a></li>
+ </ul>
+ </div></div>
</div>
<div id="container"><div id="contents"><div class="content">
- <h1>What's New</h1>
+ <h1>Overview</h1>
+<p>Tizen .NET is a new application framework for Tizen based on .NET.</p>
+<p>Tizen .NET is an exciting new way to develop applications for the Tizen operating system, running on 50 million Samsung devices, including TVs, wearables, mobile phones, and many other IoT devices around the world. The existing Tizen frameworks are either C-based with no advantages of a managed runtime, or HTML5-based with fewer features and lower performance than the C-based solution. With Tizen .NET, you can use the C# programming language and the Common Language Infrastructure standards, and benefit from a managed runtime for faster application development and code execution that is efficient and secure.</p>
+<p>To start developing Tizen applications using .NET, familiarize yourself with Visual Studio Tools for Tizen:</p>
-<div class="note"><strong>News and Updates</strong>
- <ul><li><strong>Visual Studio 2017 Support.</strong> Visual Studio Tools for Tizen has supported Microsoft’s Visual Studio 2017 released on March 2017 since the second preview.</li></ul>
-</div>
+<ul>
+ <li><a href="getting_started/getting_started_cover.htm">Getting Started</a>
+ <p>Learn about installing Visual Studio Tools for Tizen, creating your first Tizen .NET application, and porting existing Xamarin.Forms applications to Tizen.</p></li>
+ <li><a href="tools/tools_overview.htm">Visual Studio Tools for Tizen</a>
+ <p>Learn about the Tizen-specific Visual Studio development tools. You can create an application project, edit the code to meet your needs, and run the application on the emulator or a target device.</p></li>
+</ul>
+For more information on the latest new features and the release plan roadmap, see <a href="introduction/whats_new.htm">What's New</a> and <a href="introduction/roadmap.htm">Roadmap</a>.
+
+<h2 id="runtime">Managed Runtime Advantages</h2>
+
+<p>A managed runtime offers the following advantages to your application development:</p>
+
+<ul>
+ <li><strong>Faster development</strong>
+ <p>Application development is accelerated since the managed runtime handles many functions that otherwise have to be coded into the application. The Tizen Native API and Tizen Web API already provide this benefit.</p></li>
+ <li><strong>Safer code</strong>
+ <p>Managed runtimes can handle, for example, bound checking, type safety, garbage collection, memory protection services, and objects being invoked directly. The Tizen Web API already provides some of these benefits, but not type safety, as JavaScript is not a strongly typed language.</p></li>
+ <li><strong>Lower deployment costs</strong>
+ <p>Component-based architecture makes it easier and faster to deploy applications in an enterprise environment characterized by multiple platforms, devices, and legacy systems.</p></li>
+ <li><strong>Better quality software</strong>
+ <p>Managed runtimes free you to focus on the business logic and code specific to the application, while reducing the number of coding errors.</p></li>
+ <li><strong>Cross-platform support</strong>
+ <p>The managed code is portable. Tizen .NET applications can have large portions of their logic applied to other systems supported by the .NET Core and Xamarin.Forms portions of the runtime.</p></li>
+</ul>
+
+<h2 id="features">Tizen .NET Features and Components</h2>
+
+<p>Tizen .NET enables you to build .NET applications with Xamarin.Forms and the Tizen .NET framework. Xamarin.Forms allows you to easily create a user interface, and the TizenFX API provides numerous interfaces to much of the hardware that is found in modern TV, mobile, wearable, and IoT devices.</p>
+
+<p align="center"><strong>Figure: Tizen .NET architecture</strong></p>
+<p align="center"><img alt="Tizen .NET architecture" src="images/cs_overview.png" /></p>
+
+<p>Tizen .NET consists of the following main components:</p>
-<p>The third preview of Tizen .NET, an application framework for Tizen based on .NET, is now available. The third preview stepped forward. Key new features are as follows:</p>
<ul>
- <li><strong>New Tools</strong>. Device Manager, Log Viewer, and API and Privilege checker were introduced with Visual Studio Tools for Tizen. Tizen-specific tools were added to further improve your productivity. </li>
-
- <li><strong>Project Wizard</strong>. Visual Studio Tools for Tizen provide a number of different options to build applications. For instance, you can build an application that runs on a single device type or an application that runs on multiple device types. You can build an application that runs on Tizen only or an application that runs on multiple platforms. The project wizard helps you to select the right project type with step-by-step guides.</li>
-
- <li><strong>Self-contained Application</strong>. Application developers can create and install them to target devices or emulators without pre-installed .NET runtime. </li>
-
- <li><strong>More Tizen platform-specific API</strong>. The third preview significantly increases the number of Tizen-specific API available for .NET developers. Following packages have become newly available. For the full pakage list, see <a href="https://developer.tizen.org/dev-guide/csapi/index.html">Tizen Platform-Specific API</a>.
- <ul>
- <li>Thumbnail Utility (capi-media-thumbnail-util)</li>
- <li>Wave Player (capi-media-wav-player)</li>
- <li>Tone Player (capi-media-tone-player)</li>
- <li>Media Stream Recording (capi-media-streamrecorder)</li>
- <li>Media Metadata Editor (capi-media-metadata-editor)</li>
- <li>Screen Mirroring (capi-media-screen-mirroring)</li>
- <li>Camera (capi-media-camera)</li>
- <li>Data Control (capi-data-control)</li>
- <li>Widget Viewer (widget_viewer_evas)</li>
- <li>FIDO (fido-client)</li>
- <li>Message (capi-messaing-messages)</li>
- <li>Email (capi-messaing-email)</li>
- <li>Input Method Manager (capi-ui-inputmethod-manager)</li>
- <li>Bluetooth (capi-network-bluetooth)</li>
- <li>Alarm (capi-appfw-alarm)</li>
- <li>Maps (capi-maps-service)</li>
- </ul></li>
- </ul>
+ <li><strong>.NET Core</strong>
+ <p>.NET Core is a general-purpose development platform maintained by Microsoft and the .NET community on <a href="https://github.com/dotnet/core" target="_blank">GitHub</a>. It is cross-platform, supporting Windows®, macOS, and Linux, and can be used in device, cloud, and embedded/IoT scenarios.</p>
+
+ <p>.NET Core is composed of the following parts:</p>
+
+ <ul>
+ <li>The <a href="https://github.com/dotnet/coreclr" target="_blank">.NET runtime</a>, which provides basic services, such as a type system, assembly loading, a garbage collector, and native interop.</li>
+ <li>A set of <a href="https://github.com/dotnet/corefx" target="_blank">framework libraries</a>, which provide primitive data types, application composition types, and fundamental utilities.</li>
+ <li>A <a href="https://github.com/dotnet/cli" target="_blank">set of SDK tools</a> and <a href="https://github.com/dotnet/roslyn" target="_blank">language compilers</a> that enable the base developer experience, available in the <a href="https://docs.microsoft.com/en-us/dotnet/articles/core/sdk" target="_blank">.NET Core SDK</a>.</li>
+ <li>The dotnet application host, which is used to launch .NET Core applications. It selects and hosts the runtime, provides an assembly loading policy, and launches the application. The application host is also used to launch SDK tools similarly.</li>
+ </ul>
+ </li>
+ <li><strong>Xamarin.Forms as a UI framework</strong>
+ <p>Xamarin.Forms is a cross-platform UI toolkit that allows you to efficiently create native user interface layouts that can be shared across iOS, Android™, Windows Phone, and Universal Windows Platform applications.</p>
+ </li>
+ <li><strong>TizenFX API</strong>
+ <p>Tizen .NET supports C# APIs, which expose Tizen-specific features:</p>
+ <ul>
+ <li><strong>Tizen.Account</strong> provides CRUD (Create, Read, Update, Delete) account management functionality and the OAuth Core RFC 6749 protocol.</li>
+ <li><strong>Tizen.Applications</strong> provides the Tizen application framework, including application state change events, inter-application messaging, and notification services.</li>
+ <li><strong>Tizen.Common</strong> provides predefined color names.</li>
+ <li><strong>Tizen.Content</strong> provides content management services, such as file and media downloading, storing and indexing audio and video content, and associating content types with helper applications.</li>
+ <li><strong>Tizen.Location</strong> manages geographical location services and geofencing.</li>
+ <li><strong>Tizen.Maps</strong> provides methods to create map-aware applications.</li>
+ <li><strong>Tizen.Messaging</strong> provides methods to receive push notifications.</li>
+ <li><strong>Tizen.Multimedia</strong> interacts with media services, including audio playback, recording, and device policy.</li>
+ <li><strong>Tizen.Network</strong> controls connectivity devices and retrieves network information.</li>
+ <li><strong>Tizen.Security</strong> provides access to secure storage for passwords, keys, certificates, and other sensitive data.</li>
+ <li><strong>Tizen.Sensor</strong> provides sensor types and sensor information.</li>
+ <li><strong>Tizen.System</strong> provides device-specific services, including status, system information and settings, feedback, and sensor control and access.</li>
+ <li><strong>Tizen.Telephony</strong> provides call, modem, network, and SIM information.</li>
+ <li><strong>Tizen.Uix</strong> provides methods to recognize speech, synthesize voice from text, and play synthesized sound data.</li>
+ <li><strong>Tizen.Log</strong> provides methods to print log messages to the Tizen logging system.</li>
+ <li><strong>Tizen.Tracer</strong> provides methods to write trace messages to the system trace buffer.</li>
+ </ul>
+ </li>
+</ul>
<script type="text/javascript" src="scripts/jquery.zclip.min.js"></script>
<script type="text/javascript" src="scripts/showhide.js"></script>
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+
+<head>
+ <meta http-equiv="content-type" content="text/html; charset=utf-8" />
+ <meta http-equiv="X-UA-Compatible" content="IE=9" />
+ <link rel="stylesheet" type="text/css" href="../css/styles.css" />
+ <link rel="stylesheet" type="text/css" href="../css/snippet.css" />
+ <script type="text/javascript" src="../scripts/snippet.js"></script>
+ <script type="text/javascript" src="../scripts/jquery.util.js" charset="utf-8"></script>
+ <script type="text/javascript" src="../scripts/common.js" charset="utf-8"></script>
+ <script type="text/javascript" src="../scripts/core.js" charset="utf-8"></script>
+ <script type="text/javascript" src="../scripts/search.js" charset="utf-8"></script>
+ <title>Creating Tizen Projects as Cross-platform Solutions</title>
+</head>
+
+<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
+
+<div id="toc-navigation">
+</div>
+
+<div id="container"><div id="contents"><div class="content">
+
+<h1 id="adding_project">Creating Tizen Projects as Cross-platform Solutions</h1>
+
+<p>The Xamarin cross-platform template consists of a shared PCL (Portable Class Library) and multiple platform-dependent application projects. If you create your Tizen project as a cross-platform solution, you can easily add other platform-dependent project versions, such as iOS and Android™, to the same solution later.</p>
+
+<p>To create a Tizen project as a cross-platform solution:</p>
+
+<ol>
+ <li>In the Visual Studio menu, go to <strong>File > New > Project</strong>.</li>
+ <li>Select <strong>Visual C# > Cross-Platform > Blank App (Xamarin.Forms Portable)</strong>.
+ <p align="center"><img alt="Select a cross-platform template" src="../images/xamarin_application.png" /></p>
+ </li>
+ <li>In the <strong>Solution Explorer</strong> view, right-click the new solution and select <strong>Add > New Project</strong>.</li>
+ <li>Select <strong>Tizen > Blank App (Tizen Xamarin.Forms Portable)</strong> and click <strong>OK</strong>.
+ <p align="center"><img alt="" src="../images/xamarin_blank_app_tizen.png" /></p>
+ </li>
+ <li>In the Tizen Project Wizard, define the Tizen application package name and profile, and click <strong>OK</strong>.
+ <p>The <strong>Solution Explorer</strong> view shows the 1 or 2 Tizen projects (depending on the selected profiles) that are added to the existing cross-platform Xamarin.Forms solution. The Tizen project is set as the startup project.</p>
+ <p align="center"><img alt="" src="../images/xamarin_solution_explorer_tizen.png" /></p>
+ </li>
+</ol>
+
+<h2>Problems with NuGet Package Versions</h2>
+
+<p>Since Tizen projects have dependencies with the Xamarin.Forms NuGet package version, you need to install the Xamarin.Forms NuGet package that has the same version as Xamarin.Forms.Platform.Tizen. Mismatched NuGet versions can cause build or packaging problems.</p>
+
+<p align="center"><strong>Figure: Mismatched NuGet version warning</strong></p>
+<p align="center"><img alt="" src="../images/xamarin_platform_mismatch.png" /></p>
+
+<p>To install the proper Xamarin.Forms NuGet package, right-click the solution in the <strong>Solution Explorer</strong> view and select <strong>Manage NuGet Packages for Solution</strong>.</p>
+
+<p align="center"><strong>Figure: Installing the correct NuGet package</strong></p>
+<p align="center"><img alt="" src="../images/xamarin_change_nuget_version.png" /></p>
+
+
+<script type="text/javascript" src="../scripts/jquery.zclip.min.js"></script>
+<script type="text/javascript" src="../scripts/showhide.js"></script>
+
+</div></div></div>
+
+<a class="top sms" href="#"><img src="../images/btn_top.gif" alt="Go to top" /></a>
+
+<div id="footer">
+<p class="footer">Except as noted, this content - excluding the Code Examples - is licensed under <a href="http://creativecommons.org/licenses/by/3.0/legalcode" target="_blank">Creative Commons Attribution 3.0</a> and all of the Code Examples contained herein are licensed under <a href="https://www.tizen.org/bsd-3-clause-license" target="_blank">BSD-3-Clause</a>.<br/>For details, see the <a href="https://www.tizen.org/content-license" target="_blank">Content License</a>.</p>
+</div>
+
+<script type="text/javascript">
+var _gaq = _gaq || [];
+_gaq.push(['_setAccount', 'UA-25976949-1']);
+_gaq.push(['_trackPageview']);
+(function() {
+var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+})();
+</script>
+
+</body>
+
+</html>
\ No newline at end of file
<body onload="prettyPrint()" style="overflow: auto;">
<div id="toc-navigation">
+
<div id="toc_border">
<div id="toc">
<p class="toc-title">Content</p>
<ul class="toc">
<li><a href="#creating">Creating a Project</a></li>
- <li><a href="#adding_class">Adding a Class Library and Restoring NuGet Manually</a></li>
- <li><a href="#adding_project">Adding a Tizen Project to an Existing Xamarin Cross Platform Project</a></li>
- <li><a href="#building">Building and Running Your Application</a></li>
- <li><a href="#enhancing">Enhancing Your Tizen .NET Application</a></li>
- <li><a href="#packaging">Packaging Your Tizen .NET Application</a></li>
+ <li><a href="#building">Building Your Application</a></li>
+ <li><a href="#running">Deploying and Running Your Application</a></li>
+ <li><a href="#enhancing">Enhancing Your Application</a></li>
+ <li><a href="#packaging">Packaging Your Application</a></li>
</ul>
</div>
</div>
<div id="container"><div id="contents"><div class="content">
<h1>Creating Your First Tizen .NET Application</h1>
-<p>The Tizen .NET framework allows you to efficiently and easily create beautiful applications for Tizen. A great way to experience this yourself is to follow the steps to your first Tizen .NET application. If you have to set up your development environment, please go to <a href="../tools/tools_overview.htm" rel="nofollow">set up the development environment</a>.</p>
+<p>The Tizen .NET framework allows you to easily and efficiently create applications for Tizen. Study the following instructions to help familiarize yourself with the Tizen .NET application development process. With the instructions, you can create and run a basic .NET application, which displays some text on the screen with no user interaction.</p>
-<p>To get started,</p>
+<ol>
+<li>Before you get started with developing Tizen applications, set up the <a href="installing.htm">development environment</a>.
+</li>
+<li><a href="#creating">Create a project</a> using Visual Studio.
+<p>This step shows how you can use a predesigned project template that creates all the basic files and folders required for your project.</p></li>
+<li><a href="#building">Build the application</a>.
+<p>After you have implemented code for the features you want, this step shows how you can build the application to validate and compile the code.</p></li>
+<li><a href="#running">Deploy and run the application</a>.
+<p>This step shows how you can deploy and run the application on the emulator or a real target device.</p></li>
+<li><a href="#enhancing">Enhance the application</a>.
+<p>This step shows how you can enhance your application by creating a UI and making small alterations to it to improve the usability of the application.</p></li>
+</ol>
-<ul class="rteindent2">
- <li><a href="#creating">Creating a new project</a></li>
- <li><a href="#building">Building and running your application</a></li>
-</ul>
+<h2 id="creating">Creating a Project</h2>
-<p>After completing the above steps, you will have created your first application, and you can move on to <a href="#enhancing">Enhancing your application</a>.</p>
+<p>The following example shows you how to create and configure a basic Tizen .NET application project in Visual Studio. An application project contains all the files that make up an application.</p>
+<p>The following figures illustrate the application to be created. The application screen displays the <strong>Welcome to Xamarin Forms!</strong> text and no user interaction is provided.</p>
-<h2 id="creating">Creating a Project</h2>
+<p align="center"><strong>Figure: Application running on the mobile emulator</strong></p>
-<p><span>To build a Tizen .NET application</span>, you must follow these general steps:</p>
+<p align="center"><img alt="Application running on the mobile emulator" src="../images/cs_first_building_emulator_mobile.png" /></p>
-<ol>
- <li>Create a project.</li>
- <li>Design the user interface for the application.</li>
- <li>Write code to implement the logic of the application.</li>
- <li>Build and deploy the application.</li>
-</ol>
+<p align="center"><strong>Figure: Application running on the TV emulator</strong></p>
-<p>You can perform all of these steps in the IDE. The Tizen .NET preview works in Microsoft's Visual Studio (2015). After making sure the <a href="../tools/tools_overview.htm">development environment is properly set up</a>, you can create a new Tizen .NET project:</p>
+<p align="center"><img alt="Application running on the TV emulator" src="../images/cs_first_building_emulator_tv1.png" /></p>
+
+<p>To create a new Tizen .NET project:</p>
<ol>
<li>Launch Visual Studio.</li>
- <li>To create a new project, select <strong>File > New > Project</strong>.
- <p align="center"><img alt="Create a new project" height="300" src="../images/cs_first01.png" width="533" /></p>
- </li>
- <li>In the New Project window, select <strong>Tizen </strong>in the <strong>Templates </strong>tree on the left, and select <strong>Blank App (Tizen Xamarin.Forms Portable)</strong>. Visual Studio defines a name, location and solution name for you, but you can modify the values: at least set the name to something meaningful.
- <p align="center"><img alt="Select a template" height="486" src="../images/cs_first02_1.png" width="700" /></p>
- Once you are happy with the name and location, click <strong>OK</strong>.
-
- <p align="center"><img alt="" height="302" src="../images/cs_first_creating_project_wizard_p3.png" width="702" /></p>
+ <li>In the Visual Studio menu, select <strong>File > New > Project</strong>.
+ <p align="center"><img alt="Create a new project" src="../images/cs_first_creating_menupath.png" /></p>
+ <p>The New Project dialog opens.</p>
+ </li>
+ <li>Select <strong>Templates > Visual C# > Tizen</strong>, and select the <strong>Blank App (Tizen Xamarin.Forms Portable)</strong> template.
+ <p>Define the project properties and click <strong>OK</strong>. You can enter the name, location, solution, and solution name.</p>
+ <p align="center"><img alt="Select a template" src="../images/cs_first_creating_new_project.png" /></p>
+ <p>The Tizen Project Wizard opens.</p></li>
+ <li>Define the package name and the profiles to add to your solution. Click <strong>OK</strong>.
+ <p align="center"><img alt="Tizen Project Wizard" src="../images/cs_first_creating_project_wizard.png" /></p>
+ <p>If you select the <strong>Common</strong> profile, you cannot select <strong>Mobile</strong> or <strong>TV</strong>.</p>
</li>
</ol>
-<p>Tizen Project Wizard window is shown as next step. You can define the package name and define which profiles are added in your solution. Click <strong>OK</strong>. <span> If you select <strong>Common</strong> profile, Mobile and TV profile cannot be selected.</span></p>
-
-<p>A solution with 2 or 3 projects is created:</p>
+<p>A solution with 2 or 3 projects is created and shown in the <strong>Solution Explorer</strong> view:</p>
<ul>
- <li align="left"><span>One project is named <projectname> (Portable) and contains the Xamarin.Forms code, which can be shared across platforms.</span></li>
- <li align="left">If you selected the common profile in the Tizen Project Wizard, a common project is added with <projectname>.Tizen suffix and contains the code to instantiate your common application within the Tizen framework.</li>
- <li align="left">If you selected the mobile profile in the Tizen Project Wizard, a mobile project is added with <projectname>.TizenMobile suffix and contains the code to instantiate your mobile application within the Tizen framework.</li>
- <li align="left">If you selected the TV profile in the Tizen Project Wizard, a TV project is added with <projectname>.TizenTV suffix and contains the code to instantiate your TV application within the Tizen framework.</li>
+ <li>The <strong><projectname> (Portable)</strong> project contains the Xamarin.Forms code shared across platforms.</li>
+ <li>If you select the common profile in the Tizen Project Wizard, a common project titled <strong><projectname>.Tizen</strong> is added. It contains code to instantiate your common application within the Tizen framework.</li>
+ <li>If you select the mobile profile in the Tizen Project Wizard, a mobile project titled <strong><projectname>.TizenMobile</strong> is added. It contains code to instantiate your mobile application within the Tizen framework.</li>
+ <li>If you select the TV profile in the Tizen Project Wizard, a TV project titled <strong><projectname>.TizenTV</strong> is added. It contains code to instantiate your TV application within the Tizen framework.</li>
</ul>
+<p align="center"><strong>Figure: Project with mobile and TV profiles</strong></p>
+<p align="center"><img alt="Project with mobile and TV profiles" src="../images/vstools_solution.png" /></p>
+<p>If you are already familiar with Xamarin.Forms, this project has the same structure as a Xamarin.Forms portable application. The "Portable" project is the portable class library and the others are the platform-specific projects; however, in the Tizen .NET preview, only the Tizen platform-specific project is generated.</p>
-<p>If you are already familiar with Xamarin.Forms, this project has exactly the same structure as a Xamarin.Forms portable application, with the "Portable" project being the portable class library and the others being the platform-specific projects; however, for the Tizen .NET preview, only the Tizen platform-specific project is generated.</p>
-
-<p align="center"><img alt="" src="../images/cs_first_creating_solution_explorer.png" /></p>
+<p>The <code>.cs</code> file in the portable project already contains simple Xamarin.Forms code that makes a basic UI.</p>
-<p>The <code>.cs</code> file in the portable project already contains simple Xamarin.Forms code, which makes a basic UI. Therefore, you can now build and run your application.</p>
+<h3 id="adding_class">Restoring NuGet Packages When Using Class Libraries</h3>
+ <p>If you add a Class Library (Tizen) to your solution in Visual Studio, the editing window for the class library CS files shows red wavy lines.</p>
+ <p align="center"><img alt="Red wavy lines" src="../images/cs_creating_classlibrary.png" /></p>
-<p>When you are done running your first application, you can <a href="#enhancing">enhance it further</a> by reading a brief overview of what the code generated by the template is doing, and learning about a few more concepts to add to your application appeal.</p>
-
-<h2 id="adding_class">Adding a Class Library and Restoring NuGet Manually</h2>
-
-<p>To add a class library and restore NuGet manually:</p>
+<p>To avoid the red lines, you must restore NuGet packages manually by adding the .NETStandard.Library to the class library references:</p>
<ol>
- <li>If you add a Class Library (Tizen) in Visual Studio, the editing window shows red wavy lines.
- <p align="center"><strong><img alt="Red wavy lines" height="253" src="../images/cs_creating04.png" width="768" /></strong></p>
- </li>
- <li>Right-click the solution item in the <strong>Solution Explorer</strong> view and click <strong>Restore NuGet Packages</strong>.
- <p align="center"><img alt="Restore NuGet packages" height="278" src="../images/cs_creating05.png" width="496" /></p>
-
- <p>Wait for the NuGet restoring to complete. Click the ClassLibrary project, and then click <strong>Refresh</strong> when the <strong>Refresh</strong> button appears.</p>
-
- <p align="center"><img alt="Refresh" height="230" src="../images/cs_creating06.png" width="300" /></p>
- </li>
- <li>The .NETStandard.Library shows up and the code looks clean.
- <p align="center"><strong><img alt=".NETStandard.Library" height="248" src="../images/cs_creating07.png" width="771" /></strong></p>
+ <li>Right-click the solution in the <strong>Solution Explorer</strong> view and select <strong>Restore NuGet Packages</strong>.
+ <p align="center"><img alt="Restore NuGet packages" src="../images/cs_creating_classlibrary_restore_nuget.png" /></p></li>
+ <li>Wait for NuGet package restoration to complete.
+ <p>In the <strong>Solution Explorer</strong> view, select the class library project, and when the <strong>Refresh</strong> button appears in the view toolbar, click it.</p>
+ <p align="center"><img alt="Refresh" src="../images/cs_creating_classlibrary_refresh.png" /></p>
+ <p>The .NETStandard.Library is added to the references, and the red lines in the code disappear.</p>
+ <p align="center"><img alt=".NETStandard.Library" src="../images/cs_creating_classlibrary_netstandard.png" /></p>
</li>
</ol>
-<p>The following figure shows warning messages that you can see in the <strong>Error List</strong> window when building the project. These can occur because the application is based on the Microsoft.NETCore.App and the Class library is based on NETStandard.Library, and the difference makes Visual Studio 2015 or 2017 show a warning. However, it is OK to run the project, because the Microsoft.NETCore.App includes the NETStandard.Library set.</p>
+<p>The following figure shows warning messages that can appear in the <strong>Error List</strong> window when building the project. These can occur because the application is based on Microsoft.NETCore.App but the class library is based on .NETStandard.Library, and the difference makes Visual Studio 2015 or 2017 show a warning. However, running the project is unaffected, because the Microsoft.NETCore.App includes the .NETStandard.Library set.</p>
<p align="center"><strong>Figure: Warning messages</strong></p>
+<p align="center"><img alt="Warning messages" src="../images/cs_creating_classlibrary_warnings.png"/></p>
-<p align="center"><img alt="Warning messages" height="169" src="../images/cs_creating08.png" width="656" /></p>
-
-<p align="center"> </p>
-
-<h2 id="adding_project">Adding a Tizen Project to an Existing Xamarin Cross Platform Project</h2>
-
-<p align="left">The Xamarin cross platform template consist of a shared PCL (Portable Class Library) and multiple platform dependent application projects for IOS and Android.</p>
-
-<p align="left">To add a new Tizen project:</p>
-
-<ol>
- <li align="left">In the Visual Studio menu, go to <strong>File > New > Project</strong> to open the <strong>New Project</strong> dialog.</li>
- <li align="left">Select <strong>Cross-Platform</strong> and <strong>Blank App (Xamarin.Forms Portable)</strong>.
- <p align="center"><img alt="" height="548" src="../images/xamarin_application.png" width="800" /></p>
- </li>
- <li align="left">Right-click the solution item in the <strong>Solution Explorer</strong> view and click <strong>Add > New Project</strong>.</li>
- <li align="left">Select Tizen <strong><strong>Blank App (Tizen Xamarin.Forms Portable)</strong></strong> and click <strong><strong>OK</strong></strong>.
- <p align="center"><img alt="" height="445" src="../images/add_tizen_project2.png" width="500" /></p>
- </li>
- <li align="left">Select the Tizen application’s package name and profile in the Tizen project wizard.
- <p align="center"><img alt="" height="105" src="../images/tizen_blank_app.png" width="400" /></p>
- </li>
- <li align="left">The <strong><strong>Solution Explorer</strong></strong> shows the 2 Tizen projects are added in your existing Xamarin.Forms solution. The Tizen project is set as a startup project.
- <p align="center"><img alt="" height="189" src="../images/solution_explorer_tizen_project2.png" width="261" /></p>
- </li>
-</ol>
-<div class="note"><strong>Note</strong>Since the Tizen projects have dependencies with the Xamarin.Forms NuGet package version, you need to install the Xamarin.Forms NuGet package that has the same version as Xamarin.Forms.Platform.Tizen. Mismatching NuGet versions can cause build or packaging problems. To install the proper Xamarin.Forms NuGet package, right-click the solution item in the <strong>Solution Explorer</strong> view and select <strong>Manage NuGet Packages for Solution</strong>.</div>
+<h2 id="building">Building Your Application</h2>
-<p align="center"><strong>Figure: Mismatched NuGet version warning</strong></p>
+<p>After you have created the application project, you can implement the required features. In this example, only the default features from the project template are used, and no code changes are required.</p>
-<p align="center"><img alt="" height="235" src="../images/platform_mismatch_warning.png" width="500" /></p>
+<p>When your application code is ready, build the application. The building process performs a validation check and compiles your files. You must sign the application package with an author certificate when building the application. If you have not yet registered a Tizen certificate in Visual Studio, see <a href="../tools/certificate_manager.htm">Certificate Manager</a>.</p>
-<p align="center"> </p>
+<p>There are 2 different ways to build the application:</p>
+<ul>
+ <li>In the Visual Studio menu, select <strong>Build > Build Solution</strong>.</li>
+ <li>In the <strong>Solution Explorer</strong> view, right-click the solution name and select <strong>Build</strong>.</li>
+</ul>
+<p>Tizen .NET applications are always deployed as installed packages. The package files have the <code>.tpk</code> file extension, and the package generation is controlled by the <a href="../tools/manifest_editor.htm">manifest file</a>. The Visual Studio template generates the manifest file (<code>tizen-manifest.xml</code>) to the top level of the <projectname>.Tizen project (if you create a project with both mobile and TV profiles, a separate manifest file is generated for each profile).</p>
-<p align="center"><strong>Figure: Installing the correct NuGet package</strong></p>
+ <p>For this example application, the default manifest is sufficient. If you want to make any changes in the application, such as changing the application icon or installing resources that are used by the application at runtime, see <a href="#packaging">Packaging Your Application</a>.</p>
+<p>After you have built the application, deploy and run it.</p>
-<p align="center"><img alt="" height="300" src="../images/change_nuget_version.png" width="700" /></p>
-<h2 id="building">Building and Running Your Application</h2>
+<h2 id="running">Deploying and Running Your Application</h2>
-<p>When you have created your first project, you can build and run it:</p>
+<p>To run the application, you must first deploy it to the target: either a device or an emulator. Deploying means transferring the package file (<code>.tpk</code>) to the target and invoking the Tizen package manager to install it.</p>
+<p>To deploy and run the application on the emulator:</p>
<ol>
- <li>Register an author certificate.</li>
- <li>Build the solution.</li>
- <li>Deploy the application to a target.</li>
- <li>Run the application.</li>
-</ol>
-
-<h3 id="Buildandrunyourapplication-1.RegisteranAuthorCertificate(onceonly)">1 Registering an Author Certificate</h3>
-
-<p><strong>If you already have registered<span> a certificate in Visual Studio or can use a default Tizen certificate, you can skip this step.</span></strong></p>
-
-<p>After installing the Visual Studio plugin, and before making Tizen package, it is useful to set up a signing certificate.</p>
-
-<p>You have 3 options:</p>
-
-<ul>
- <li>Use a default Tizen certificate
- <p>If you do not need to upload your application to Tizen Application store, you can use a default certificate and deploy your application in the Tizen Emulator too. You can check this in <strong>Menu > Tools > Options > Tizen > Certification</strong>. If you do not check the <strong>Sign the <code>.tpk </code> file using the following option</strong> box, your application is made with a default certificate.</p>
-
- <p align="center"><strong>Figure: Tizen default certificate registration</strong></p>
-
- <p align="center"><img alt="" src="../images/cs_first_building_certificate_01.png" /></p>
- </li>
- <li>Use a Tizen certificate profile
- <p>If you have used Tizen Studio and have already generated a certificate profile using the Tizen Certificate Manager (<strong>Menu > Tools > Tizen > Tizen Certificate Manager</strong>, the usage is added in tools menu too), the profile information can be read in <code>%ToolPath/Tizen/SDK/user-data/profile</code>.</p>
-
- <p align="center"><strong>Figure: Tizen certificate profile registration</strong></p>
-
- <p align="center"><img alt="" src="../images/cs_first_building_certificate_02.png" /></p>
+ <li>
+ <p>In the Visual Studio menu, select <strong>Tools > Tizen > Tizen Emulator Manager</strong>.</p>
+ <p>Alternatively, you can launch the Tizen Emulator Manager by clicking <strong>Launch Tizen Emulator</strong> in the Visual Studio toolbar.</p>
+ <p align="center"><img alt="Launch Tizen Emulator" src="../images/cs_launch_tizen_emu.png" /></p>
</li>
<li>
- <p align="left">Use your own certificates.</p>
-
- <p>If you already have author and distributor certificates, you can import them in <strong>Menu > Tools > Options > Tizen > Certification</strong>.</p>
-
- <p align="center"><strong>Figure: Tizen certificates registration </strong></p>
+ <p>In the Emulator Manager, select an emulator from the list and click <strong>Launch</strong>.</p><p>If no applicable emulator instance exists, <a href="../tools/emulator_manager.htm#create">create one</a>.</p>
+ <p align="center"><img alt="Tizen Emulator Manager" src="../images/cs_first_building_emulator_manager.png" /></p> </li>
+ <li>
+ <p>Once you launch an emulator instance, you can deploy the application by clicking the emulator instance in the Visual Studio toolbar.</p>
+ <p>You can change the deployment target in the Visual Studio toolbar by selecting the target from the drop-down list.</p>
+ <p align="center"><img alt="Tizen Emulator Manager" src="../images/vs_emulator_launch.png" /></p>
- <p align="center"><img alt="" src="../images/cs_first_building_certificate_03.png" /></p>
+ <p align="center"><img alt="Select deployment target" src="../images/cs_first_building_emulator_list.png" /></p>
</li>
-</ul>
-
-<p align="center"> </p>
-
-<h3 id="Buildandrunyourapplication-2.Build">2 Building the Solution</h3>
-
-<p>To build the solution, go to <strong>Build > Build Solution</strong> in the main Visual Studio menu (you can also right-click the solution title in the <strong>Solution Explorer</strong> window and select <strong>Build</strong>). If the build process works all the way through to the end, the final part of the build output window shows something similar to the following figure - indicating that a <code>.tpk</code> package was built.</p>
-
-<p align="center"><strong>Figure: Building process output</strong></p>
+ <li>If deployment is successful, the application icon is visible on the emulator or device screen. Click the icon to launch the application. The following figures show the launched application on the mobile and TV emulator.
-<p align="center"><img alt="" height="161" src="../images/cs_first_building_process.png" width="850" /></p>
-
-<p>Tizen .NET applications are always deployed as installed packages. The package files take the <code>.tpk</code> suffix, and the package generation is controlled by the manifest file. The Visual Studio template generates a package manifest, which is named <code>tizen-manifest.xml</code> and placed at the top level of the .Tizen project. The default manifest is sufficient to build these example applications without modification. If you need to make any changes, such as changing the icon displayed when the application is installed (it defaults to the Tizen logo), or installing resources that are used by the application at runtime, see <a href="#packaging">Packaging Your Tizen .NET Application</a>.</p>
-
-<h3>3 Deploying the Application</h3>
-
-<p>To run the application, you must first deploy it to the target: either a device or an emulator. Deploying means transfering the <code>.tpk</code> (package file) to the target and invoking the Tizen package manager to install it; this usually happens in a single command.</p>
-
-<p>To deploy to a target:</p>
+<p align="center"><img alt="Application running on the mobile emulator" src="../images/cs_first_building_emulator_mobile.png" /></p>
+<p align="center"><img alt="Application running on the TV emulator" src="../images/cs_first_building_emulator_tv1.png" /></p></li>
+</ol>
+<p>Visual Studio uses the Smart Development Bridge (SDB) to communicate with the target device or emulator. If you encounter problems with detecting the device in Visual Studio, you can check the SDB manually:</p>
<ol>
- <li>The target can be a development device (connected to a USB port), or the Tizen emulator. Launch the emulator from the Visual Studio menu by going to<strong> Menu > Tools > Tizen > Tizen Emulator Manager</strong>.
-
- <p align="center"><img alt="" height="589" src="../images/cs_first_building_emulator_manager.png" width="602" /></p>
- </li>
- <li>You can create emulators as shown above by clicking <strong>Create</strong>. For more information on creating emulator instances, see <a href="../tools/emulator_manager.htm">Emulator Manager</a>.</li>
- <li>The emulator launches after a small delay. When it is up and running, the display inside Visual Studio changes a bit, and the green debug button updates to show the running emulator.
- <p align="center"><img alt="" src="../images/cs_first_building_selected_emulator.png" /></p>
- </li>
+ <li>In the Visual Studio menu, select <strong>Tools > Tizen > Tizen Sdb Command Prompt</strong>.</li>
+ <li>At the command prompt, enter <code>sdb devices</code>.
+ <p align="center"><img alt="Emulator detection" src="../images/cs_first_building_sdb_prompt.png" /></p>
+ <p>A list of the attached devices appears.</p>
+ </li>
</ol>
-<p>Communication with the device happens through the SDB program (Smart Development Bridge). Visual Studio uses this program behind the scenes, so you normally do not have to use it directly, but in case there are problems, you can run the SDB manually to check that it actually finds the device.<br />
-To check the SDB, click <strong>Menu > Tools > Tizen > Tizen Sdb Command Prompt</strong>, and type sdb devices.</p>
-
-<p>The following figure shows an example of a successful emulator detection.</p>
-
-<p align="center"><strong>Figure: Emulator detection</strong></p>
+<p>If problems occur during deployment, try to install the application manually using the SDB:</p>
-<p align="center"><img alt="Emulator detection" height="450" src="../images/cs_first08.png" width="857" /></p>
-
-<p>If you want to change the target to be deployed, you can change it in the Visual Studio configuration manager as shown in the following figure. After selecting the right target in the combo box, go to debugging or start without debugging.</p>
-
-<p align="center"><strong>Figure: Emulator list</strong></p>
-
-<p align="center"><img alt="" src="../images/cs_first_building_emulator_list.png" /></p>
-
-<h3 id="Buildandrunyourapplication-3.Run">4 Running the Application</h3>
+<ul>
+<li>Mobile application:
+<pre class="prettyprint">
+$ sdb install <path-to-package>/XamarinApplication1.TizenMobile.tpk
+</pre>
+</li>
+<li>TV application:
+<pre class="prettyprint">
+$ sdb install <path-to-package>/XamarinApplication1.TizenTV.tpk
+</pre>
+</li>
+</ul>
-<p>After the deployment, you can launch the application. If the deployment was successful, the application icon is visible on the device screen. Click the icon to launch the application. The following figure shows the launched application (as seen on the emulator).</p>
-<p align="center"><strong>Figure: Application running on the mobile emulator</strong></p>
+<h2 id="enhancing">Enhancing Your Application</h2>
-<p align="center"><img alt="Application running" height="497" src="../images/cs_first09_1.png" width="290" /></p>
+<p>Xamarin.Forms provides a way to build portable applications which run in a native way. It provides a set of controls for building a user interface, as well as generates code which adapts the user interface code to use the native facilities of the supported platforms. The following is a brief introduction to the Xamarin.Forms controls, and how to use them to build on the application you have just created.</p>
-<p align="center"><strong>Figure: Application running on the TV emulator</strong></p>
+<h3>Understanding the Source Code</h3>
-<p align="center"><img alt="" src="../images/cs_first_building_emulator_tv1.png" /></p>
+<p>The C# code from your first application displays a label centered on the screen, containing the <strong>Welcome to Xamarin Forms!</strong> text. This XamarinApplication1 application created from the template is set up and ready to be built and run by Visual Studio right after you create it, as described above.</p>
-<p>If the deployment had problems, try to use the SDB to install the application:</p>
+<p>The Xamarin.Forms controls used to create the user interface of a Tizen .NET application can be broadly categorized into 4 groups:</p>
-<pre class="prettyprint">
-$ sdb install <path-to-package>/XamarinApplication1.TizenMobile.tpk </pre>
+<ul>
+ <li><code>Pages</code> represent screens within an application. The UI of an application is built from one or more pages and with a navigation mechanism, if needed. The navigation scheme is specified by the <code>INavigation</code> interface. Many pages are of the <code>ContentPage</code> type, which describes the view of a single screen.</li>
+ <li><code>Layouts</code> are containers used to compose views into logical structures. Some available types are absolute, grid, relative, and stack layouts; each provide mechanisms, such as orientation, spacing, and padding, to control the layout. The <code>StackLayout</code> class is a basic layout where you can simply stack controls on top of, or side-by-side, one another. Layouts can also be bundled with and nested into each other.</li>
+ <li><code>Views</code> are the controls displayed on the user interface, such as labels, buttons, and text entry boxes.</li>
+ <li><code>Cells</code> are specialized elements used for items in tables and lists, which help describe how the items must be rendered.</li>
+</ul>
-<div>
-<p align="left">or</p>
+<p>The following shows the portable code portion of the Tizen Xamarin.Forms Portable project <code>XamarinApplication1.cs</code> file, generated by the template:</p>
-<div>
<pre class="prettyprint">
-$ sdb install <path-to-package>/XamarinApplication1.TizenTV.tpk </pre>
-
-<p align="left">If the installation succeeds, the application icon shows up on the emulator or device screen, and you can click it to launch the application.</p>
-</div>
-</div>
-
-<h2 id="enhancing">Enhancing Your Tizen .NET Application</h2>
-
-<p>The C# code from your first application displays a label centered on the screen, containing the <strong>Welcome to Xamarin Forms!</strong> text. The <strong>Hello</strong> application (created from the template) is set up and ready to be built and run by Visual Studio right after you create it, as shown in the preceding sections of this topic.</p>
-
-<p>Xamarin.Forms provides a way to build portable applications which run in a native way: it provides a set of controls to help build a user interface, as well as generating code which adapts the user interface code to use the native facilities of the supported platforms. The following information just scratches the surface of these controls, but it is enough to give you an idea of how to build on the initial application.</p>
-
-<p>The following example shows the portable code portion of the Tizen Xamarin.Forms Portable project <code>XamarinApplication1.cs</code> file, generated by the template:</p>
-
-<pre class="code">
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Xamarin.Forms;
-
+
namespace XamarinApplication1
{
public class App : Application
{
public App()
{
- // Root page of your application
+ /// Root page of your application
MainPage = new ContentPage
{
Content = new StackLayout
{
VerticalOptions = LayoutOptions.Center,
- Children = {
- new Label {
+ Children =
+ {
+ new Label
+ {
HorizontalTextAlignment = TextAlignment.Center,
Text = "Welcome to Xamarin Forms!"
}
}
protected override void OnStart()
{
- // Handle when your app starts
+ /// Handle when your app starts
}
protected override void OnSleep()
{
- // Handle when your app sleeps
+ /// Handle when your app sleeps
}
protected override void OnResume()
{
- // Handle when your app resumes
+ /// Handle when your app resumes
}
}
}
</pre>
-<p> </p>
-
-<p>The Xamarin.Forms controls used to create the user interface of a Tizen .NET application can be roughly categorized into 4 groups:</p>
+<p>This application is constructed with the following Xamarin.Forms controls:</p>
<ul>
- <li><code>Pages</code> represent screens within an application. The UI of an application is built from one or more pages and with a navigation mechanism, if needed. The navigation scheme is specified by the <code>INavigation</code> interface. Many pages are of the <code>ContentPage</code> type, which describes the view of a single screen.</li>
- <li><code>Layouts</code> are containers used to compose views into logical structures. Some available types are absolute, grid, relative, and stack layouts; each provide mechanisms, such as orientation, spacing, and padding, to control the layout. The <code>StackLayout</code> class is a basic layout where you just stack controls on top of one another (or side-by-side). Layouts can be bundled and nested in each other.</li>
- <li><code>Views</code> are the controls displayed on the user interface, such as labels, buttons, and text entry boxes.</li>
- <li><code>Cells</code> are specialized elements used for items in tables and lists, which help describe how the items must be rendered.</li>
-</ul>
-
-<p>You can read all about how Xamarin.Forms works at the <a class="external-link" href="https://developer.xamarin.com/guides/xamarin-forms/" rel="nofollow">Xamarin Developer Center</a>. In addition, there is a <a class="external-link" href="https://developer.xamarin.com/guides/xamarin-forms/creating-mobile-apps-xamarin-forms/" rel="nofollow">comprehensive book about Xamarin.Forms</a> from Microsoft Press, which is available as a free download. This topic does not duplicate the definitive documentation, only introduces the controls in use in the example above, and a bit more.</p>
-
-<p>The Xamarin.Forms controls in play in this application:</p>
-
-<ol>
- <li>The <code>App</code> class is declared, deriving from the <a class="external-link ext" href="https://developer.xamarin.com/api/type/Xamarin.Forms.Application/" rel="nofollow">Application</a> class, which is the Xamarin.Forms class that represents a cross-platform mobile application.</li>
- <li>The <code>App</code> class constructor creates a <code>ContentPage</code> instance (line 14) where you set up the view to display.</li>
- <li>You assign what you want to display to the <code>Content</code> property of that class.
- <p>In this case, the content is a container, specifically a <code>StackLayout</code> instance (line 16). This is just a layout that positions its child elements in a single vertical (by default) or horizontal line - thus the name: the elements are "stacked" on top of one another.</p>
+ <li>The <code>App</code> class is declared, deriving from the <a href="https://developer.xamarin.com/api/type/Xamarin.Forms.Application/" target="_blank">Xamarin.Forms.Application</a> class, which represents a cross-platform mobile application.</li>
+ <li>The <code>App</code> class constructor creates a <code>ContentPage</code> instance where you set up the view to display.</li>
+ <li>You assign what you want to display to the <code>Content</code> property of the <code>ContentPage</code> class.
+ <p>In this case, the content is a container, specifically a <code>StackLayout</code> instance. This layout positions ("stacks") its child elements in a single vertical (default) or horizontal line.</p>
</li>
- <li>You set up the child elements by adding to the <code>Children</code> property (line 19) - in this case just a single <code>Label</code> instance (line 20), whose <code>Text</code> property you set to the message you want to display.</li>
- <li>Some lines (18 and 21) implement some control over the layout.</li>
- <li>Besides the <code>App</code> constructor, the rest of the file is just boilerplate - event handlers from the <code>Application</code> class that can be filled in if the application needs code to handle application state changes.</li>
-</ol>
-
-<p>That is a very brief view without any real details; the Xamarin.Forms documentation goes into much more detail on each of the classes, interfaces, properties, and attributes involved and is a good place to do further research.</p>
+ <li>Child elements are added to the <code>Children</code> property. In this example, a single <code>Label</code> instance is added, whose <code>Text</code> property is the message you want to display.</li>
+ <li>Some lines implement control over the layout. For example, the stack is set to vertically center the child elements, and the label is set to use center-alignment for its text.</li>
+ <li>Besides the <code>App</code> constructor, the rest of the file is just a template. Event handlers from the <code>Application</code> class can be filled in if the application needs to handle application state changes.</li>
+</ul>
-<p>The code does not show the instantiation of the <code>App</code> class. Since application launching is platform-specific, the launching part, including the instatiation of the <code>App</code> class and the declaration of the <code>Main()</code> method (required as the entry point of every C# program), happens in the .Tizen project, in the matching file there. For example, if the file you are looking at in the portable project is named <code>XamarinApplication1.TizenMobile.cs</code> or <code>XamarinApplication1.TizenTV.cs</code>, the platform-specific file is <code>XamarinApplication1.TizenMobile.cs</code> or <code>XamarinApplication1.TizenTV.cs</code> <span> </span>in the .Tizen project. For an application like this one, which just uses Xamarin.Forms controls, the generated code at the .Tizen part of the project contains everything needed, and you do not need to make any modifications. The following example shows the content of the <code>XamarinApplication1.TizenMobile.cs</code> or <code>XamarinApplication1.TizenTV.cs</code> file:</p>
+<p>The code does not show the instantiation of the <code>App</code> class. Since application launching is platform-specific, the launching part, including the instantiation of the <code>App</code> class and the declaration of the <code>Main()</code> function (required as the entry point of every C# program), happens in the <projectname>.Tizen project, in the matching file there. For example, if the file you are looking at in the portable project is named <code><projectname>.cs</code>, the platform-specific file in the <projectname>.Tizen project is <code><projectname>.TizenMobile.cs</code> or <code><projectname>.TizenTV.cs</code>. For an application like this one, which uses only Xamarin.Forms controls, the generated code at the <projectname>.Tizen part of the project contains everything needed, and you do not need to make any modifications. The following example shows the content of the <code><projectname>.TizenMobile.cs</code> file:</p>
-<pre class="code">
+<pre class="prettyprint">
using System;
-
+
namespace XamarinApplication1.TizenMobile
{
class Program : global::Xamarin.Forms.Platform.TizenMobile.FormsApplication
}
</pre>
-<h3 id="EnhancingYourFirstTizen.NETApplication-Howtodefineabutton">Defining a Button</h3>
+<h3>Adding a Button and Second Label</h3>
+
+<p>To modify and build a new application, create a new project. The default name for the second project is <strong>XamarinApplication2</strong> (as shown in the namespace declaration in the following step list), but of course you can name it anything you want.</p>
+
+<p>The basic template uses a label which displays text in an area of the screen. The properties inherited from the base classes of <code>Label</code> give control over the display: font attributes, families, and sizes, as well as layout options. Modify the application by adding a button control. It is similar to the label, but is specifically designed to react to click events. As a result, the <code>Button</code> class defines the <code>Clicked</code> event, which tells the application what to do when the click event takes place.</p>
+
+<p>In order to do something visible on the screen to show that you have received the click event, define another label. Give the new label a value to be displayed in the initial state, and make the button click event handler update the text and button color once the click event triggers.</p>
-<p>The basic template uses a label, which displays text in an area of the screen. The properties inherited from the base classes of <code>Label</code> give lots of control over the display: font attributes, families, and sizes as well as layout options. A button control is relatively similar, but is specifically designed to react to click events. As a result, the <code>Button</code> class defines an event called <code>Clicked</code>, which tells the application what to do when the click event takes place. To instantiate a generic button:</p>
-<pre class="code">
+<p>To modify the application by adding a button and label:</p>
+<ol>
+ <li>Instantiate a generic button:
+ <ol type="a">
+ <li>Add the <code>OnButtonClicked</code> event handler to the button's <code>Clicked</code> event:
+<pre class="prettyprint">
Button button = new Button
{
Text = "Click here!"
};
button.Clicked += OnButtonClicked;
-</pre>
-
-<p>The above example adds the <code>OnButtonClicked</code> method to the button's <code>Clicked</code> event, and you need to define that method. When an event triggers, 2 parameters are delivered to any handler set up to watch it. The first parameter is an object representing the control that triggered the event and the second parameter is the event data appropriate to the event type:</p>
-
-<pre class="code">
+</pre></li>
+<li>Define the <code>OnButtonClicked</code> event handler.
+<p>When an event triggers, 2 parameters are delivered to any handler set up to watch it. The first parameter is an object representing the control that triggered the event and the second parameter is the event data appropriate to the event type:</p>
+<pre class="prettyprint">
void OnButtonClicked(object sender, EventArgs e)
{
- // Do something with the click event
+ /// Do something with the click event
}
</pre>
-
-<h3 id="EnhancingYourFirstTizen.NETApplication-AddingaLabelwhichwillbeupdatedwhenthebuttonisclicked">Adding a Label to be Updated When the Button is Clicked</h3>
-
-<p>To build the modified application, create a new project. The default name for the second project is <strong>XamarinApplication2</strong> (as shown in the namespace declaration in the following code example), but of course you can name it anything you want.</p>
-
-<p>In order to do something visible on the screen to show that you actually got the click event, define another label. Give the label a value (by setting the <code>Text</code> property) to be displayed in the initial state, and have the event handler update the <code>Text</code> property (and color) once the click event triggers:</p>
-
-<ol>
- <li>Since the the click event triggers outside the class constructor, you must declare the label and a click counter up at the class level (lines 11-12).</li>
- <li>The button is instantiated (line 16) as is the new label (line 23): these 2 are then included as children of the <code>StackLayout</code> (lines 41-42), so they are stacked below the label from the initial program.</li>
- <li>In this example, the initial text of the first label is changed to "Welcome to Tizen!".</li>
- <li>The event handler is added (lines 47-52). In it, increment the click counter, build a string showing how many times the button has been clicked, and set the <code>Text</code> property of the label to that string. Just for visual effect, also set the color of the label to something different than the initial color (which was set at line 26).</li>
-</ol>
-
-<p>The following example shows the modified code:</p>
-
-<pre class="code">
+ </li>
+ </ol></li>
+ <li>Instantiate a new label and define its property changes in the click event handler:
+ <ol type="a">
+ <li>Since the click event triggers outside the class constructor, declare the label and a click counter at the class level:
+<pre class="prettyprint">
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Xamarin.Forms;
-
+
namespace XamarinApplication2
{
public class App : Application
{
- Label label;
- int clicks = 0;
-
+ <span class="highlight">Label label;</span>
+ <span class="highlight">int clicks = 0;</span>
+</pre></li>
+ <li>Instantiate the button and label, and include them later as children of the <code>StackLayout</code>, so they are stacked below the label from the initial program. Give the new label a value to be displayed in the initial state by setting the <code>Text</code> property.
+<pre class="prettyprint">
public App()
{
- Button button = new Button
- {
- Text = "Click here!",
- BackgroundColor = Color.Red,
- HorizontalOptions = LayoutOptions.Center,
- };
- button.Clicked += OnButtonClicked;
- label = new Label
- {
- Text = "unclicked",
- HorizontalOptions = LayoutOptions.Center,
- };
-
- // The root page of your application
+ <span class="highlight">Button button = new Button</span>
+ <span class="highlight">{</span>
+ <span class="highlight">Text = "Click here!",</span>
+ <span class="highlight">BackgroundColor = Color.Red,</span>
+ <span class="highlight">HorizontalOptions = LayoutOptions.Center,</span>
+ <span class="highlight">};</span>
+ <span class="highlight">button.Clicked += OnButtonClicked;</span>
+ <span class="highlight">label = new Label</span>
+ <span class="highlight">{</span>
+ <span class="highlight">Text = "unclicked",</span>
+ <span class="highlight">HorizontalOptions = LayoutOptions.Center,</span>
+ <span class="highlight">};</span>
+
+ /// The root page of your application
MainPage = new ContentPage
{
Content = new StackLayout
HorizontalTextAlignment = TextAlignment.Center,
Text = "Welcome to Tizen!"
},
- button,
- label,
+ <span class="highlight">button,</span>
+ <span class="highlight">label,</span>
}
}
};
}
+</pre></li>
+ <li>Change the initial text of the first label to "Welcome to Tizen":
+<pre class="prettyprint">
+ Content = new StackLayout
+ {
+ VerticalOptions = LayoutOptions.Center,
+ Children = {
+ new Label {
+ HorizontalTextAlignment = TextAlignment.Center,
+ <span class="highlight">Text = "Welcome to Tizen!"</span>
+ },
+ button,
+ label,
+ }
+ }
+</pre></li>
+ <li>Modify the click event handler content.
+ <p>Increment the click counter, build a string showing how many times the button has been clicked, and set the <code>Text</code> property of the label to that string.</p>
+ <p>Just for visual effect, you can also set the button background color to something different than the initial color set when the button was instantiated.</p>
+<pre class="prettyprint">
void OnButtonClicked(object s, EventArgs e)
{
- clicks += 1;
- label.Text = String.Format("Number of clicks: {0}", clicks);
+ <span class="highlight">clicks += 1;</span>
+ <span class="highlight">label.Text = String.Format("Number of clicks: {0}", clicks);</span>
+ <span class="highlight">button.BackgroundColor = Color.Blue;</span>
}
protected override void OnStart()
{
- // Handle when your app starts
+ /// Handle when your app starts
}
protected override void OnSleep()
{
- // Handle when your app sleeps
+ /// Handle when your app sleeps
}
protected override void OnResume()
{
- // Handle when your app resumes
+ /// Handle when your app resumes
}
}
-
-
}
-</pre>
+</pre></li>
+</ol></li>
+</ol>
-<p>The following image shows what happens if you try out the modified code and run the application with it. At the startup, the button is red and the text below the button is <strong>unclicked</strong>. After a couple of clicks, the click counter is displayed below the button, and the button color has changed.</p>
+<p>The following image shows what happens when you run the modified code. At startup, the button is red and the text below the button is <strong>unclicked</strong>. After a couple of clicks, the click counter is displayed below the button, and the button color has changed.</p>
<p align="center"><strong>Figure: Enhanced application</strong></p>
+<p align="center"><img alt="Enhanced application" src="../images/cs_first_building_emulator_enhanced.png" /></p>
-<p align="center"><img alt="Enhanced application" height="516" src="../images/cs_enhancing01_1.png" width="290" /> <img alt="" height="516" src="../images/cs_enhancing02_1.png" width="290" /></p>
+<p>This topic only introduces the controls in use in the example above. For more information on Xamarin.Forms, see the <a href="https://developer.xamarin.com/guides/xamarin-forms/" target="_blank">Xamarin Developer Center</a>. There is also <a href="https://developer.xamarin.com/guides/xamarin-forms/creating-mobile-apps-xamarin-forms/" target="_blank">a comprehensive book about Xamarin.Forms</a> available as a free download from Microsoft Press.</p>
-<h2 id="packaging">Packaging Your Tizen .NET Application</h2>
+<h2 id="packaging">Packaging Your Application</h2>
-<p>This section gives a basic overview of packaging, to aid in understanding how to make simple changes. For more complex applications, see the packaging information in the Tizen documentation.</p>
+<p>A Tizen .NET application is deployed in the form of an installable package, with the package file extension <code>.tpk</code>. A Tizen .NET package has a relatively simple structure: internally it is a ZIP file with content that matches the directory layout of the project.</p>
-<p>A Tizen .NET application is deployed in the form of an installable package, where the package file takes the suffix <code>.tpk</code>. A Tizen .NET package has a relatively simple structure: internally it is a zipfile with content that matches the directory layout of the project.</p>
-
-<p>In the following figure, the layout of the platform specific (.Tizen) project is shown. It includes the <code>lib</code>, <code>res</code>, and <code>shared</code> (with a <code>res</code> subdirectory containing an image file) directories , and the <code>tizen-manifest.xml</code> file. There is also the <code>bin</code> directory, which Visual Studio only shows if you select the <span>Show all files</span> option for the solution. These pieces all go into the package.</p>
-
-<p align="center"><strong><span>Figure: Project layout</span></strong></p>
-
-<p align="center"><img alt="Project layout" height="546" src="../images/cs_first_creating_solution_explorer.png" width="346" /></p>
-
-<p>Package generation (and in fact installation) is controlled by a package manifest file, which is named <code>tizen-manifest.xml</code>. The Visual Studio template generates a package manifest, and places it at the top of the directory tree of the .Tizen project. The following figure shows the <code>.tpk</code> file for the initial application, to illustrate how the combination of the directory layout and the package manifest leads to the actual package.</p>
-
-<p align="center"><strong><span>Figure: Package content</span></strong></p>
+<p>The package contains the following:</p>
+<ul>
+ <li>The <code>shared</code> directory, which is for items that are considered system-wide (shareable).
+ <p>The application icon is packaged in the <code>shared/res</code> directory on installation, and the icon appears on the home screen with the icons for the other applications. You can either replace the icon (which is just a copy of the default Tizen logo) with one of your own using the file name generated by Visual Studio, or put a new icon in the same project directory and update the package manifest to indicate the new name.</p></li>
+ <li>The <code>res</code> directory, which is for application-private resources.
+ <p>If the application needs a file to open at runtime, it can be placed here.</p></li>
+ <li>The <code>bin</code> directory, which contains the generated application executable.</li>
+ <li>The <code>lib</code> directory, which contains the generated application support code.
+ <p>If you use nugget libraries, they are imported in the lib directory.</p></li>
+ <li>The package manifest, which defines the application properties and is used at the installation time.</li>
+ <li>2 signature files (author and distributor), which are checked at the installation time.</li>
+</ul>
-<p align="center"><img alt="Package content" height="117" src="../images/cs_first_packaging_content.png" width="329" /></p>
+<p>The following figure shows the layout of the platform-specific (Tizen) project. It includes the <code>lib</code>, <code>res</code>, and <code>shared</code> (with a <code>res</code> subdirectory containing an image file) directories, and the <code>tizen-manifest.xml</code> file. There is also the <code>bin</code> directory, which Visual Studio only shows if you select the <strong>Show all files</strong> option for the solution. These pieces all go into the package.</p>
-<p>The initial points to learn here are:</p>
+<p align="center"><strong>Figure: Project layout</strong></p>
+<p align="center"><img alt="Project layout" src="../images/vstools_solution.png" /></p>
-<ul>
- <li>The <code>shared</code> directory is for items that are considered systemwide (shareable). The application icon is packaged in <code>shared/res</code>: on installation, the icon appears on the home screen with the icons for the other applications. You can either replace the icon (which is just a copy of the default Tizen logo) with one of your own using the file name generated by Visual Studio, or put a new icon in the same project directory and update the package manifest to indicate the new name.</li>
- <li>The <code>res</code> directory is for application-private resources. If the application needs a file to open at runtime, it can be placed here.</li>
- <li>The <code>bin</code> directory contains the generated application executable.</li>
- <li>The <code>lib</code> directory contains the generated application support code.<br />
- If you use nugget libraries, they are imported in the <code>lib</code> directory.</li>
- <li>The package manifest is included in the package, as it is used at the installation time.</li>
- <li>2 signature files (author and distributor) are included, as they are checked at the installation time.</li>
-</ul>
+<p>Package generation (and in fact installation) is controlled by the <code>tizen-manifest.xml</code> package manifest file. The following figure shows the <code>.tpk</code> file for the initial application, to illustrate how the combination of the directory layout and the package manifest leads to the actual package.</p>
-<p>Other information relating to packaging includes declarations of features and privileges, and the placement of language-specific files.</p>
+<p align="center"><strong>Figure: Package content</strong></p>
+<p align="center"><img alt="Package content" src="../images/cs_first_packaging_content.png" /></p>
+<p>When packaging your application, you also need to consider whether any feature or privilege declarations are needed in the manifest file, and how to place any language-specific files.</p>
<script type="text/javascript" src="../scripts/jquery.zclip.min.js"></script>
<script type="text/javascript" src="../scripts/showhide.js"></script>
<script type="text/javascript" src="../scripts/common.js" charset="utf-8"></script>
<script type="text/javascript" src="../scripts/core.js" charset="utf-8"></script>
<script type="text/javascript" src="../scripts/search.js" charset="utf-8"></script>
- <title>Downloading Visual Studio Tools for Tizen Preview</title>
+ <title>Getting Started</title>
</head>
<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
<div id="container"><div id="contents"><div class="content">
- <h1>Downloading Visual Studio Tools for Tizen Preview</h1>
+ <h1>Getting Started</h1>
-<div class="note"><strong>Note </strong> The latest Visual Studio Tools for Tizen installer automatically detects the installed Visual Studio version (2015 or 2017), and installs the applicable Tizen .NET development environment.</div>
+<p>The Visual Studio Tools for Tizen Preview is a collection of tools for developing Tizen .NET applications. It consists of a Visual Studio extension for templates, a debugger, and the Tizen Emulator. The Visual Studio Tools for Tizen Preview runs on Windows® with Visual Studio.</p>
-<p>The Visual Studio Tools for Tizen P<span>review </span>is a collection of tools for developing Tizen .NET applications. It consists of Visual Studio extension for templates, debugger, and Tizen Emulator. <span>The Visual Studio Tools for Tizen P</span><span>review</span> runs on Windows® with Visual Studio.</p>
+<p>To get started with developing your own Tizen .NET applications:</p>
+<ul>
+<li><a href="#download">Download</a> and <a href="installing.htm">install</a> Visual Studio Tools for Tizen.</li>
+<li><a href="first_app.htm">Create your first Tizen .NET application</a>.</li>
+<li><a href="cross_platform_project.htm">Create Tizen projects as cross-platform solutions</a>.</li>
+<li><a href="porting_xamarinforms.htm">Port existing Xamarin.Forms applications</a> to Tizen.</li>
+</ul>
+
+<h2 id="download">Downloading Visual Studio Tools for Tizen</h2>
-<p><span>For the installation of Visual Studio Tools for Tizen </span><span>Preview, your system requires </span><span>more than 1.5GB</span><span> available disk space.</span></p>
+<div class="note"><strong>Note</strong> The latest Visual Studio Tools for Tizen installer automatically detects the installed Visual Studio version (2015 or 2017), and installs the applicable Tizen .NET development environment.</div>
-<p>You can download by selecting a server below where is located near your side.</p>
+<p>Download the Visual Studio Tools for Tizen Preview installer by selecting the location that is closest to you:</p>
<ul>
<li><a href="http://download.tizen.org/sdk/vstools/VisualStudioToolsforTizen-preview-3.exe">Origin</a></li>
<body onload="prettyPrint()" style="overflow: auto;">
<div id="toc-navigation">
- <div id="profile">
- <p><img alt="Mobile C#" src="../images/mobile_s_cs.png"/> <img alt="TV C#" src="../images/tv_s_cs.png"/></p>
- </div>
-
<div id="toc_border"><div id="toc">
- <p class="toc-title">Dependencies</p>
- <ul class="toc">
- <li>Tizen 4.0 and Higher for Mobile and TV</li>
- </ul>
+
+ <p class="toc-title">Dependencies</p>
+ <ul class="toc">
+ <li>Tizen 4.0 and Higher</li>
+ </ul>
+
<p class="toc-title">Content</p>
<ul class="toc">
<li><a href="#basic_usage">Basic Usage</a></li>
<title>Installing Visual Studio Tools for Tizen</title>
</head>
-<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
+<body onload="prettyPrint()" style="overflow: auto;">
<div id="toc-navigation">
+ <div id="toc_border"><div id="toc">
+ <p class="toc-title">Content</p>
+ <ul class="toc">
+ <li><a href="#prerequisites">Prerequisites</a></li>
+ <li><a href="#installing">Installing Visual Studio Tools for Tizen Preview</a></li>
+ <li><a href="#configure_haxm">Configuring Intel® HAXM</a></li>
+ </ul>
+ </div></div>
</div>
-
<div id="container"><div id="contents"><div class="content">
<h1>Installing Visual Studio Tools for Tizen</h1>
-<h2>Prerequisites</h2>
-
-<p>To work with Visual Studio Tools for Tizen, make sure that your system meets the following requirements.</p>
-
-<p>For the installation of Visual Studio Tools for Tizen Preview, your system requires more than 1.5GB available disk space.</p>
+<p>Set up the Tizen C# development environment by installing Visual Studio Tools for Tizen. Before installing, make sure that your development computer fulfills the prerequisites.</p>
-<h3 align="left"> Visual Studio 2017 or Visual Studio 2015 Update 3</h3>
+<h2 id="prerequisites">Prerequisites</h2>
-<p align="left">Visual Studio Tools for Tizen works with all variations including Community. Installation or re-installation with the C#/.NET (Xamarin v3.1.1) in Cross Platform Mobile Development is recommended.</p>
+<p>To work with Visual Studio Tools for Tizen, your computer must have:</p>
-<h3 align="left">.NET Core 1.0.1 Tools Preview 2 or later</h3>
+<ul>
+ <li>At least 1.5 GB of available disk space</li>
-<p align="left">This update is needed to set the .NET development environment. For more information, see <a class="ext" href="https://www.microsoft.com/net/core#windows" target="_blank">https://www.microsoft.com/net/core#windows</a>.</p>
+ <li>Visual Studio 2017 or Visual Studio 2015 Update 3
-<h3 id="java">Java Development Kit (JDK) Requirements</h3>
+<p>Visual Studio Tools for Tizen works with all Visual Studio variations, including Community. Installing or re-installing Visual Studio with C#/.NET (Xamarin v3.1.1) in Cross Platform Mobile Development is recommended.</p></li>
-<p>You must install a Java Development Kit (JDK) 8 or higher to use Emulator Manager & Certificate Manager which were introduced at Preview 2. Do not install OpenJDK.</p>
+<li>.NET Core 1.0.1 Tools Preview 2 or higher
+<p>Tools Preview is needed to set up the .NET development environment. For more information, see <a href="https://www.microsoft.com/net/core#windows" target="_blank">https://www.microsoft.com/net/core#windows</a>.</p></li>
-<p>Download the JDK from the <a class="ext" href="http://www.oracle.com/technetwork/java/javase/downloads/index.html" target="_blank">official Oracle Web site</a>. Select the appropriate platform for your hardware architecture and Windows® version. Then, run the downloaded execution file and follow the displayed instructions.</p>
+<li>Java Development Kit (JDK) 8 or higher
+<p>JDK is needed to use the Emulator Manager and Certificate Manager. Do not install OpenJDK.</p>
+<p>Download the JDK from the <a href="http://www.oracle.com/technetwork/java/javase/downloads/index.html" target="_blank">official Oracle Web site</a>. Select the appropriate platform for your hardware architecture and Windows® version. Run the downloaded executable file and follow the displayed instructions.</p></li>
+</ul>
-<h3 align="left">Emulator Prerequisites</h3>
+<h3>Emulator Requirements</h3>
-<p
align="left">Tizen emulator for Visual Studio requires an equivalent environment with an emulator in the Tizen Studio. To check the hardware and software requirements of the Tizen emulator, see <a href="../../../org.tizen.studio/html/download/prerequisites.htm#emulator">Emulator Requirements</a>.</p>
+<p
>The Tizen emulator for Visual Studio has the same requirements as the emulator in the Tizen Studio. To check the detailed hardware and software requirements for the Tizen emulator, see <a href="../../../org.tizen.studio/html/download/prerequisites.htm#emulator">Emulator Requirements</a>.</p>
<ul>
- <li align="left">Emulator requires 64-bit host PC and 64-bit Windows only.</li>
- <li
align="left">Intel HAXM environment is required for accelerating the Tizen emulator. Intel HAXM is started automatically when you try to install Visual Studio Tools for Tizen. For more information, see <a href="../../../org.tizen.studio/html/download/hardware_accelerated_execution_manager.htm">Hardware Accelerated Execution Manager</a>.</li>
- <li>Make sure <strong>Hyper-V</strong> should be disabled (in Windows® 8 or later):
+ <li>The emulator requires a 64-bit computer running a 64-bit Windows® version.</li>
+ <li
>Intel® Hardware Acceleration Execution Manager (Intel® HAXM) speeds up the Tizen emulation on Intel-VT-enabled systems. Intel® HAXM is installed automatically as part of Visual Studio Tools for Tizen. For more information, see <a href="../../../org.tizen.studio/html/download/hardware_accelerated_execution_manager.htm">Hardware Accelerated Execution Manager</a>.</li>
+ <li>Make sure <strong>Hyper-V</strong> is disabled (in Windows® 8 or higher):
<ol>
- <li align="left" value="1">Run <strong>Programs and Features</strong> in the <strong>Start</strong> menu.
- <p align="center"><img alt="Programs and Features" height="401" src="../images/cs_prerequiste01.png" width="250" /></p>
+ <li>Run <strong>Programs and Features</strong> in the <strong>Start</strong> menu.
+ <p align="center"><img alt="Programs and Features" src="../images/vs_install_programs_features.png" /></p>
</li>
- <li align="left" value="2">Select <strong>Turn Windows features on or off</strong>.</li>
- <li align="left" value="3">Disable <strong>Hyper-V</strong>.
- <p align="center"><img alt="Disaböe Hyper-V" height="295" src="../images/cs_prerequiste02.png" width="331" /></p>
+ <li>Click <strong>Turn Windows features on or off</strong>.</li>
+ <li>Disable <strong>Hyper-V</strong> and click <strong>OK</strong>.
+ <p align="center"><img alt="Disable Hyper-V" src="../images/vs_install_disable_hyperv.png" /></p>
</li>
- <li>Reboot the host PC</li>
+ <li>Reboot the computer.</li>
</ol>
</li>
</ul>
-<p> </p>
-
-<h2>Visual Studio Tools for Tizen Preview Installation</h2>
-
-<p>The following steps are needed in installing Visual Studio Tools for Tizen.</p>
-
-<h3 align="left">1 InstallShield</h3>
-
-<p>The InstallShield wizard sets the basic environment for the Visual Studio extension installer and Tizen Emulator installer. The Tizen C# development environment is organized step by step with a few clicks.</p>
-
-<p align="center"><strong>Figure: Installing Visual Studio Tools for Tizen with InstallShield</strong></p>
-
-<p align="center"><img alt="" height="381" src="../images/cs_install01.png" width="500" /></p>
-
-<p>Since the license contains important legal notifications for using Visual Studio Tools for Tizen, read it line by line, and check the <strong>I accept the terms in the license agreement</strong> check box only when you agree with the license statement.</p>
-
-<p align="center"><strong>Figure: Visual Studio Tools for Tizen License Agreement</strong></p>
-
-<p align="center"><img alt="" height="381" src="../images/cs_install02.png" width="500" /></p>
-
-<h3>2 VSIX Installation</h3>
-
-<p>After the Install Shield process, the VSIX installer for Tizen MI-based Debugger and Visual Studio Tools for Tizen are launched. These installers add the Tizen application development extensions to Visual Studio.</p>
-
-<p align="center"><strong>Figure: MI-based Debugger installer</strong></p>
-
-<p align="center"><img alt="" height="331" src="../images/cs_install03.png" width="436" /></p>
-
-<p align="center"><strong>Figure: VISIX installer</strong></p>
-
-<p align="center"><img alt="" height="331" src="../images/cs_install04.png" width="436" /></p>
-
-<h3>3 Intel HAXM Installation</h3>
-
-<p>After the VSIX installation process, the Intel HAXM installer is launched. Intel HAXM is needed to accelerate the Tizen Emulator.</p>
-
-<p align="center"><strong>Figure: Intel HAXM installer</strong></p>
-
-<p align="center"><img alt="Start installation" height="400" src="../images/hardware_start_instal.png" width="495" /></p>
-
-<p>The memory limitation for the Tizen Emulator can be managed manually. The default value is recommended, but you can set a suitable memory limitation for your development environment.</p>
-
-<p align="center"><strong>Figure: Memory management in Intel HAXM</strong></p>
-
-<p align="center"><img alt="Adjust RAM" height="387" src="../images/hardware_ram.png" width="495" /></p>
+<h2 id="installing">Installing Visual Studio Tools for Tizen Preview</h2>
+To install the Tizen tools and Visual Studio extensions needed for the Tizen C# development environment:
+<ol>
+<li>Launch the Visual Studio Tools for Tizen Preview installer.</li>
+<li>Install the Tizen tools:
+ <ol type="a">
+ <li>To begin the installation, click <strong>Next</strong>.
+ <p align="center"><img alt="Visual Studio Tools for Tizen Preview installer" src="../images/vs_install_installshield.png" /></p></li>
+ <li>Accept the software license.
+ <p>The license contains important legal notices for using Visual Studio Tools for Tizen. Read it in full, click the <strong>I accept the terms in the license agreement</strong> option only when you agree with the license statement, and click <strong>Next</strong>.</p>
+ <p align="center"><img alt="License agreement" src="../images/vs_install_license_agreement.png" /></p></li>
+ <li>Read the list of items included in the installation and click <strong>Next</strong>.
+ <p align="center"><img alt="Installation readme" src="../images/vs_install_readme.png" /></p></li>
+ <li>Optionally, enter your user name and organization, and click <strong>Next</strong>.
+ <p align="center"><img alt="Enter user name" src="../images/vs_install_username.png" /></p></li>
+ <li>Review the installation settings and click <strong>Install</strong>.
+ <p align="center"><img alt="Confirm settings" src="../images/vs_install_confirm_settings.png" /></p></li>
+ <li>When the Tizen tool installation is complete, click <strong>Finish</strong>.
+ <p align="center"><img alt="InstallShield finished" src="../images/vs_install_installshield_finish.png" /></p></li>
+ </ol></li>
+<li>Install the Tizen MI-based Debugger extension.
+ <p>After the Tizen tool installation is complete, the Tizen MI-based Debugger installer launches automatically.</p>
+ <ol type="a">
+ <li>Select the Visual Studio version on which to install the extension, and click <strong>Install</strong>.
+ <p align="center"><img alt="MI-based Debugger installer" src="../images/vs_install_debugger.png" /></p></li>
+ <li>When the installation is complete, click <strong>Close</strong>.</li>
+ </ol></li>
+<li>Install the Visual Studio Tools for Tizen extension.
+ <p>After the Tizen MI-based Debugger installation is complete, the Visual Studio Tools for Tizen installer launches automatically.</p>
+ <ol type="a">
+ <li>Select the Visual Studio version on which to install the extension, and click <strong>Install</strong>.
+ <p align="center"><img alt="Visual Studio Tools for Tizen installer" src="../images/vs_install_vstools.png" /></p></li>
+ <li>When the installation is complete, click <strong>Close</strong>.</li>
+ </ol></li>
+</ol>
-<h3 id="ToolsRelease-Checkinginstallation">4 Installation Checks</h3>
+<h3>Verifying the Installation</h3>
-<p>To check that the installation has been successful:</p>
+<p>To make sure that the installation has been successful:</p>
<ol>
- <li>Run Visual Studio 2015.</li>
- <li>Go to <strong>Tools > Extensions and Update</strong>. If you find the <strong>Visual Studio Tools for Tizen</strong> and <strong>Tizen MI-based Debugger</strong> items installed, everything is OK.
- <p align="center"><img src="../images/cs_install05.png" /></p>
-
- <p align="center"><img src="../images/cs_install06.png" /></p>
+ <li>Run Visual Studio.</li>
+ <li>In the Visual Studio menu, go to <strong>Tools > Extensions and Updates</strong>.
+ <p>In the <strong>Installed > Tools</strong> panel, make sure that <strong>Tizen MI-based Debugger</strong> and <strong>Visual Studio Tools for Tizen</strong> are installed.</p>
+ <p align="center"><img alt="Visual Studio extensions for Tizen" src="../images/vs_install_extensions_check.png" /></p>
</li>
- <li>Go to <strong>File > New > Project</strong> to find the <strong>Tizen</strong> entry with some Tizen-specific templates in the <strong>Visual C#</strong> tree.
- <p align="center"><img align="middle" alt="" height="284" src="../images/cs_install07_1.png" width="500" /></p>
+ <li>In the Visual Studio menu, go to <strong>File > New > Project</strong>.
+ <p>In the <strong>Installed > Templates > Visual C#</strong> menu tree, make sure there is a <strong>Tizen</strong> entry with Tizen-specific templates.</p>
+ <p align="center"><img alt="Tizen-specific project templates" src="../images/vs_install_new_project.png" /></p>
</li>
</ol>
-<h2 id="ToolsRelease-Whatisinstalled">Installed Components</h2>
-
-<p>The following components are installed:</p>
+<p>After a successful installation, the following components can be found on your computer:</p>
<ul>
- <li>In <code class="prettyprint"><span class="tag"><Program</span><span class="pln"> </span><span class="atn">Files</span><span class="tag">></span><span class="pln">/Tizen/Tools</span></code>:
+ <li>In <code><Program Files>/Tizen/Tools</code>:
<ul>
- <li><code class="prettyprint"><span class="typ">Tizen</span><span class="pun">.</span><span class="typ">Extension</span><span class="pun">.</span><span class="pln">vsix</span></code>: Visual Studio extension with project templates and debugging</li>
- <li><code class="prettyprint"><span class="typ">Tizen</span><span class="pun">.</span><span class="typ">MIDebugPackage</span><span class="pun">.</span><span class="pln">vsix</span></code>: Visual Studio extension with MIEngine fork for Tizen</li>
+ <li><code>Tizen.Extension.vsix</code>: Visual Studio extension with project templates and debugging</li>
+ <li><code>Tizen.MIDebugPackage.vsix</code>: Visual Studio extension with MIEngine fork for Tizen</li>
</ul>
</li>
- <li>In <code class="prettyprint"><span class="tag"><Program</span><span class="pln"> </span><span class="atn">Files</span><span class="tag">></span><span class="pln">/Tizen/SDK/platforms</span></code>: Mobile and TV Emulator images</li>
- <li>​In <code class="prettyprint"><span class="tag"><Program</span><span class="pln"> </span><span class="atn">Files</span><span class="tag">></span><span class="pln">/Tizen/SDK/tools</span></code>:
+ <li>In <code><Program Files>/Tizen/SDK/platforms</code>: Mobile and TV Emulator images</li>
+ <li>​In <code><Program Files>/Tizen/SDK/tools</code>:
<ul>
- <li><code class="prettyprint"><span class="pln">sdb</span><span class="pun">.</span><span class="pln">exe</span></code>: For connection with the emulator and target devices</li>
- <li>In <code class="prettyprint"><span class="pln">certificate</span><span class="pun">-</span><span class="pln">generator</span></code>: Storage for Tizen certificates</li>
- <li>In <code class="prettyprint"><span class="pln">certificate</span><span class="pun">-</span><span class="pln">manager</span></code>: Tool for managing Tizen certificates</li>
- <li>In <code class="prettyprint"><span class="pln">device</span><span class="pun">-</span><span class="pln">manager</span></code>: Tool for managing devices including Tizen emulators and devices</li>
- <li>In <code class="prettyprint"><span class="pln">emualtor</span></code>: Tool for emulator manager</li>
- <li>In <code class="prettyprint"><span class="pln">on</span><span class="pun">-</span><span class="pln">demand</span></code>: lldb engines for on-demand debugger</li>
+ <li><code>sdb.exe</code>: For connecting to emulators and target devices</li>
+ <li>In <code>certificate-generator</code>: Storage for Tizen certificates</li>
+ <li>In <code>certificate-manager</code>: Tool for managing Tizen certificates</li>
+ <li>In <code>device-manager</code>: Tool for managing Tizen emulators and devices</li>
+ <li>In <code>emulator</code>: Tool for emulator manager</li>
+ <li>In <code>on-demand</code>: lldb engines for on-demand debugger</li>
</ul>
</li>
- <li><code class="prettyprint"><span class="typ">In</span><span class="pun"><</span><span class="typ">Program</span><span class="pln"> </span><span class="typ">Files</span><span class="pun">></span><span class="str">/MSBuild/</span><span class="typ">Tizen</span></code>:
+ <li>In <code><Program Files>/MSBuild/Tizen</code>:
<ul>
- <li><code class="prettyprint"><span class="typ">Tizen</span><span class="pun">.</span><span class="typ">CSharp</span><span class="pun">.</span><span class="pln">targets</span></code>: Used for building</li>
- <li><code class="prettyprint"><span class="pln">bin</span><span class="pun">/</span><span class="pln">author_test</span><span class="pun">.</span><span class="pln">p12</span></code>: Used as a test author certificate file
+ <li><code>Tizen.CSharp.targets</code>: Used for building</li>
+ <li><code>bin/author_test.p12</code>: Used as a test author certificate file
<ul>
- <li>The password is <strong><span>author_test</span></strong> without double quotation marks.</li>
+ <li>The password is <strong>author_test</strong>.</li>
</ul>
</li>
- <li><code class="prettyprint"><span class="pun">​</span><span class="pln">bin</span><span class="pun">/</span><span class="pln">tizen</span><span class="pun">-</span><span class="pln">distributor</span><span class="pun">-</span><span class="pln">signer</span><span class="pun">.</span><span class="pln">p12</span></code>: Used as a test distributor certificate file</li>
- <li><code class="prettyprint"><span class="pln">bin</span><span class="pun">/</span><span class="pln">libxmlsec</span><span class="pun">-</span><span class="lit">1.2</span><span class="pun">.</span><span class="lit">18</span></code>: Used for signing</li>
+ <li><code>bin/tizen-distributor-signer.p12</code>: Used as a test distributor certificate file</li>
+ <li><code>bin/libxmlsec-1.2.18</code>: Used for signing</li>
</ul>
</li>
</ul>
+<h2 id="configure_haxm">Configuring Intel® HAXM</h2>
+Intel® HAXM is installed automatically as part of Visual Studio Tools for Tizen. The installer also functions as a configuration tool for Intel® HAXM. You can change the amount of RAM allocated to Intel® HAXM. The default value is recommended, but you can set a memory limit suitable for your development environment.
+<p>To change the amount of RAM allocated to Intel® HAXM:</p>
+ <ol>
+ <li>Launch the Intel® HAXM installer from <code><Program Files>/Tizen/SDK/tools/emulator/etc/IntelHaxm.exe</code> and click <strong>Next</strong>.
+ <p align="center"><img alt="Intel HAXM installer" src="../images/vs_install_haxm.png" /></p></li>
+ <li>Click <strong>Change</strong>.
+ <p align="center"><img alt="Change installation" src="../images/vs_install_haxm_installation.png" /></p></li>
+ <li>Adjust the memory limit for Intel® HAXM and click <strong>Next</strong>.
+ <p align="center"><img alt="Memory limit for Intel HAXM" src="../images/vs_install_haxm_ram.png" /></p>
+<div class="note">
+ <strong>Note</strong>
+ If you change the Intel® HAXM memory settings, you must restart both Intel® HAXM and the emulator for the change to take effect. Emulators currently running continue to use the previous memory setting.
+</div></li>
+ <li>Confirm your Intel® HAXM memory allocation settings and click <strong>Change</strong>.
+ <p align="center"><img alt="Confirm HAXM change" src="../images/vs_install_haxm_confirm.png" /></p></li>
+ <li>When the Intel® HAXM configuration is complete, click <strong>Finish</strong>.
+ <p align="center"><img alt="HAXM configuration finished" src="../images/vs_install_haxm_finished.png" /></p></li>
+ </ol>
<script type="text/javascript" src="../scripts/jquery.zclip.min.js"></script>
<script type="text/javascript" src="../scripts/showhide.js"></script>
<script type="text/javascript" src="../scripts/common.js" charset="utf-8"></script>
<script type="text/javascript" src="../scripts/core.js" charset="utf-8"></script>
<script type="text/javascript" src="../scripts/search.js" charset="utf-8"></script>
- <title>Porting Xamarin.Forms Apps to Tizen using Visual Studio</title>
+ <title>Porting Xamarin.Forms Applications to Tizen using Visual Studio</title>
</head>
<body onload="prettyPrint()" style="overflow: auto;">
<li><a href="#opening">Opening a Xamarin.Forms Sample Application</a></li>
<li><a href="#adding">Adding a Tizen-dependent Project</a></li>
<li><a href="#deploying">Deploying and Running the Application</a></li>
- <li><a href="#demoshots">Sample UI in Various Platforms</a></li>
+ <li><a href="#demoshots">Sample UI on Various Platforms</a></li>
</ul>
</div>
</div>
<div id="container"><div id="contents"><div class="content">
- <h1>Porting Xamarin.Forms Apps to Tizen using Visual Studio</h1>
+ <h1>Porting Xamarin.Forms Applications to Tizen</h1>
<div class="wiki-content" id="main-content">
-<p>As Tizen is embracing .NET and Xamarin.Forms for better development environments, it creates opportunities for cross-platform application developers. To manage cross-platform development, you must be able to port existing Xamarin.Forms applications to the Tizen OS. As shown in the following figure, Tizen is consistent with the .NET architecture and it is easy to adapt Xamarin.Forms applications to Tizen. The following sections use a sample application as an example of how to perform porting.</p>
+<p>As Tizen embraces .NET and Xamarin.Forms for better development environments, it creates opportunities for cross-platform application developers. To manage cross-platform development, you must be able to port existing Xamarin.Forms applications to the Tizen OS. In practice, this means that you can add a Tizen-specific project for an existing cross-platform solution, which already contains projects for, for example, Android, iOS, and Universal Windows Platform (UWP). When developing the Tizen-specific project, you can reuse the shared Xamarin.Forms code from the portable project within the solution.</p>
-<div class="note"><strong>Note</strong> Before porting, make sure that <a href="../getting_started/download.htm">Visual Studio Tools for Tizen</a> is installed on your system.</div>
+<p>As shown in the following figure, Tizen is consistent with the .NET architecture and it is easy to adapt Xamarin.Forms applications to Tizen.</p>
<p align="center"><strong>Figure: Tizen .NET architecture</strong></p>
-<p align="center"><a class="colorbox" href="../images/cs_overview.png"><img alt="Tizen .NET Architecture" height="282" src="../images/cs_overview-707x282.png" width="707" /></a></p>
+<p align="center"><img alt="Tizen .NET architecture" src="../images/cs_overview.png" /></p>
-<p> </p>
+<div class="note"><strong>Note</strong> Before porting, make sure that <a href="../getting_started/getting_started_cover.htm#download">Visual Studio Tools for Tizen</a> is installed on your system.</div>
+
+<p>The following sections describe how to port a Xamarin Forms sample application to Tizen.</p>
</div>
<h2 id="opening">Opening a Xamarin.Forms Sample Application</h2>
-<p><span>You can find various sample applications at <a href="https://developer.xamarin.com/samples/xamarin-forms/all/">Xamarin.Forms Samples</a>. Among them, the <a href="https://developer.xamarin.com/samples/xamarin-forms/UserInterface/Animation/Basic/">Basic Animation</a> application shows the implementation of simple animations, such as rotating, scaling, and fading. The sample consists of a shared project and multiple platform-dependent projects for Android, iOS, and Universal Windows Platform (UWP).</span></p>
+<p>You can find various sample applications at <a href="https://developer.xamarin.com/samples/xamarin-forms/all/" target="blank">Xamarin.Forms Samples</a>. Among them, the <a href="https://developer.xamarin.com/samples/xamarin-forms/UserInterface/Animation/Basic/" target="blank">Basic Animation</a> application shows the implementation of simple animations, such as rotating, scaling, and fading. The sample consists of a shared project and multiple platform-dependent projects for Android, iOS, and Universal Windows Platform (UWP).</p>
-<p><span>To open the sample application:</span></p>
+<p>To open the sample application in Visual Studio:</p>
<ol>
- <li>Download and extract the <a href="https://developer.xamarin.com/samples/xamarin-forms/UserInterface/Animation/Basic/Basic.zip">source code of the Basic Animation sample</a> from the Xamarin sample site.</li>
+ <li>Download and extract the <a href="https://developer.xamarin.com/samples/xamarin-forms/UserInterface/Animation/Basic/Basic.zip" target="blank">source code of the Basic Animation sample</a> from the Xamarin sample site.</li>
<li>Launch Visual Studio.</li>
- <li>In the Visual Studio menu, go to <strong>File > Open > Project/Solution </strong>and select <strong><code>BasicAnimation.sln</code></strong>.
- <p align="center"><img alt="Open Project" height="441" src="../images/openproject.png" width="668" /></p>
+ <li>In the Visual Studio menu, go to <strong>File > Open > Project/Solution </strong>and select <code>BasicAnimation.sln</code> from within the extracted sample.
+ <p align="center"><img alt="Open project" src="../images/xamarin_open_new_project.png" /></p>
</li>
</ol>
-<p> </p>
-
-<p align="center"> </p>
-
<h2 id="adding">Adding a Tizen-dependent Project</h2>
-<p><span>By adding a new project for Tizen and reusing the shared code, you can get the Basic Animation application ready to be built for the Tizen OS. </span></p>
+<p>By reusing the shared code from the sample solution in a new Tizen project, you can build the Basic Animation application for Tizen with minimal coding.</p>
-<p><span>To add a Tizen-dependent project:</span></p>
+<p>To add a Tizen-dependent project to the sample application solution:</p>
<ol>
- <li>
- <p>In the <strong>Solution Explorer</strong>, right-click <strong>Solution 'BasicAnimation'</strong> and select <strong>Add > New Project</strong>.</p>
+ <li>In the <strong>Solution Explorer</strong> view, right-click the solution and select <strong>Add > New Project</strong>.
- <p align="center"><img alt="Add New Project" height="592" src="../images/addnewproject.png" width="654" /></p>
+ <p align="center"><img alt="Add new project" src="../images/xamarin_add_new_project.png" /></p>
</li>
- <li>
- <p>Select <strong><strong><strong>Tizen ></strong></strong></strong><strong><strong><strong> Blank App (Tizen Xamarin.Forms Portable)</strong></strong></strong>, enter a name and location for the Tizen project, and click <strong><strong><strong>OK</strong></strong></strong>.</p>
+ <li>Select <strong>Visual C# > Tizen > Blank App (Tizen Xamarin.Forms Portable)</strong>, enter a name and location for the Tizen project, and click <strong>OK</strong>.
- <p align="center"><img alt="Add New Project" height="538" src="../images/addnewproject2.png" width="844" /></p>
+ <p align="center"><img alt="Name new project" src="../images/xamarin_add_tizen_templates.png" /></p>
</li>
- <li>
- <p>In the Tizen Project Wizard, select the applicable profiles (Common, Mobile, or TV), and click <strong>OK</strong>.</p>
-
- <p align="center"><img alt="Tizen Project Wizard" height="368" src="../images/tizenprojectwizard.png" width="652" /></p>
+ <li>In the Tizen Project Wizard, select the applicable profiles and click <strong>OK</strong>.
- <p>The <strong>Solution Explorer </strong>shows that new profile-specific Tizen projects are added to the existing Xamarin.Forms solution. In this case, since 2 profiles were selected, 2 new projects are added.</p>
+ <p align="center"><img alt="Tizen Project Wizard" src="../images/xamarin_projectwizard_basicanimation.png" /></p>
- <p align="center"><img alt="Tizen Project Added" height="226" src="../images/addedprojects.png" width="430" /></p>
+ <p>The <strong>Solution Explorer</strong> shows that new profile-specific Tizen projects are added to the existing Xamarin.Forms solution. In this case, since 2 profiles were selected, 2 new projects are added.</p>
+ <p align="center"><strong>Figure: Added Tizen projects</strong></p>
+ <p align="center"><img alt="Added Tizen projects" src="../images/xamarin_added_tizen_projects.png" /></p>
</li>
- <li>
- <p>Since the Tizen projects have dependencies with the Xamarin.Forms NuGet package version, you must install the Xamarin.Forms NuGet package that has the same version as Xamarin.Forms.Platform.Tizen. Mismatching the NuGet versions can cause build or packaging problems.<br />
- Right-click <strong>Solution 'BasicAnimation'</strong> and select <strong>Manage NuGet Packages for Solution</strong>.</p>
+ <li>Since the Tizen projects have dependencies with the Xamarin.Forms NuGet package version, you must install the Xamarin.Forms NuGet package that has the same version as Xamarin.Forms.Platform.Tizen. Mismatched NuGet versions can cause build or packaging problems.
+ <ol type="a">
+ <li>Right-click <strong>Solution 'BasicAnimation'</strong> and select <strong>Manage NuGet Packages for Solution</strong>.
- <p align="center"><img alt="Manage NuGet Packages" height="484" src="../images/managenugetpackages.png" width="552" /></p>
+ <p align="center"><img alt="Manage NuGet packages" src="../images/xamarin_manage_nuget.png" /></p>
</li>
- <li>
- <p>In the <strong>Installed </strong>tab, select <strong>Xamarin.Forms</strong>. If there are mismatched versions between the PCL (Portable Class Library) project and the newly added projects, install the latest Xamarin.Forms version.</p>
+ <li>In the <strong>Installed </strong>tab, select <strong>Xamarin.Forms</strong>. If there are mismatched versions between the PCL (Portable Class Library) project and the newly-added projects, install the latest Xamarin.Forms version.
- <p align="center"><img alt="Manage NuGet Packages" height="392" src="../images/managenugetpackages2.png" width="640" /></p>
+ <p align="center"><img alt="Manage NuGet packages" src="../images/xamarin_manage_packages.png" /></p>
</li>
- <li>
- <p>To build the solution, in the main menu of Visual Studio, select <strong>Build > Build Solution</strong>.</p>
+ </ol>
+ </li>
+ <li>To build the solution, in the main menu of Visual Studio, select <strong>Build > Build Solution</strong>.
- <p>Alternatively, you can right-click the solution in the <strong>Solution Explorer </strong>and select <strong>Build Solution</strong>.</p>
+ <p>Alternatively, you can right-click the solution in the <strong>Solution Explorer</strong> and select <strong>Build Solution</strong>.</p>
- <p align="center"><img alt="Build Solution" height="408" src="../images/buildsolution.png" width="678" /></p>
+ <p align="center"><img alt="Build solution" src="../images/xamarin_build_solution.png" /></p>
</li>
- <li>
- <p>Copy the necessary image file for the animation (<strong><code>Droid/Resources/drawable/monkey.png</code></strong>) to the <strong><code>BasicAnimationTizen.TizenMobile/res</code></strong> Tizen resource directory.</p>
+ <li>Copy the necessary image file for the animation from the Android project (<code>Droid/Resources/drawable/monkey.png</code>) to the Tizen projects (<code>BasicAnimationTizen.TizenMobile/res</code> and <code>BasicAnimationTizen.TizenTV/res</code>).
</li>
</ol>
<h2 id="deploying">Deploying and Running the Application</h2>
-<p><span>To run the application, you must deploy it first to the target: either a device or an emulator. Deploying means transferring the package file (</span><code>.tpk</code><span>) to the target and invoking the Tizen package manager to install it. In this example, the Tizen emulator in Visual Studio is used as a target.</span></p>
-
-<ol>
- <li>
- <p>In the Visual Studio menu, select <strong>Tools > Tizen > Tizen Emulator Manager</strong>.</p>
+<p>To run the application, you must first deploy it to the target: either a device or an emulator. Deploying means transferring the package file (<code>.tpk</code>) to the target and invoking the Tizen package manager to install it.</p>
- <p>Alternatively, you can launch the Tizen emulator using the Visual Studio toolbars as shown in the following figure.</p>
+<p>To deploy and run the application on the emulator:</p>
- <p align="center"><img alt="Launch Tizen Emulator" height="113" src="../images/launchtizenemul.png" width="786" /></p>
+<ol>
+ <li>In the Visual Studio menu, select <strong>Tools > Tizen > Tizen Emulator Manager</strong>.
+ <p>Alternatively, you can launch the Tizen emulator using the Visual Studio toolbar as shown in the following figure:</p>
+ <p align="center"><img alt="Launch Tizen Emulator" src="../images/cs_launch_tizen_emu.png" /></p>
</li>
- <li>
- <p>In the Tizen Emulator Manager, create an emulator by clicking <strong>Create</strong>. For more information on creating emulator instances, see <a href="../tools/emulator_manager.htm">Emulator Manager</a>.</p>
-
- <p align="center"><img alt="Tizen Emulator Manager" height="589" src="../images/tizenemulmanager.png" width="602" /></p>
+ <li>In the Emulator Manager, select an emulator instance from the list and click <strong>Launch</strong>.
+ <p>If no applicable emulator instance exists, <a href="../tools/emulator_manager.htm#create">create one</a>.</p>
+ <p align="center"><img alt="Tizen Emulator Manager" src="../images/vs_emulator_manager.png" /></p>
</li>
- <li>
- <p>Once you launch an emulator instance, you can run the application by clicking the emulator instance in the Visual Studio toolbar. The following figure shows a screenshot of the Xamarin.Forms sample app running on the Tizen mobile emulator.</p>
-
- <p align="center"><img alt="Tizen Emulator Manager" height="109" src="../images/deploy.png" width="726" /></p>
-
- <p align="center"><img alt="Demo1" height="511" src="../images/demo1.png" width="384" /></p>
+ <li>Once you launch an emulator instance, you can run the application by clicking the emulator instance in the Visual Studio toolbar.
+ <p align="center"><img alt="Tizen Emulator Manager" src="../images/vs_emulator_launch.png" /></p>
+ <p>The following figure shows the Basic Animation Xamarin.Forms sample application running on the Tizen mobile emulator.</p>
+ <p align="center"><strong>Figure: Basic Animation sample application</strong></p>
+ <p align="center"><img alt="Basic Animation sample application" src="../images/xamarin_basicanimation_tizen.png" /></p>
</li>
</ol>
-<p> </p>
-
-<h2 id="demoshots">Sample UI in Various Platforms</h2>
-
-<p><span>The following screenshots display the UI of the Basic Animation sample on different mobile platforms and the Tizen TV emulator. Since Tizen .NET supports the TV profile, you can port the Xamarin applications to the Tizen TV as well as Tizen mobile profile in the Tizen Project Wizard.</span></p>
-
-<p align="center"><strong>Figure: Basic Animation sample in different targets and platforms</strong></p>
-
-<p align="center"><img alt="Demo Screeshot" height="389" src="../images/demo1.jpg" width="780" /></p>
-
-<p align="center"><img alt="Tizen TV Demo Screeshot1" height="363" src="../images/tizentvdemo1.png" width="740" /></p>
+<h2 id="demoshots">Sample UI on Various Platforms</h2>
-<p align="center"><img alt="Tizen TV Demo Screeshot2" height="363" src="../images/tizentvdemo2.png" width="740" /></p>
+<p>The following screenshots display the UI of the Basic Animation sample on different mobile platforms and the Tizen TV emulator. Since Tizen .NET supports the TV profile, you can port the Xamarin applications to the Tizen TV as well as the Tizen mobile profile in the Tizen Project Wizard.</p>
-<p> </p>
+<p align="center"><strong>Figure: Basic Animation sample on different platforms</strong></p>
+<p align="center"><img alt="Basic Animation sample on different mobile platforms" src="../images/xamarin_basicanimation_mobile.png" /></p>
+<p align="center"><img alt="Basic Animation sample on Tizen TV" src="../images/xamarin_basicanimation_tizentv.png" /></p>
<script type="text/javascript" src="../scripts/jquery.zclip.min.js"></script>
</div>
<ul id="navigation">
- <li><a href="cover_page.htm" target="content">Introduction</a>
+ <li><a href="cover_page.htm" target="content">Overview</a>
<ul>
- <li><a href="cover_page.htm" target="content">What's New</a></li>
- <li><a href="introduction/overview.htm" target="content">Overview</a></li>
+ <li><a href="introduction/whats_new.htm" target="content">What's New</a></li>
<li><a href="introduction/roadmap.htm" target="content">Roadmap</a></li>
</ul>
</li>
- <li><a href="getting_started/download.htm" target="content">Getting Started</a>
+ <li><a href="getting_started/getting_started_cover.htm" target="content">Getting Started</a>
<ul>
- <li><a href="getting_started/download.htm" target="content">Download</a></li>
<li><a href="getting_started/installing.htm" target="content">Installing Visual Studio Tools for Tizen</a></li>
<li><a href="getting_started/first_app.htm" target="content">Creating Your First Tizen .NET Application</a></li>
- <li><a href="getting_started/porting_xamarinforms.htm" target="content">Porting Xamarin.Forms Apps to Tizen using Visual Studio</a></li>
+ <li><a href="getting_started/cross_platform_project.htm" target="content">Creating Tizen Projects as Cross-platform Solutions</a></li>
+ <li><a href="getting_started/porting_xamarinforms.htm" target="content">Porting Xamarin.Forms Applications to Tizen</a></li>
</ul>
</li>
<li><a href="tools/tools_overview.htm" target="content">Visual Studio Tools for Tizen</a>
<ul>
- <li><a href="tools/tools_overview.htm" target="content">Overview</a></li>
<li><a href="tools/project_wizard.htm" target="content">Project Wizard</a></li>
<li><a href="tools/certificate_manager.htm" target="content">Certificate Manager</a></li>
<li><a href="tools/manifest_editor.htm" target="content">Tizen Manifest Editor</a>
</li>
<li><a href="tools/emulator_manager.htm" target="content">Emulator Manager</a></li>
<li><a href="tools/emulator_control_panel.htm" target="content">Emulator Control Panel</a></li>
+ <li><a href="tools/api-privilege_checker.htm" target="content">API and Privilege Checker</a></li>
<li><a href="tools/device_manager.htm" target="content">Device Manager</a></li>
<li><a href="tools/log_viewer.htm" target="content">Log Viewer</a></li>
- <li><a href="tools/api-privilege_checker.htm" target="content">API and Privilege Checker</a></li>
</ul>
</li>
</ul>
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
-
-<head>
- <meta http-equiv="content-type" content="text/html; charset=utf-8" />
- <meta http-equiv="X-UA-Compatible" content="IE=9" />
- <link rel="stylesheet" type="text/css" href="../css/styles.css" />
- <link rel="stylesheet" type="text/css" href="../css/snippet.css" />
- <script type="text/javascript" src="../scripts/snippet.js"></script>
- <script type="text/javascript" src="../scripts/jquery.util.js" charset="utf-8"></script>
- <script type="text/javascript" src="../scripts/common.js" charset="utf-8"></script>
- <script type="text/javascript" src="../scripts/core.js" charset="utf-8"></script>
- <script type="text/javascript" src="../scripts/search.js" charset="utf-8"></script>
- <title>Overview</title>
-</head>
-
-<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
-
-<div id="toc-navigation">
-</div>
-
-<div id="container"><div id="contents"><div class="content">
-
- <h1>Overview</h1>
-
-<p align="left">Tizen .NET is an exciting new way to develop applications for the Tizen operating system, running on 50 million Samsung devices, including TVs, wearables, mobile, and many other IoT devices around the world. The existing Tizen frameworks are either C-based with no advantages of a managed runtime, or HTML5-based with fewer features and lower performance than the C-based solution. With Tizen .NET, you can use the C# programming language and the Common Language Infrastructure standards and benefit from a managed runtime for faster application development, and efficient, secure code execution.</p>
-
-<h2 align="left"><span>Managed Runtime Advantages</span></h2>
-
-<p>A managed runtime offers the following advantages for your application development:</p>
-
-<ul>
- <li><strong><span>Faster time to develop</span></strong><br />
- Application development is accelerated since the managed runtime already handles many functions that otherwise have to be coded in the application (the Tizen Native API and Tizen Web API already provide this type of benefit).<br />
- </li>
- <li><strong><span>Safer code</span></strong><br />
- Managed runtimes can handle, for example, bound checking, type safety, garbage collection, memory protection services, and objects being invoked directly (the Tizen Web API already provides some of these benefits, but not type safety, as JavaScript is not a strongly typed language).<br />
- </li>
- <li><strong><span>Lower deployment costs</span></strong><br />
- Component-based architecture makes it easier and faster to deploy applications in an enterprise environment characterized by multiple platforms, devices, and legacy systems.<br />
- </li>
- <li><strong><span>Better quality software</span></strong><br />
- Managed runtimes free you to focus on the business logic and code specific to the application while reducing the number of coding errors.<br />
- </li>
- <li><strong><span>Cross-platform support</span></strong><br />
- The managed code is portable; Tizen .NET applications can have large portions of their logic applied to other systems supported by the .NET Core and Xamarin.Forms portions of the runtime.</li>
-</ul>
-
-<h2 id="Tizen.NETFeatures">Tizen .NET Features and Components</h2>
-
-<p>Tizen .NET consists of the following main components:</p>
-
-<ul>
- <li>
- <p><strong>.NET Core</strong></p>
-
- <p>.NET Core is a general purpose development platform maintained by Microsoft and the .NET community on <a class="external-link" href="https://github.com/dotnet/core" rel="nofollow" target="_blank">GitHub</a>. It is cross-platform, supporting Windows®, Mac OS® X, and Linux, and can be used in device, cloud, and embedded/IoT scenarios.</p>
-
- <p>.NET Core is composed of the following parts:</p>
-
- <ul>
- <li>
- <p>A <a href="https://github.com/dotnet/coreclr" target="_blank">.NET runtime</a>, which provides a type system, assembly loading, a garbage collector, native interop and other basic services.</p>
- </li>
- <li>
- <p>A set of <a href="https://github.com/dotnet/corefx" target="_blank">framework libraries</a>, which provide primitive data types, app composition types and fundamental utilities.</p>
- </li>
- <li>
- <p>A <a href="https://github.com/dotnet/cli" target="_blank">set of SDK tools</a> and <a href="https://github.com/dotnet/roslyn" target="_blank">language compilers</a> that enable the base developer experience, available in the <a href="https://docs.microsoft.com/en-us/dotnet/articles/core/sdk" target="_blank">.NET Core SDK</a>.</p>
- </li>
- <li>
- <p>The 'dotnet' app host, which is used to launch .NET Core apps. It selects the runtime and hosts the runtime, provides an assembly loading policy and launches the app. The same host is also used to launch SDK tools in much the same way.</p>
- </li>
- </ul>
- </li>
- <li>
- <p><strong>Xamarin.Forms as a UI framework</strong></p>
-
- <p>Xamarin.Forms is a cross-platform UI toolkit that allows you to efficiently create native user interface layouts that can be shared across iOS, Android, Windows Phone, and Universal Windows Platform applications.</p>
- </li>
- <li>
- <p><strong>Tizen Platform-Specific API</strong></p>
-
- <p>Tizen .NET supports C# APIs, which expose the Tizen-specific features:</p>
-
- <ul>
- <li><span>Tizen.Account: Provides CRUD (Create, Read, Update, Delete) account management functionality and </span><span>the OAuth Core RFC 6749 protocol.</span></li>
- <li>Tizen.Applications: Provides the Tizen application framework, including application state change events, inter-application messaging, and notification services.</li>
- <li>Tizen.Common: <span>Provides predefined color name</span><span>s</span><span>.</span></li>
- <li>Tizen.Content: Provides content management services, such as file and media downloads, storing and indexing audio and video content, and associating content types with helper applications.</li>
- <li>Tizen.Location: Manages geographical location services and geofencing.</li>
- <li>Tizen.<span>Messaging: Provides functions to receive push notifications.</span></li>
- <li>Tizen.Multimedia: Interacts with media services, including audio playback, recording, and device policy.</li>
- <li>Tizen.Network: Provides APIs to control connectivity devices, as well as providing various network information.</li>
- <li>Tizen.Security: Provides access to secure storage for passwords, keys, certificates, and other sensitive data.</li>
- <li><span>Tizen.Sensor: Provides sensor types and sensor information.</span></li>
- <li>Tizen.System: Provides device-specific services, including status, system information and settings, feedback, and sensor control and access.</li>
- <li><span>Tizen.Telephony: Provides call, modem, network, and SIM information.</span></li>
- <li>Tzien.Uix: <span>Provides functions to recognize the speech and to synthesize voice from text and playing synthesized sound data.</span></li>
- <li>Tizen.Log: <span>Provides methods to print log messages to </span><span>Tizen</span><span> logging system.</span></li>
- <li>Tizen.Tracer: <span>Provides functions for writing trace message to the system trace buffer.</span></li>
- </ul>
- </li>
-</ul>
-
-<p>Tizen .NET enables you to build .NET applications with Xamarin.Forms and the Tizen .NET framework. Xamarin.Forms allows you to easily create a user interface, and the Tizen platform API provides numerous interfaces to much of the hardware that is found in modern TVs, and mobile, wearable, and IoT devices.</p>
-
-<p align="center"><strong>Figure: Tizen .NET Architecture</strong></p>
-
-<p align="center"><img alt="Tizen .NET Architecture" height="282" src="../images/cs_overview.png" width="707" /></p>
-
-<h2 id="VisualStudioToolsforTizen">Visual Studio Tools for Tizen</h2>
-
-<p>Visual Studio Tools for Tizen provides the following tools:</p>
-
-<ul>
- <li><a href="../tools/project_wizard.htm">Project Wizard</a><br />
- The Project Wizard is a tool that is used to create a Tizen .Net application project.</li>
- <li><a href="../tools/certificate_manager.htm">Certificate Manager</a><br />
- The certificates can be created, edited, removed, and set as active in the Certificate Manager. The active certificates are used when packaging your application.</li>
- <li><span><a href="../tools/manifest_editor.htm">Tizen Manifest Editor</a></span><br />
- The Tizen Manifest Editor is a tool that is used to edit Tizen manifest file, called <code class="prettyprint"><span class="pln"><span class="pln">tizen</span></span><span class="pun"><span class="pun">-</span></span><span class="pln"><span class="pln">manifest</span></span><span class="pun"><span class="pun">.</span></span><span class="pln"><span class="pln">xml</span></span></code>, which is used to describe the application information</li>
- <li><a href="../tools/emulator_manager.htm"><span>Emulator Manager</span></a><br />
- The Emulator Manager provides emulators to run your application in a virtual environment.</li>
- <li><a href="../tools/emulator_control_panel.htm"><span>Emulator Control Panel</span></a><br />
- The Emulator Control Panel allows you to run the application in the emulator, and test a variety of user scenarios, such as network access, audio input and out, and text messages. </li>
- <li><a href="../tools/device_manager.htm">Device Manager</a><br />
- The Tizen Device Manager is a tool that is used to manage connected Tizen devices or emulators, which is used to browse, push and pull files from them. </li>
- <li><a href="../tools/log_viewer.htm">Log Viewer</a><br />
- The Tizen Log Viewer is a tool that is used to see logs from connected Tizen devices or emulaotors. </li>
- <li><a href="../tools/api-privilege_checker.htm">API and Privilege Checker</a><br />
- The API and Privilege Checker is a tool that detects API and Privilege violations in Tizen .NET Applications.</li>
-</ul>
-
-
-<script type="text/javascript" src="../scripts/jquery.zclip.min.js"></script>
-<script type="text/javascript" src="../scripts/showhide.js"></script>
-
-</div></div></div>
-
-<a class="top sms" href="#"><img src="../images/btn_top.gif" alt="Go to top" /></a>
-
-<div id="footer">
-<p class="footer">Except as noted, this content - excluding the Code Examples - is licensed under <a href="http://creativecommons.org/licenses/by/3.0/legalcode" target="_blank">Creative Commons Attribution 3.0</a> and all of the Code Examples contained herein are licensed under <a href="https://www.tizen.org/bsd-3-clause-license" target="_blank">BSD-3-Clause</a>.<br/>For details, see the <a href="https://www.tizen.org/content-license" target="_blank">Content License</a>.</p>
-</div>
-
-<script type="text/javascript">
-var _gaq = _gaq || [];
-_gaq.push(['_setAccount', 'UA-25976949-1']);
-_gaq.push(['_trackPageview']);
-(function() {
-var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
-ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
-var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
-})();
-</script>
-
-</body>
-
-</html>
<div id="toc-navigation">
</div>
<div id="container"><div id="contents"><div class="content">
- <h1>Roadmap</h1>
-<p><span>The first public milestone of Tizen .NET will be released in June 2017 as a part of </span><span>Tizen 4.0.</span> Until then, several previews will be released on every two or three months so that developers can begin making themselves familar with Tizen .NET and give early feedback.</p>
+ <h1>Roadmap</h1>
-<p>The release plan is as follows.</p>
+<p>Preview or beta versions of Tizen .NET are released every 2-3 months, allowing you to familiarize yourself with Tizen .NET and give early feedback.</p>
-<p><img alt="" height="1394" src="../images/release_plan_preview4_m1.png" width="1058" /></p>
+<p align="center"><strong>Tizen .NET release roadmap</strong></p>
+<p align="center"><img src="../images/roadmap.png" alt="Tizen .NET release roadmap"/></p>
<script type="text/javascript" src="../scripts/jquery.zclip.min.js"></script>
<script type="text/javascript" src="../scripts/showhide.js"></script>
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+
+<head>
+ <meta http-equiv="content-type" content="text/html; charset=utf-8" />
+ <meta http-equiv="X-UA-Compatible" content="IE=9" />
+ <link rel="stylesheet" type="text/css" href="../css/styles.css" />
+ <link rel="stylesheet" type="text/css" href="../css/snippet.css" />
+ <script type="text/javascript" src="../scripts/snippet.js"></script>
+ <script type="text/javascript" src="../scripts/jquery.util.js" charset="utf-8"></script>
+ <script type="text/javascript" src="../scripts/common.js" charset="utf-8"></script>
+ <script type="text/javascript" src="../scripts/core.js" charset="utf-8"></script>
+ <script type="text/javascript" src="../scripts/search.js" charset="utf-8"></script>
+ <title>What's New</title>
+</head>
+
+<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
+
+<div id="toc-navigation">
+</div>
+
+<div id="container"><div id="contents"><div class="content">
+
+ <h1>What's New</h1>
+
+<div class="note"><strong>News and Updates</strong>
+ <strong>Visual Studio 2017 Support</strong><p>Since the second preview, Visual Studio Tools for Tizen supports Microsoft Visual Studio 2017, released in March 2017.</p>
+</div>
+
+<p>The fourth preview of Tizen .NET is now available. The key new features are:</p>
+
+<ul>
+<li><strong>.NET Core 2.0 Preview</strong>
+<p>Microsoft has made many improvements as part of the .NET Core 2.0 Preview release. The following improvements are included in .NET Core 2.0 Preview:</p>
+ <ul>
+ <li>Massive API increase (over 100%) relative to .NET Core 1.x</li>
+ <li>Support for <a href="https://github.com/dotnet/standard" target="_blank">.NET Standard 2.0</a></li>
+ <li>Support for referencing .NET framework libraries and NuGet packages</li>
+ </ul>
+</li>
+<li><strong>Visual Studio Tools for Tizen update</strong>
+ <ul>
+ <li>Support for x86 Tizen .NET TV Emulator Preview: Preview 4 now provides 3 emulators - x64 TV, x64 Mobile, and x86 TV Emulators</li>
+ <li>API and Privilege Checker helps to verify that APIs and privileges are used as designed</li>
+ </ul>
+</li>
+<li><strong>Xamarin.Forms update</strong>
+ <ul>
+ <li>Support for the latest Xamarin.Forms version 2.3.5</li>
+ <li>Enhanced TV Control UX</li>
+ </ul>
+</li>
+<li><strong>TizenFX API</strong>
+<p>The following packages are newly available. For the full package list, see <a href="https://developer.tizen.org/dev-guide/csapi/index.html">TizenFX API</a>.</p>
+ <ul>
+ <li>Tizen.Log: Prints log messages to the Tizen logging system.</li>
+ <li>Tizen.Multimedia.Radio: Provides radio functionality.</li>
+ <li>Tizen.Network.IoTConnectivity: Manages, for example, resources, remote resources, requests, and responses based on the IoTivity project.</li>
+ <li>Tizen.Security.TEE: Connects client applications running in a rich operating environment with security-related trusted applications running inside a Trusted Execution Environment (TEE).</li>
+ <li>Tizen.Uix.VoiceControl: Controls the device through the user’s voice.</li>
+ </ul>
+</li>
+</ul>
+
+<script type="text/javascript" src="../scripts/jquery.zclip.min.js"></script>
+<script type="text/javascript" src="../scripts/showhide.js"></script>
+
+</div></div></div>
+
+<a class="top sms" href="#"><img src="../images/btn_top.gif" alt="Go to top" /></a>
+
+<div id="footer">
+<p class="footer">Except as noted, this content - excluding the Code Examples - is licensed under <a href="http://creativecommons.org/licenses/by/3.0/legalcode" target="_blank">Creative Commons Attribution 3.0</a> and all of the Code Examples contained herein are licensed under <a href="https://www.tizen.org/bsd-3-clause-license" target="_blank">BSD-3-Clause</a>.<br/>For details, see the <a href="https://www.tizen.org/content-license" target="_blank">Content License</a>.</p>
+</div>
+
+<script type="text/javascript">
+var _gaq = _gaq || [];
+_gaq.push(['_setAccount', 'UA-25976949-1']);
+_gaq.push(['_trackPageview']);
+(function() {
+var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+})();
+</script>
+
+</body>
+
+</html>
\ No newline at end of file
<body onload="prettyPrint()" style="overflow: auto;">
<div id="toc-navigation">
- <div id="profile">
- <p><img alt="Mobile C#" src="../images/mobile_s_cs.png"/> <img alt="TV C#" src="../images/tv_s_cs.png"/></p>
- </div>
-
<div id="toc_border"><div id="toc">
<p class="toc-title">Content</p>
<ul class="toc">
<title>Certificate Manager</title>
</head>
-<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
+<body onload="prettyPrint()" style="overflow: auto;">
<div id="toc-navigation">
+ <div id="toc_border"><div id="toc">
+ <p class="toc-title">Content</p>
+ <ul class="toc">
+ <li><a href="#selecting">Selecting the Certificates</a></li>
+ <li><a href="#creating">Creating a Certificate Profile</a></li>
+ <li><a href="#managing">Managing Certificate Profiles</a></li>
+ </ul>
+ </div></div>
</div>
<div id="container"><div id="contents"><div class="content">
<h1>Certificate Manager</h1>
-<p align="left">Before installing your application on a device or submitting it to the Tizen Store, it must be signed with a certificate profile. The certificate ensures the source of the application and makes sure it has not been tampered with since its publication. A certificate profile consists of author and distributor certificates. They can be made in Certificate Manager and they can be managed in <strong>Tools > Options > Tizen > Certification</strong>. The certificates can be created, edited, removed, and set as active in the Certificate Manager. The active certificates are used when packaging your application.</p>
-
-<p align="left">In Visual Studio Tools for Tizen, the certification can be defined in the following ways:</p>
+<p>Before installing your application on a device or submitting it to the Tizen Store, it must be signed with a certificate profile. The signature verifies the source of the application and makes sure it has not been tampered with since its publication. A certificate profile is a combination of the certificates used for signing.</p>
+<h2 id="selecting">Selecting the Certificates</h2>
+<p>To select the certificates used to package your application:</p>
+<ol>
+<li>In the Visual Studio menu, go to <strong>Tools > Options > Tizen > Certification</strong>.</li>
+<li>Define the certificates in one of the following ways:
<ul>
<li><strong>Using the default certificates</strong>
- <p>If you do not need to upload your application to the Tizen Store, you can use a default certificate and deploy your application in the Tizen Emulator. For using this option, set the certification as illustrated in the following figure.</p>
+ <p>If you do not need to upload your application to the Tizen Store, you can use a default certificate and deploy your application in the Tizen Emulator for testing purposes.</p>
+ <p>To use the default certificates, uncheck the <strong>Sign the .TPK file using the following option.</strong> checkbox.</p>
- <p align="center" class="figure"><strong>Figure: Using the default certificates</strong></p>
-
- <p align="center"><img alt="" height="125" src="../images/vstools_cert_default.png" width="943" /></p>
+ <p align="center"><img alt="Use default certificates" src="../images/vstools_cert_default.png" /></p>
</li>
<li><strong>Using an existing certificate profile</strong>
- <p>If you have used Tizen Studio and have already generated a certificate profile using the Tizen Certificate Manager, it can be imported in <strong>Tools > Options > Tizen > Certification</strong>. If you create a Certificate Profile using the Tizen Certificate Manager, it is set as default automatically.</p>
-
- <p align="center" class="figure"><strong>Figure: Using an existing certificate profile</strong></p>
+ <p>If you have used Tizen Studio before and have already generated a certificate profile using the Tizen Certificate Manager, you can import the profile by selecting <strong>Use profile of Tizen Certificate Manager</strong> from the drop-down list.</p>
+ <p>If you want to create a new certificate profile, see <a href="#creating">Creating a Certificate Profile</a>.</p>
- <p align="center"><img alt="" height="272" src="../images/vstools_cert_profile1.png" width="940" /></p>
+ <p align="center"><img alt="Use existing certificate profile" src="../images/vstools_cert_profile1.png" /></p>
</li>
<li><strong>Using your own certificates</strong>
- <p>If you already have author and distributor certificates, you can import them in <strong>Menu > Tools > Options > Tizen > Certification</strong>.</p>
+ <p>If you already have author and distributor certificates from another application store, you can import them by selecting <strong>Direct registration</strong> from the drop-down list and entering the required information.</p>
- <p align="center" class="figure"><strong>Figure: Using your own certificates</strong></p>
-
- <p align="center"><img alt="" height="576" src="../images/vstools_cert_certificate1.png" width="940" /></p>
+ <p align="center"><img alt="Use own certificates" src="../images/vstools_cert_certificate1.png" /></p>
</li>
-</ul>
+</ul></li>
+<li>Click <strong>OK</strong>.</li>
+</ol>
-<h2 id="certificate_profile">Certificate Profile and Certificates</h2>
-<p>The certificate profile consists of an author certificate and 1 or 2 distributor certificates. To distribute your application, you must create a certificate profile and sign the application with it:</p>
+<h2 id="creating">Creating a Certificate Profile</h2>
+<p>A certificate profile consists of an author certificate and 1 or 2 distributor certificates:</p>
<ul>
<li>An author certificate includes information about the author of the application. It is used to create an author signature, which ensures the integrity of the application from the author since the publication of the application.</li>
<li>A distributor certificate includes information about the distributor of the application, such as a store. It is used to create a distributor signature, which ensures the integrity of the application from the distributor since the distribution of the application.</li>
</ul>
-
-<h2 id="creating_certificate">Creating the Certificate Profile</h2>
-
-<p>You can create a new certificate profile with the Certificate Manager. To run the Certificate Manager, in the Visual Studio menu, select <strong>Tools > Tizen > Tizen Certificate Manager</strong>.</p>
-
-<p align="center" class="figure"><strong>Figure: Certificate Manager</strong></p>
-
-<p align="center"><img alt="" height="174" src="../images/vstools_cert_menu.png" width="861" /></p>
-
-<p>In the Certificate Manager, click the plus icon (<img alt="Plus icon" src="../images/cert_reg_plus.png" />) to create a new profile.</p>
-
-<p align="center" class="figure"><strong>Figure: Creating a new certificate profile</strong></p>
-
-<p align="center"><img alt="Creating a new certificate profile" src="../images/cert_reg_create_new.png" /></p>
-
-<p>You can create a new certificate profile with the creation wizard.</p>
-
-<p align="center" class="figure"><strong>Figure: Creation wizard</strong></p>
-
-<p align="center"><img alt="Creation wizard" src="../images/cert_reg_creation_wizard.png" /></p>
-
-<h2 id="adding_author">Adding the Author and Distributor Certificates</h2>
-
-<p>To add author and distributor certificates:</p>
-
-<ol>
- <li>Create a new author certificate or use a previously created author certificate.
+<p>To distribute your application, you must create a certificate profile and sign the application with it. You can create a new certificate profile with the Certificate Manager:</p>
+ <ol>
+ <li>In the Visual Studio menu, select <strong>Tools > Tizen > Tizen Certificate Manager</strong>.</li>
+<li>In the Certificate Manager window, click <strong>+</strong> to create a new profile.
+<p align="center"><img alt="Certificate Manager window" src="../images/cert_reg_create_new.png" /></p>
+<p>The certificate profile creation wizard opens.</p></li>
+<li>Enter a name for the profile and click <strong>Next</strong>.
+<p align="center"><img alt="Certificate profile creation wizard" src="../images/cert_reg_creation_wizard.png" /></p></li>
+
+<li>Add the author and distributor certificates:
+<ol type="a">
+ <li>Select whether to create a new author certificate or use a previously created author certificate, and click <strong>Next</strong>.
<p align="center"><img alt="Author certificate" src="../images/cert_reg_author_cert.png" /></p>
- </li>
- <li>Fill in the required information.
+ <p>Define the existing author certificate or enter the required information for a new certificate, and click <strong>Next</strong>.</p>
<p align="center"><img alt="Author information" src="../images/cert_reg_author_info.png" /></p>
</li>
- <li>You can use the default Tizen distributor certificate or another distributor certificate if you have one. In general, the default Tizen distributor certificate is used and you do not need to modify distributor certificates. You can also select the privilege level of the distributor certificate (in <a href="../../../org.tizen.training/html/native/details/sec_privileges_n.htm">native</a> and <a href="../../../org.tizen.training/html/web/details/sec_privileges_w.htm">Web</a> applications)).
- <p align="center"><img alt="Distributor certificate" height="453" src="../images/cert_reg_dist_cert2.png" width="666" /></p>
+ <li>You can use the default Tizen distributor certificate or another distributor certificate if you have one. In general, the default Tizen distributor certificate is used and you do not need to modify the distributor certificates. You can also select the privilege level of the distributor certificate (needed if the same certificate is used for signing <a href="../../../org.tizen.training/html/native/details/sec_privileges_n.htm">native</a> and <a href="../../../org.tizen.training/html/web/details/sec_privileges_w.htm">Web</a> applications).
+ <p align="center"><img alt="Distributor certificate" src="../images/cert_reg_dist_cert2.png" /></p>
</li>
-</ol>
+ <li>Click <strong>Finish</strong>.</li>
+</ol></li></ol>
-<h2 id="managing_certificate">Managing the Certificate Profile</h2>
+<h2 id="managing">Managing Certificate Profiles</h2>
-<p>You can also view, edit, and remove the certificate profiles you have created.</p>
+<p>You can view, edit, and remove the certificate profiles you have created in the Certificate Manager.</p>
-<p align="center" class="figure"><strong>Figure: Managing certificate profiles</strong></p>
+<p align="center"><strong>Figure: Managing certificate profiles</strong></p>
<p align="center"><img alt="Managing certificate profiles" src="../images/cert_reg_manage_cert.png" /></p>
<p>To manage a certificate profile:</p>
<ul>
- <li>Click the info icon (<img alt="Info" src="../images/cert_reg_info.png" />) to see detailed information of the certificate.
- <p align="center" class="figure"><strong>Figure: Certificate information</strong></p>
-
- <p align="center"><img alt="" height="560" src="../images/vstools_cert_result.png" width="695" /></p>
+ <li>To see the details of an individual certificate within the selected certificate profile, click the info button (<img alt="Info" src="../images/cert_reg_info.png" />).
+ <p align="center"><strong>Figure: Certificate information</strong></p>
+ <p align="center"><img alt="Certificate information" src="../images/vstools_cert_result.png" /></p>
</li>
- <li>Click the pencil icon (<img alt="Pencil" src="../images/cert_reg_pencil.png" />) to change the author or distributor certificate of the selected certificate profile.
- <p align="center" class="figure"><strong>Figure: Changing the certificate</strong></p>
-
- <p align="center"><img alt="" height="394" src="../images/vstools_changing_cert.png" width="666" /></p>
+ <li>To change the author or distributor certificate of the selected certificate profile, click the pencil button (<img alt="Pencil" src="../images/cert_reg_pencil.png" />).
+ <p align="center"><strong>Figure: Changing the certificate</strong></p>
+ <p align="center"><img alt="Changing the certificate" src="../images/vstools_changing_cert.png" /></p>
</li>
- <li>Click the trash icon (<img alt="Trash" src="../images/cert_reg_trash.png" />) to remove the selected certificate profile.
- <p align="center" class="figure"><strong>Figure: Removing the certificate profile</strong></p>
+ <li>To remove the selected certificate profile, click the trash button (<img alt="Trash" src="../images/cert_reg_trash.png" />).</li>
+ <li>To set the selected certificate profile as active, click the check button (<img alt="Check" src="../images/cert_reg_check.png" />).
+ <p>The active profile is used when you package your application. The active profile is also automatically set in <strong>Tools > Options > Tizen > Certification</strong>.</p>
+ <p align="center"><strong>Figure: Removing the certificate profile or setting it active</strong></p>
- <p align="center"><img alt="Removing the certificate profile" src="../images/cert_reg_remove_cert.png" /></p>
+ <p align="center"><img alt="Trash and check buttons" src="../images/cert_reg_trash_check.png" /></p>
</li>
- <li>The active profile is used when you package your application. Click the check icon to set the selected certificate profile as active. The active profile is also set in <strong>Tools > Options > Tizen > Certification</strong> automatically.</li>
</ul>
<p class="toc-title">Content</p>
<ul class="toc">
- <li><a href="#launching">Launching Tizen Device Manager</a></li>
- <li><a href="#connectexploreview">Connection Explore View</a></li>
+ <li><a href="#launch">Tizen Device Manager Launch</a></li>
+ <li><a href="#connectexploreview">Connection Explorer View</a></li>
+ <li><a href="#logview">Log View</a></li>
</ul>
</div>
</div>
<h1>Device Manager</h1>
-<p>Tizen Device Manager is a standalone tool that provides informations of connected Tizen device or emulators for application debugging.</p>
+<p>Tizen Device Manager is a standalone tool that provides information about connected Tizen devices or emulators for application debugging purposes.</p>
-<p>With this tool, you can manage the connected devices or emulators and you can also push or pull files from host PC to devices. Plus, the log viewer in device manager can help you to check logs from connected devices too.</p>
+<p>With this tool, you can manage the connected devices or emulators and push or pull files from the host computer to devices. The <strong>Log View</strong> allows you to check the logs from connected devices.</p>
-<p>The features provided are as follows.</p>
+<p>The Device Manager is implemented in the Visual Studio as the <strong>Connection Explorer</strong> and <strong>Log View</strong> views.</p>
-<ul>
- <li>Connection Explore View</li>
- <li>Log View</li>
-</ul>
+<p align="center"><strong>Figure: Device Manager</strong></p>
+<p align="center"><img alt="Device Manager" src="../images/cs_device_manager_first_screen.png" /></p>
-<h2 align="left">Launching Tizen Device Manager</h2>
+<h2 id="launch">Tizen Device Manager Launch</h2>
-<p>You can launch the Tizen Device Manager with below action</p>
+<p>You can launch the Tizen Device Manager in the following ways:</p>
<ul>
- <li>From Visual Studio tools for Tizen, select <span>Tools > Tizen > Tizen Device Manager</span>.<br />
- <br />
- <span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img alt="" height="188" src="../images/cs_device_manager_menu.png" width="623" /></span><br />
- </li>
- <li>From File Explorer, select <span>%program files%/Tizen/SDK/tools/device-manager</span>.<br />
- <span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img alt="" height="339" src="../images/cs_device_manager_explorer.png" width="700" /></span><br />
- </li>
- <li>From the command line, you can also launch the Tizen Device Manager.<br />
- <span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img alt="" height="120" src="../images/cs_device_manager_prompt.png" width="900" /></span><br />
- </li>
+ <li>In the Visual Studio menu, select <strong>Tools > Tizen > Tizen Device Manager</strong>.
+ <p align="center"><img alt="Launch from Visual Studio" src="../images/cs_device_manager_menu.png" /></p>
+ </li>
+ <li>In the Windows® <strong>Start</strong> menu, select <strong>Device Manager</strong>.
+ <p align="center"><img alt="Launch from Start menu" src="../images/cs_device_manager_start.png" /></p></li>
+ <li>In the command line, go to the <code><Program Files>/Tizen/SDK/tools/device-manager</code> directory and run the <code>device-manager.exe</code> command.
+ </li>
</ul>
-<p>If you can select this tool with above, Tizen Device Manager will be shown.</p>
-
-<p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img alt="" height="529" src="../images/cs_device_manager_first_screen.png" width="700" /></span></p>
-
-<h3> </h3>
-
-<h2>Connection Explore View</h2>
-
-<p>The connection explorer view shows the devices or emulators connected to the system.</p>
-<p>A list of connected devices is available after connecting a device or launching a Tizen emulator with a tree view.</p>
+<h2 id="connectexploreview">Connection Explorer View</h2>
-<p>The connection explorer view provides the following actions for the connected devices:</p>
+<p>The <strong>Connection Explorer</strong> view shows the devices connected to the system. A list of connected devices is available in tree view after connecting a device or launching a Tizen emulator. The <strong>Connection Explorer</strong> view provides the following actions for the connected devices:</p>
<ul>
- <li>Show a list of connected devices and connects devices for running and debugging the application.</li>
- <li>Provide file operations on connected devices like as push or pull.</li>
- <li>Send or receive files between the Project Explorer and Connection Explorer views by dragging and dropping.
- <ul>
- <li>showing folder/file list of connected device</li>
- <li>Information of file (date/size)</li>
- <li>create/delete/rename</li>
- <li>upload/download</li>
- </ul>
- </li>
- <li>Explore the file system on the connected devices.</li>
- <li>Launch the Emulator Manager to handle the multiple instances of the emulator.<br />
- </li>
+ <li>Show a list of connected devices and connect devices for running and debugging the application.</li>
+ <li>Provide file operations on connected devices.</li>
+ <li>Send or receive files between the <strong>Solution Explorer</strong> and <strong>Connection Explorer</strong> views by dragging and dropping.</li>
+ <li>Explore the file system on the connected devices.</li>
+ <li>Launch the Emulator Manager to handle multiple emulator instances.</li>
</ul>
+<p align="center"><strong>Figure: Connection Explorer view</strong></p>
+<p align="center"><img alt="Connection Explorer view" src="../images/cs_device_manager_connection_explorer_view.png" /></p>
-<p><img alt="" height="471" src="../images/cs_device_manager_connection_explorer_view.png" width="980" /><img src="../images/cs_device_manager_connection_explorer_view.png" /></p>
+<h2 id="logview">Log View</h2>
-<h3>Log View</h3>
+<p>The <strong>Log View</strong> helps you debug your application by capturing all the events logged by the platform and your application. The <strong>Log View</strong> shows the logs through the Tizen logging system.</p>
-<p>The Log view helps you debug your application by capturing all the events logged by the platform and your application.</p>
-
-<p>The Log view shows the logs through the Tizen.Library.</p>
-
-<p>You can create a log message as below. Tizen.Library is referenced in your project. So, you can call Log function.</p>
+<p>To create log messages, reference the Tizen library in your project and call the functions of the <a href="https://developer.tizen.org/dev-guide/csapi/classTizen_1_1Log.html">Tizen.Log</a> class:</p>
<pre class="prettyprint">
using System;
+
namespace XamarinApplication1.Tizen
{
class Program : global::Xamarin.Forms.Platform.Tizen.FormsApplication
{
protected override void OnCreate()
{
- // Using Tizen.Log directly
+ /// Using Tizen.Log directly
global::Tizen.Log.Debug("TEST", "Test Debug Message!");
global::Tizen.Log.Error("TEST", "Test Error Message!");
global::Tizen.Log.Fatal("TEST", "Test Fatal Message!");
global::Tizen.Log.Info("TEST", "Test Info Message!");
global::Tizen.Log.Verbose("TEST", "Test Verbose Message!");
- global::Tizen.Log.Warn("TEST", "Test Warn Message!");
+ global::Tizen.Log.Warn("TEST", "Test Warn Message!");
base.OnCreate();
LoadApplication(new App());
}
</pre>
-<p> </p>
-
-<h3>Adding and Removing the Log Tab</h3>
-
-<p>Adding a log tab:</p>
-
-<ol>
- <li>Click the Add LogTab icon.</li>
- <li>Type the tab name in the Name field and select a device in the Device list.</li>
- <li>Type the search keywords in the Tag, Pid, and Message fields.</li>
- <li>Click OK.</li>
-</ol>
-
-<p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img alt="" height="283" src="../images/cs_device_manager_log_add_tab.png" width="397" /></span><br />
-<br />
-<img alt="" height="470" src="../images/cs_device_manager_log_added_tab.png" width="980" /></p>
+<p>The <strong>Log View</strong> displays a log table consisting of the following fields:</p>
+<ul>
+<li><strong>Time</strong>: log time</li>
+<li><strong>Level</strong>: priority level indicates the urgency of the log message</li>
+<li><strong>Pid</strong>: process ID</li>
+<li><strong>Tid</strong>: thread ID</li>
+<li><strong>Tag</strong>: identification of the log message source</li>
+<li><strong>Message</strong>: log message</li>
+</ul>
-<p>Removing a log tab:</p>
+<h3>Adding and Removing Log Tabs</h3>
-<ol>
- <li>Click the log tab which you want to remove.</li>
- <li>Click the Remove LogTab button.<br />
- </li>
-</ol>
+<p>To add a log tab:</p>
+ <ol><li>Click the <strong>Add LogTab</strong> button (<img alt="Add LogTab icon" src="../images/log_view_icon.png" />).</li>
+ <li>Enter the tab name in the <strong>Name</strong> field and select a device in the <strong>Device</strong> list.</li>
+ <li>Enter the search keywords in the <strong>Tag</strong>, <strong>Pid</strong>, and <strong>Message</strong> fields.</li>
+ <li>Click <strong>OK</strong>.</li>
+ </ol>
+<p><img alt="Added log tab" src="../images/cs_device_manager_log_added_tab.png" /></p>
-<h3 id="DeviceManager-UnderstandingandFilteringLogs">Understanding and Filtering Logs</h3>
+<p>To remove a log tab:</p>
+ <ol>
+ <li>Click the log tab to be removed.</li>
+ <li>Click the <strong>Remove LogTab</strong> button (<img alt="Remove LogTab icon" src="../images/log_view_icon_remove_tab.png" />).</li>
+ </ol>
-<p>The log table consists of the following fields:</p>
-<ul>
- <li>
- <p>Time: log time</p>
- </li>
- <li>
- <p>Level: priority level indicates the urgency of the log message</p>
- </li>
- <li>
- <p>Pid: process ID</p>
- </li>
- <li>
- <p>Tid: thread ID</p>
- </li>
- <li>
- <p>Tag: identification of the log message source</p>
- </li>
- <li>
- <p>Message: log message</p>
- </li>
-</ul>
+<h3>Understanding and Filtering Logs</h3>
<p>In the log table, you have the following options and functions:</p>
<ul>
- <li>
- <p>Log level filtering option</p>
-
- <ul>
- <li>
- <p>In the Log view, you can filter the log messages using the V (verbose), D (debug), I (info), W (warning), E (error), and F (fatal) buttons to show specific log messages suitable to the selected type.</p>
- </li>
- </ul>
- </li>
- <li>Keyword filtering option
- <ul>
- <li>
- <p>You can filter the log messages by selecting one of the PID, Tag, and Message options, or entering keywords at the search box which is in the bottom of the log view. The keywords must be separated by a space and a comma.<br />
- </p>
- </li>
- </ul>
- </li>
- <li>Scroll lock
- <ul>
- <li>The log table shows the latest logs by default. This can make you uncomfortable when checking the specified log. Enable scroll lock when checking a specified log.<br />
- </li>
- </ul>
- </li>
- <li>
- <p>Clearing the table</p>
-
- <ul>
- <li>
- <p>You can remove all log messages from the log tab by clicking the clear the log icon.</p>
- </li>
- </ul>
- </li>
- <li>
- <p>Exporting logs to a file</p>
-
- <ul>
- <li>You can export the current log messages in the log tab and save them as a log file by clicking the export the log icon.</li>
- </ul>
- </li>
-</ul>
-
-<p> </p>
-
-<ul>
- <li>
- <p>Export the log<br />
- <br />
- <span class="confluence-embedded-file-wrapper"><img alt="" height="470" src="../images/cs_device_manager_log_export.png" width="980" /></span><br />
- </p>
- </li>
-</ul>
-
+<li>Log level filtering option
+<p>In the <strong>Log View</strong>, you can filter the log messages using the <strong>V</strong> (verbose), <strong>D</strong> (debug), <strong>I</strong> (info), <strong>W</strong> (warning), <strong>E</strong> (error), and <strong>F</strong> (fatal) buttons to show the log messages matching the selected type.</p></li>
+<li>Keyword filtering option
+<p>You can filter the log messages by selecting one of the <strong>PID</strong>, <strong>Tag</strong>, and <strong>Message</strong> options, or entering keywords in the bottom of the <strong>Log View</strong>. The keywords must be separated by a space or a comma.</p></li>
+<li>Scroll lock
+<p>The log table shows the latest logs by default. While the application is running, the log table scrolls as new logs are added to the table. To stop the table from scrolling while you are checking a specific log, click the <strong>Scroll Lock</strong> button (<img alt="Scroll lock button" src="../images/log_view_icon_lock.png" />).</p></li>
+<li>Clearing the table
+<p>You can remove all log messages from the log tab by clicking the <strong>Clear the log</strong> button (<img alt="Clear the log button" src="../images/log_view_icon_clear.png" />).</p></li>
+<li>Exporting logs to a file
+<p>You can export the current log messages in the log tab and save them as a log file by clicking the <strong>Export the log</strong> button (<img alt="Export the log button" src="../images/log_view_icon_export.png" />).</p>
+</li></ul>
+<p align="center"><strong>Figure: Exporting a log file</strong></p>
+<p align="center"><img alt="Exporting a log file" src="../images/cs_device_manager_log_export.png" /></p>
<script type="text/javascript" src="../scripts/jquery.zclip.min.js"></script>
<script type="text/javascript" src="../scripts/showhide.js"></script>
<title>Emulator Control Panel</title>
</head>
-<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
+<body onload="prettyPrint()" style="overflow: auto;">
<div id="toc-navigation">
+ <div id="toc_border"><div id="toc">
+ <p class="toc-title">Content</p>
+ <ul class="toc">
+ <li><a href="#controls">Using the Control Keys and Context Menu</a></li>
+ <li><a href="#panel">Using the Control Panel</a></li>
+ </ul>
+ </div></div>
</div>
-
<div id="container"><div id="contents"><div class="content">
<h1>Emulator Control Panel</h1>
<p>Before deploying your application, it is important that you test it in an environment similar to a real device.</p>
-<p>You can run the application in the emulator, and test a variety of user scenarios, such as network access, audio input and out, and text messages. You can control the application in the emulator with mouse and keyboard buttons, like if you used an actual device.</p>
+<p>You can run the application in the emulator, and test a variety of user scenarios, such as network access, audio input and out, and text messages. With a mouse and keyboard, you can control the application in the emulator just like on an actual device.</p>
-<p>During the run, you can use the Emulator Control Panel to inject events for several system options that the actual device provides. For example, by manipulating the optional battery, you can simulate the application in different charge environments.</p>
+<p>While the application is running, you can use the Emulator Control Panel to simulate events for a variety of system options that the actual device provides. For example, by manipulating the virtual battery, you can simulate the application in different charge environments.</p>
<p>The emulator controls consist of internal and external parts:</p>
<ul>
- <li>The <strong><strong><strong>HOME</strong></strong></strong>, <strong><strong><strong>Volume control</strong></strong></strong> and <strong><strong><strong>Back</strong></strong></strong> buttons, for example, are external parts controlling the device from the outside.
+ <li>The <strong>HOME</strong>, <strong>Volume control</strong> and <strong>Back</strong> buttons, for example, are external parts controlling the device from the outside.
- <p>In the emulator, the external parts are called the <strong><strong><strong>emulator control keys and menu</strong></strong></strong>.</p>
- </li>
- <li>Battery level and screen brightness, for example, are internal parts controlling the device from the inside. In the emulator, the internal parts are called the <strong><strong><strong>Emulator Control Panel</strong></strong></strong>.</li>
+<p>In the emulator, the external parts are called the <strong>emulator control keys and menu</strong>.</p></li>
+ <li>Battery level and screen brightness, for example, are internal parts controlling the device from the inside. In the emulator, the internal parts are called the <strong>Emulator Control Panel</strong>.</li>
</ul>
<h2 id="controls">Using the Control Keys and Context Menu</h2>
-<p>The control keys are visible on the emulator when you start it. To access the context menu, right-click the emulator. The following figure illustrates the TV and mobile emulator.</p>
+<p>The control keys are visible on the emulator when you start it. To access the context menu, right-click the emulator.</p>
-<p align="center" class="figure"><strong><strong><strong>Figure: TV and mobile emulator</strong></strong></strong></p>
+<p align="center"><strong>Figure: TV and mobile emulators</strong></p>
+<p align="center"><strong><img alt="TV and mobile emulators" src="../images/emulator_tv_mobile.png" /></strong></p>
-<p align="center" class="figure"><strong><img alt="" height="281" src="../images/em_skin.png" width="750" /></strong></p>
+<div class="note"><strong>Note</strong>You can create a custom resolution emulator by using the <a href="../../../org.tizen.studio/html/common_tools/emulator_manager.htm#control">Emulator Manager CLI</a>, and launch it with the TV and mobile skin. It is not guaranteed that all applications are correctly shown in the custom resolution.</div>
-<div class="note"><strong><strong>Note</strong></strong>You can create a custom resolution emulator by using the <a href="../../../org.tizen.studio/html/common_tools/emulator_manager.htm#control"><u><font color="#000080">Emulator Manager CLI</font></u></a>, and launch it with the TV and mobile skin. It is not guaranteed that all the applications are correctly shown in the custom resolution.</div>
-
-<h3 id="controlkeys" name="controlkeys">Control Keys</h3>
+<h3 id="controlkeys">Control Keys</h3>
<p>The following hardware keys are available on the emulator:</p>
<ul>
- <li><strong><strong><strong>Menu</strong></strong></strong>
-
- <p>When tapped, it opens a list of options available for the current screen. This button can be used to delete an application on the TV platform.</p>
+ <li><strong>Menu</strong>
+ <p>When tapped, a list of options available for the current screen opens. On the TV platform, the options include removing an application.</p>
</li>
- <li><strong><strong><strong>Home</strong></strong></strong>
- <p>When long-pressed, the Task switcher application opens as in a real device.</p>
+ <li><strong>Home</strong>
+ <p>When long-pressed, the Task switcher application opens as on a real device.</p>
</li>
- <li><strong><strong><strong>Back</strong></strong></strong>
+ <li><strong>Back</strong>
<p>When tapped, the emulator returns to the previous screen.</p>
</li>
- <li><strong><strong><strong>Power</strong></strong></strong>
- <p>You can power off the display by tapping the <strong><strong><strong>Power</strong></strong></strong> key in most general situations. Sometimes, the display does not power off though you tap the <strong><strong><strong>Power</strong></strong></strong> key. This is to guarantee the operation of a current application, such as the Stopwatch in the Clock application. If you tap the <strong><strong><strong>Power</strong></strong></strong> or <strong><strong><strong>Home</strong></strong></strong> key again, the display is powered on.</p>
+ <li><strong>Power</strong>
+ <p>You can power off the display by tapping the <strong>Power</strong> key in most situations. Sometimes, the display does not power off when you tap the <strong>Power</strong> key. This is to guarantee the operation of a current application, such as the Stopwatch in the Clock application. If you tap the <strong>Power</strong> or <strong>Home</strong> key again, the display is powered on.</p>
</li>
- <li><strong><strong><strong>Volume Up</strong></strong></strong> and <strong><strong><strong>Volume Down</strong></strong></strong> (mobile only)
+ <li><strong>Volume Up</strong> and <strong>Volume Down</strong> (mobile only)
<p>When tapped, the volume changes accordingly.</p>
</li>
<li>
- <p><strong><strong>Arrow keys </strong></strong>(TV only)</p>
+ <p><strong>Arrow keys </strong>(TV only)</p>
- <p>When tapped, the cursor or selection moves to the desired direction.</p>
+ <p>When tapped, the cursor or selection moves in the desired direction.</p>
</li>
<li>
- <p><strong><strong>OK </strong></strong>(TV only)</p>
+ <p><strong>OK </strong>(TV only)</p>
<p>When tapped, the item is selected.</p>
</li>
</ul>
-<h3 name="menu"> </h3>
-
-<h3 id="menu" name="menu">Context Menu</h3>
+<h3 id="menu">Context Menu</h3>
<p>You can access the context menu by right-clicking the emulator. In the menu, you can select:</p>
<ul>
<li>Emulator name (the top row in the menu)
- <p>The <strong><strong><strong>Detailed Info</strong></strong></strong> window is displayed, showing the <strong><strong><strong>Shortcut Info</strong></strong></strong> and <strong><strong><strong>VM Info</strong></strong></strong> tabs. The <strong><strong><strong>Shortcut Info</strong></strong></strong> tab lists the <a href="../../../org.tizen.studio/html/common_tools/keyboard_shortcuts.htm#emulator"><u><font color="#000080">emulator keyboard shortcuts</font></u></a> and the <strong><strong><strong>VM Info</strong></strong></strong> tab defines the virtual machine details.</p>
-
- <p>In Mac OS® X: To use the emulator keyboard shortcuts, open the Keyboard Setting dialog and switch your Mac function keys option to work as standard function keys.</p>
+ <p>The <strong>Detailed Info</strong> window is displayed, showing the <strong>Shortcut Info</strong> and <strong>VM Info</strong> tabs. The <strong>Shortcut Info</strong> tab lists the <a href="../../../org.tizen.studio/html/common_tools/keyboard_shortcuts.htm#emulator">emulator keyboard shortcuts</a> and the <strong>VM Info</strong> tab defines the virtual machine details.</p>
- <p align="center" class="Table"><strong><strong><strong>Table: VM Info</strong></strong></strong></p>
+ <p align="center" class="Table"><strong>Table: VM Info</strong></p>
<table border="1">
<tbody>
<th>Description</th>
</tr>
<tr>
- <td>VM Name</td>
+ <td><strong>VM Name</strong></td>
<td>VM name</td>
</tr>
<tr>
- <td>Skin Name</td>
+ <td><strong>Skin Name</strong></td>
<td>Skin name</td>
</tr>
<tr>
- <td>CPU Arch</td>
+ <td><strong>CPU Arch</strong></td>
<td>CPU architecture</td>
</tr>
<tr>
- <td>RAM Size</td>
+ <td><strong>RAM Size</strong></td>
<td>RAM size (in MB)</td>
</tr>
<tr>
- <td>Display</td>
- <td>Target display resolution (in DPI; Dots Per Inch)</td>
+ <td><strong>Display</strong></td>
+ <td>Target display resolution (in DPI; Dots Per Inch)</td>
</tr>
<tr>
- <td>Network connection</td>
+ <td><strong>Network Connection</strong></td>
<td>NAT (Network Address Translation) or Bridged</td>
</tr>
<tr>
- <td>CPU Virtualization</td>
+ <td><strong>CPU Virtualization</strong></td>
<td>Whether hardware virtualization is supported</td>
</tr>
<tr>
- <td>GPU Virtualization</td>
+ <td><strong>GPU Virtualization</strong></td>
<td>Whether GPU virtualization is supported</td>
</tr>
<tr>
- <td>Platform Image Version</td>
- <td>Version of the used platform image</td>
+ <td><strong>Platform Image Version</strong></td>
+ <td>Version of the used platform image</td>
</tr>
<tr>
- <td>Platform Image File</td>
- <td>Location of the used platform image</td>
+ <td><strong>Platform Image File</strong></td>
+ <td>Location of the used platform image</td>
</tr>
<tr>
- <td>Directory Sharing</td>
+ <td><strong>Directory Sharing</strong></td>
<td>Whether host directory sharing is used</td>
</tr>
<tr>
- <td>File Shared Path</td>
+ <td><strong>File Shared Path</strong></td>
<td>Path to the shared host directory</td>
</tr>
<tr>
- <td>Kernel Log File</td>
+ <td><strong>Kernel Log File</strong></td>
<td>Kernel log file path</td>
</tr>
<tr>
- <td>Emulator Log File</td>
+ <td><strong>Emulator Log File</strong></td>
<td>Emulator (Qemu) log file path</td>
</tr>
<tr>
- <td>Emulator Version</td>
- <td>Tizen Emulator version</td>
+ <td><strong>Emulator Version</strong></td>
+ <td>Tizen Emulator version</td>
</tr>
</tbody>
</table>
</li>
- <li><strong><strong><strong>Always On Top</strong></strong></strong>
+ <li><strong>Always On Top</strong>
<p>Select this option to keep the emulator window on top of other windows.</p>
</li>
- <li><strong><strong><strong>Rotate </strong></strong></strong>(mobile only)
- <p>Select either <strong><strong><strong>Portrait</strong></strong></strong>, <strong><strong><strong>Landscape</strong></strong></strong>, <strong><strong><strong>Reverse Portrait</strong></strong></strong>, or <strong><strong><strong>Reverse Landscape</strong></strong></strong> as the orientation of the emulator.</p>
- </li>
- <li><strong><strong><strong>Scale</strong></strong></strong> (mobile only)
- <p>Scale the size of the emulator between 1x, 1/2x (default), 3/4x, and 1/4x.</p>
- </li>
- <li><strong><strong><strong>Advanced > Controller</strong></strong></strong>
- <p>Show or hide the controller window.</p>
+ <li><strong>Rotate</strong> (mobile only)
+<p>Select either <strong>Portrait</strong>, <strong>Landscape</strong>, <strong>Reverse Portrait</strong>, or <strong>Reverse Landscape</strong> as the orientation of the emulator.</p></li>
- <div class="note"><strong><strong><strong>Note</strong></strong></strong>The Controller menu is not supported in the profile-specific skin.</div>
- </li>
- <li><strong><strong><strong>Advanced > Screenshot</strong></strong></strong>
- <p>Capture a screenshot of the emulator.</p>
- </li>
- <li><strong><strong><strong>Advanced > About</strong></strong></strong>
- <p>Display the emulator version and build time.</p>
- </li>
- <li><strong><strong><strong>Advanced > Force Reboot</strong></strong></strong>
- <p>Force the emulator to reboot. Since force rebooting the emulator can cause problems, use the reboot option from the SDB shell to reboot the emulator. Use <strong><strong><strong>Force Reboot</strong></strong></strong> only when absolutely necessary.</p>
- </li>
- <li><strong><strong><strong>Advanced > Force Close</strong></strong></strong>
- <p>Force the emulator to exit. Since force stopping the emulator can cause problems, use the <strong><strong><strong>Close</strong></strong></strong> option to exit the emulator. Use <strong><strong><strong>Force Close</strong></strong></strong> only when absolutely necessary.</p>
- </li>
- <li><strong><strong><strong>Shell</strong></strong></strong>
- <p>Open a Smart Development Bridge (SDB) shell command window.</p>
- </li>
- <li><strong><strong><strong>Control Panel</strong></strong></strong>
- <p>Help to control or monitor the state of the emulator dynamically.</p>
- </li>
- <li><strong><strong><strong>Close</strong></strong></strong>
- <p>Exit the emulator.</p>
- </li>
-</ul>
-
-<div class="note"><strong><strong><strong>Note</strong></strong></strong>In Ubuntu, you must change a global GNOME setting to view the menu icons:
-
-<ol>
- <li>In the command console, execute the <code>gconf-editor</code> command.</li>
- <li>In the tree, navigate to <code>desktop > gnome > interface</code>.</li>
- <li>Enable the <code>menus_have_icons</code> option.</li>
-</ol>
-</div>
-
-<h2 id="panel">Using the Control Panel</h2>
+<li><strong>Scale</strong> (mobile only)
+<p>Scale the size of the emulator between 1x, 1/2x (default), 3/4x, and 1/4x.</p></li>
-<p>With the Emulator Control Panel, you can inject system events and perform related tasks.</p>
-
-<p align="center" class="figure"><span>Figure: Emulator Control Panel</span></p>
-
-<p align="center"><span><img alt="Emulator Control Panel" src="../images/emulator_control_panel2.png" /></span></p>
-
-<p>The control panel consists of 3 layers:</p>
-
-<ul>
- <li><strong><strong><strong>Dialog</strong></strong></strong>, which is the main application window, shows a list of testable device cards.</li>
- <li><strong><strong><strong>Card</strong></strong></strong>, which represents each device, shows the representative device status. By clicking a card, you can inject an event directly or open <strong><strong><strong>Popup</strong></strong></strong> to do it.</li>
- <li><strong><strong><strong>Popup</strong></strong></strong> displays testable events for each device.</li>
-</ul>
-
-<p align="center" class="figure"><strong><strong><strong>Figure: Emulator Control Panel Layers</strong></strong></strong></p>
-
-<p align="center"><strong><img alt="" height="539" src="../images/emulator_control_panel2-1.png" width="1360" /></strong></p>
-
-<p>To open the control panel:</p>
-
-<ol>
- <li>Launch the emulator.</li>
- <li>Right-click the emulator and select <strong><strong><strong>Control Panel</strong></strong></strong>.</li>
-</ol>
-
-<p align="center" class="figure"><strong><strong><strong>Figure: Opening the control panel</strong></strong></strong></p>
-
-<p align="center"><strong><img alt="Opening the control panel" height="668" src="../images/emulator_control_panel_open2.png" width="515" /></strong></p>
-
-<p>The main features of the Emulator Control Panel are described in the following sections.</p>
-
-<h3>Controlling the Network Setting</h3>
-
-<p>You can control the user network.</p>
-
-<p>To lose the network connection, set the link status to off. To forward a remote or local port to an inside port of the emulator, enter values in text boxes, and click <strong><strong><strong>Apply</strong></strong></strong>.</p>
-
-<p align="center" class="figure"><span>Figure: Network Setting</span></p>
-
-<p align="center"><span><img alt="" height="539" src="../images/emulator_control_panel_network.png" width="1360" /></span></p>
-
-<h3>Mounting a Host Directory</h3>
-
-<p>The specified host directory is mounted to <code>/mnt/host</code> to share resources. Therefore, file transfer is possible through the host directory sharing feature without using the SDB utility.</p>
-
-<p align="center" class="figure"><span>Figure: Host Directory Sharing</span></p>
-
-<p align="center"><span><img alt="" height="539" src="../images/emulator_control_panel_hds.png" width="1360" /></span></p>
-
-<h3>Providing Device Data</h3>
-
-<p>The control panel can be used to simulate device data, such as the battery level, adding or removing a earjack (headset) or USB device, setting RSSI (remote signal strength indicator) information, and attaching and detaching the SD card:</p>
-
-<ul>
- <li>In the <strong><strong><strong>Battery</strong></strong></strong> card, set the battery level using the <strong><strong><strong>Level</strong></strong></strong> slider. To set the charger status to connected or disconnected, select the appropriate <strong><strong><strong>Charger</strong></strong></strong> radio button.</li>
- <li>In the <strong><strong><strong>EarJack</strong></strong></strong> card, select the earjack setting:
- <ul>
- <li><strong><strong><strong>3 Wire</strong></strong></strong></li>
- <li><strong>4 Wire</strong></li>
- <li><strong>Disconnect</strong></li>
- </ul>
- </li>
- <li>In the <strong><strong><strong>USB</strong></strong></strong> card, set the USB device setting to the connected or disconnected state.</li>
- <li>In the <strong><strong><strong>RSSI</strong></strong></strong> card, set the RSSI information level using the <strong><strong><strong>Level</strong></strong></strong> slider.</li>
- <li>In the <strong><strong><strong>SD Card</strong></strong></strong> card, select the <strong><strong><strong>4G</strong></strong></strong>, <strong><strong><strong>8G</strong></strong></strong>, <strong><strong><strong>16G</strong></strong></strong>, or <strong><strong><strong>32G</strong></strong></strong> SD card and attach it to the emulator at runtime.
- <div class="note"><strong><strong><strong>Note</strong></strong></strong>The same SD card cannot be attached to multiple emulators at the same time.</div>
- </li>
-</ul>
-
-<p>The device information set using the control panel is reflected on the indicator bar of the device.</p>
-
-<h3>Providing Location Data</h3>
-
-<p>The control panel can be used to provide imitated responses to location data requests by loading GPS log files, manually entering location coordinates, or injecting markers directly on the map in the <strong><strong><strong>Location</strong></strong></strong> tab:</p>
-
-<ul>
- <li>Loading a GPS log file
- <p>In the <strong><strong><strong>Log</strong></strong></strong> section, select the pre-logged GPS data file (NMEA183 format) and click <strong><strong><strong>Inject Log</strong></strong></strong> to send the location data to the emulator.</p>
- </li>
- <li>Manually entering location coordinates
- <p>In the <strong><strong><strong>Manual</strong></strong></strong> section, enter the coordinates and click <strong><strong><strong>Inject Location</strong></strong></strong> to send the location data to the emulator. The range of the latitude, longitude, altitude, and horizontal accuracy is from -90 to 90, -180 to 180, -300 to 100000, and 0 to 100000, respectively.</p>
- </li>
- <li>Injecting markers on the map
- <p>In the <strong><strong><strong>Map</strong></strong></strong> section, right-click the desired map locations and click <strong><strong><strong>Inject Markers</strong></strong></strong> to send the location data to the emulator.</p>
- </li>
-</ul>
-
-<h3>Providing NFC Data</h3>
-
-<p>The control panel can be used to test the near-field communication (NFC) features, such as NFC data exchange format (NDEF) events, NFC tag detection, and peer-to-peer (P2P) data connections in the <strong><strong><strong>NFC</strong></strong></strong> tab.</p>
+ <li><strong>Advanced > Controller</strong>
+ <p>Show or hide the controller window.</p>
+<div class="note">
+ <strong>Note</strong>
+ The <strong>Controller</strong> menu is not supported in the profile-specific skin.
+</div></li>
+<li><strong>Advanced > Screenshot</strong>
+<p>Capture a screenshot of the emulator.</p></li>
-<div class="note"><strong><strong><strong>Note</strong></strong></strong>The control panel only sends NFC-related events to the emulator. There is no actual information exchange between the control panel and emulator. Therefore, for features such as writing information to an NFC tag, the emulator simply displays a success message.</div>
+<li><strong>Advanced > About</strong>
+<p>Display the emulator version and build time.</p></li>
-<ul>
- <li>Creating NDEF messages
- <p>An NDEF message contains one or more NDEF records. In the <strong><strong><strong>NDEF Message</strong></strong></strong> section:</p>
+<li><strong>Advanced > Force Reboot</strong>
+<p>Force the emulator to reboot. Since force rebooting the emulator can cause problems, use the reboot option from the SDB shell to reboot the emulator. Use <strong>Force Reboot</strong> only when absolutely necessary.</p></li>
- <ol>
- <li>Select the record type name format.</li>
- <li>Enter the record type name, ID, and payload.</li>
- <li>Click <strong><strong><strong>Add</strong></strong></strong>.</li>
- </ol>
+<li><strong>Advanced > Force Close</strong>
+<p>Force the emulator to exit. Since force stopping the emulator can cause problems, use the <strong>Close</strong> option to exit the emulator. Use <strong>Force Close</strong> only when absolutely necessary.</p></li>
- <p>You can add multiple NDEF records, as required, in the NDEF message.</p>
+<li><strong>Shell</strong>
+<p>Open a Smart Development Bridge (SDB) shell command window.</p></li>
- <p>Click <strong><strong><strong>Edit</strong></strong></strong> or <strong><strong><strong>Remove</strong></strong></strong> to modify or delete a selected record.</p>
- </li>
- <li>Attaching and detaching NFC tags
- <p>In the <strong><strong><strong>NFC Tag</strong></strong></strong> section:</p>
+<li><strong>Control Panel</strong>
+<p>Control or monitor the state of the emulator dynamically. </p></li>
- <ol>
- <li>Select the tag type.</li>
- <li>Click <strong><strong><strong>Tag Attach</strong></strong></strong>.
- <p>If the NDEF record list is not empty, an NDEF message is created using this list and the attach message is sent to the emulator with the NDEF message.</p>
- </li>
- <li>When the tag operation is finished, click <strong><strong><strong>Tag Detach</strong></strong></strong>.</li>
- </ol>
- </li>
- <li>Creating a P2P data Connection
- <p>In the <strong><strong><strong>Peer to Peer</strong></strong></strong> section:</p>
+<li><strong>Close</strong>
+<p>Exit the emulator.</p></li>
- <ul>
- <li>To send the emulator the discovered state of the new device, click <strong><strong><strong>P2P Discovered</strong></strong></strong>.</li>
- <li>To send the emulator an NDEF message, click <strong><strong><strong>P2P Send</strong></strong></strong>.</li>
- <li>To send the emulator the detached state of the connected device, click <strong><strong><strong>P2P Detached</strong></strong></strong>.</li>
- </ul>
- </li>
</ul>
-<h3>Providing Sensor Data</h3>
-
-<p>In the control panel, you can model your actions, such as shaking, throwing, and tilting the device for the emulator instance. In addition, you can generate a single sensor event on the instance, or inject sequences of 3-axis sensor events to the instance.</p>
-
-<p>To control 3-axis sensors, select <strong><strong><strong>Event Injector > Sensor > 3-Axis Sensor</strong></strong></strong>. The <strong><strong><strong>3-Axis Sensor</strong></strong></strong> tab consist of 4 subtabs, in which you can adjust the acceleration, magnetic, and gyro sensors of the emulator instance. In the <strong><strong><strong>GUI</strong></strong></strong> subtab, you can intuitively adjust various sensor data by using 3D graphics. In the other subtabs, you can inject a single event into the individual sensor, or use the sensor data files to inject sequences of events into the sensor.</p>
-
-<ul>
- <li>GUI
- <p>In the <strong><strong><strong>GUI</strong></strong></strong> subtab, you can select an active sensor and move the 3D model of the emulator instance by the 3 axis sliders or direction buttons (<strong><strong><strong>Portrait</strong></strong></strong>, <strong><strong><strong>Landscape</strong></strong></strong>, <strong><strong><strong>Reverse Portrait</strong></strong></strong>, and <strong><strong><strong>Reverse Landscape</strong></strong></strong>). The instance monitor displays the acceleration, magnetic, and gyro values.</p>
-
- <p>To better control the movement, select the <strong><strong><strong>With axis</strong></strong></strong> checkbox to see the axes in the emulator image. You can also fix the Y or Z axis by selecting the <strong><strong><strong>X/Z</strong></strong></strong> or <strong><strong><strong>X/Y</strong></strong></strong> radio button, respectively. To change the emulator accelerator value in the direction of the movement, select the <strong><strong><strong>Move</strong></strong></strong> radio button.</p>
- </li>
- <li>Acceleration
- <p>You can control the acceleration of the instance along the coordinate axes. When the instance is standing, the acceleration value of the Y axis is -1 g as gravitational acceleration. By using the sliders in the <strong><strong><strong>Acceleration</strong></strong></strong> subtab, you can control the acceleration 3-axis values from -2 g to 2 g.</p>
- </li>
- <li>Magnetic
- <p>You can control the magnetic values of the instance along the coordinate axes. When the instance is standing, the magnetic 3-axis tesla values (azimuth 0) are set for the North. By using the sliders in the <strong><strong><strong>Magnetic</strong></strong></strong> subtab, you can control the magnetic 3-axis values from -2000 uT to 2000 uT.</p>
- </li>
- <li>Gyro
- <p>You can control the gyro (rotation angle per second) of the instance along the coordinate axes. By using the sliders in the <strong><strong><strong>Gyro</strong></strong></strong> subtab, you can control the gyro 3-axis values from -573 deg/s to 573 deg/s.</p>
- </li>
- <li>Event file
- <p>The event file consists of predefined events. It is written in ASCII. By loading the event file in the <strong><strong><strong>Acceleration</strong></strong></strong>, <strong><strong><strong>Magnetic</strong></strong></strong>, or <strong><strong><strong>Gyro</strong></strong></strong> subtab, you can replay a sequence of predefined events. You can also add multiple event files to replay. The format of each line in the event file is:</p>
-
- <pre class="prettyprint">
-timestamp, x, y, z
-</pre>
+<h2 id="panel">Using the Control Panel</h2>
- <p>When you add the event files and click <strong><strong><strong>Start</strong></strong></strong>, the predefined events are injected at their specified relative timestamp. The timestamp unit is 0.01 seconds. Some events can be discarded, if they exceed certain limits of performance, resource, or logic. When you add multiple event files, the files are executed in sequence. You can also repeat the replay.</p>
- </li>
-</ul>
+<p>With the Emulator Control Panel, you can simulate system events and perform related tasks.</p>
-<p>In the <strong><strong><strong>Event Injector > Sensor</strong></strong></strong> tab, you can control other sensors, such as light, proximity, pressure, ultraviolet, and HRM sensors:</p>
+<p>The control panel consists of 3 layers:</p>
<ul>
- <li>To control the light sensor, set the Lux value in the <strong><strong><strong>Light</strong></strong></strong> tab. The range of this value is from 0 Lux to 65635 Lux.
-
- <p>If you set brightness as <strong><strong><strong>auto</strong></strong></strong>, the display is changed based on the injected light value.</p>
- </li>
- <li>To control the proximity sensor, set it on or off in the <strong><strong><strong>Proximity</strong></strong></strong> tab.</li>
- <li>To control the pressure sensor, set the hPa (Hectopascal) value in the <strong><strong><strong>Pressure</strong></strong></strong> tab. The range of this value is from 260 hPa to 1260 hPa.</li>
- <li>To control the ultraviolet sensor, use the slider in the <strong><strong><strong>Ultraviolet</strong></strong></strong> tab. The unit is UV index and the range of this value is from 0 to 15.0.</li>
- <li>To control the HRM (Heart Rate Monitor) sensor, use the sliders in the <strong><strong><strong>Heart Rate Monitor</strong></strong></strong> tab. You can set the <strong><strong><strong>Heart Rate</strong></strong></strong> value between 0 and 220, and the <strong><strong><strong>Peek-to-Peek</strong></strong></strong> value between 0 and 5000 (in milliseconds).</li>
+<li><strong>Dialog</strong> is the main Emulator Control Panel window, which shows a list of testable device cards.</li>
+<li><strong>Card</strong> represents a peripheral device or system option, and shows the respective device or option status. By clicking a card, you can simulate an event directly or open a <strong>Popup</strong> to do it. </li>
+<li><strong>Popup</strong> displays testable events for a peripheral device.</li>
</ul>
-<h3>Providing Telephony Features</h3>
-
-<p>The control panel can be used to generate incoming calls and messages in the <strong><strong><strong>Telephony</strong></strong></strong> tab.</p>
-
-<ul>
- <li>Generating incoming calls
- <p>Incoming calls are generated in the <strong><strong><strong>Event Injector > Telephony > Call</strong></strong></strong> tab.</p>
-
- <div class="note"><strong><strong><strong>Note</strong></strong></strong>A Mobile Termination (MT) call is made from the Event Injector view to the emulator. A Mobile Origination (MO) call is made from the emulator to the Event Injector view using the phone application of the emulator.</div>
-
- <p>To make an MT call:</p>
+<p align="center"><strong>Figure: Emulator Control Panel layers</strong></p>
+<p align="center"><strong><img alt="Emulator Control Panel layers" src="../images/emulator_control_panel_layers.png" /></strong></p>
- <ol>
- <li>Enter the phone number you want to imitate the call from.</li>
- <li>Click <strong><strong><strong>Connect</strong></strong></strong>.</li>
- <li>To hide the phone number on the emulator, select the <strong><strong><strong>Hidden</strong></strong></strong> option.
- <p>The caller ID on the emulator is set to "Unknown".</p>
- </li>
- </ol>
-
- <p>To make an MO call, use the emulator's phone application:</p>
-
- <ol>
- <li>To ready the emulator for the connection, click <strong><strong><strong>Alert</strong></strong></strong>.</li>
- <li>To ready the emulator for the call, click <strong><strong><strong>Connect</strong></strong></strong>.</li>
- </ol>
- </li>
- <li>Generating messages
- <p>SMS messages are generated in the <strong><strong><strong>Event Injector > Telephony > Messaging</strong></strong></strong> tab. After sending a message, your application waits for the asynchronous send status message. You can generate this status report for SMS messages using the same <strong><strong><strong>Messaging</strong></strong></strong> tab.</p>
-
- <p>To generate an SMS message:</p>
-
- <ol>
- <li>Enter the sender phone number you want to imitate.</li>
- <li>Enter the message body text and click <strong><strong><strong>Send Msg</strong></strong></strong>.</li>
- </ol>
-
- <p>To generate status reports, set the sending status value for the SMS message:</p>
-
- <ul>
- <li><strong><strong><strong>SMS OK</strong></strong></strong> (Success)</li>
- <li><strong><strong><strong>SMS Not Available</strong></strong></strong></li>
- </ul>
-
- <p>You can also generate MMS message status reports. To generate MMS status reports, set the sending status value for the MMS message:</p>
-
- <ul>
- <li><strong><strong><strong>MMS OK</strong></strong></strong> (Success)</li>
- <li><strong><strong><strong>MMS Failure</strong></strong></strong></li>
- </ul>
- </li>
-</ul>
-
-<h3>Providing Memory Data</h3>
-
-<p>The control panel can be used to simulate low memory status in the <strong><strong><strong>Memory</strong></strong></strong> tab.</p>
-
-<p>Set the low memory status using the radio buttons:</p>
-
-<ul>
- <li><strong><strong><strong>Hard-Warning</strong></strong></strong> (40 MB and under)</li>
- <li><strong><strong><strong>Soft-Warning</strong></strong></strong> (60 MB and under)</li>
- <li><strong><strong><strong>Normal</strong></strong></strong> (sufficient)</li>
-</ul>
+<p>To open the control panel:</p>
-<h3>Control Panel Features on Different Profiles</h3>
+<ol>
+ <li>Launch the emulator.</li>
+ <li>Click the <strong>Control Panel</strong> button, or right-click the emulator and select <strong>Control Panel</strong>.
-<p>The following table lists the control panel features and their availability on different profiles.</p>
+<p align="center"><img alt="Opening the control panel" src="../images/emulator_control_panel_open2.png" /></p>
+</li></ol>
-<p align="center" class="Table"><strong><strong><strong>Table: Control panel features</strong></strong></strong></p>
+<p>The following table lists the control panel features and their availability on different profiles. The instructions for using the features are described below the table.</p>
+<p align="center" class="Table"><strong>Table: Control panel features</strong></p>
<table>
<tbody>
<td colspan="2">Host Directory Sharing</td>
<td>Yes</td>
<td>Yes</td>
- <td>File transfer is possible through the host directory sharing feature without using the SDB utility.</td>
+ <td>You can transfer files through the host directory sharing feature without using the SDB utility.</td>
</tr>
<tr>
<td colspan="2">Battery</td>
<td>You can set the remote signal strength.</td>
</tr>
<tr>
- <td rowspan="6">Sensor</td>
- <td>3-Axis Sensor</td>
+ <td rowspan="7">Sensor</td>
+ <td>3-Axis</td>
<td>Yes</td>
<td>No</td>
- <td>You can inject user acceleration, magnetic, and gyroscope values.</td>
+ <td>You can simulate user acceleration, magnetic, and gyroscope values.</td>
</tr>
<tr>
<td>Light</td>
<td>Yes</td>
<td>No</td>
- <td>You can inject a lux value into the light sensor.</td>
+ <td>You can simulate a lux value for the light sensor.</td>
</tr>
<tr>
<td>Proximity</td>
<td>Yes</td>
<td>No</td>
- <td>You can inject the presence of nearby objects.</td>
+ <td>You can simulate the presence of nearby objects.</td>
</tr>
<tr>
<td>Pressure</td>
<td>Yes</td>
<td>No</td>
- <td>You can inject an hPa value into the pressure sensor.</td>
+ <td>You can simulate an hPa value for the pressure sensor.</td>
</tr>
<tr>
<td>Ultraviolet</td>
<td>Yes</td>
<td>No</td>
- <td>You can inject an ultraviolet index.</td>
+ <td>You can simulate an ultraviolet index value.</td>
</tr>
<tr>
<td>Heart Rate Monitor</td>
<td>Yes</td>
<td>No</td>
- <td>You can inject the heart rate and peek-to-peek time.</td>
+ <td>You can simulate the user heart rate and peak-to-peak time.</td>
+ </tr>
+ <tr>
+ <td>Pedometer</td>
+ <td>Yes</td>
+ <td>No</td>
+ <td>You can simulate user movement with the device.</td>
</tr>
<tr>
<td colspan="2">Earjack</td>
<td colspan="2">SD Card</td>
<td>Yes</td>
<td>No</td>
- <td>You can inject a 4, 8, 16, or 32G SD card.</td>
+ <td>You can simulate a 4G, 8G, 16G, or 32G SD card.</td>
</tr>
<tr>
+ <td colspan="2">NFC</td>
+ <td>Yes</td>
+ <td>No</td>
+ <td>You can simulate near-field communication (NFC) events.</td>
+ </tr>
+ <tr>
<td colspan="2">Location</td>
<td>Yes</td>
<td>No</td>
- <td>You can inject latitude and longitude values using a map, manually, or from a log file.</td>
+ <td>You can simulate latitude and longitude values using a map, manually, or from a log file.</td>
</tr>
<tr>
<td colspan="2">Telephony</td>
<td colspan="2">Memory</td>
<td>Yes</td>
<td>No</td>
- <td>You can set the low memory status.</td>
+ <td>You can set the memory status.</td>
</tr>
</tbody>
</table>
+<h3>Controlling the Network Setting</h3>
+<p>In the <strong>Network</strong> card, you can control the user network.</p>
+<p>To lose the network connection, set the <strong>Link Status</strong> switch off. To forward a remote or local port to an inside port of the emulator, enter values in the text boxes, and click <strong>Apply</strong>.</p>
+
+<p align="center"><strong>Figure: Network popup</strong></p>
+<p align="center"><img alt="Network popup" src="../images/emulator_control_panel_network.png" /></p>
+
+<h3>Mounting a Host Directory</h3>
+<p>In the <strong>HDS</strong> card, you can configure host directory sharing (HDS) to share resources and transfer files without using the SDB utility. The specified host directory is mounted to <code>/mnt/host</code>.</p>
+
+<p align="center"><strong>Figure: Host Directory Sharing popup</strong></p>
+<p align="center"><img alt="Host directory sharing popup" src="../images/emulator_control_panel_hds.png" /></p>
+
+<h3>Providing Device Data</h3>
+<p>The control panel can be used to simulate various device data:</p>
+<ul>
+<li>In the <strong>Battery</strong> card, you can set the battery level using the <strong>Level</strong> slider. You can also connect or disconnect a charger using the <strong>Charger</strong> switch.</li>
+<li>In the <strong>Ear Jack</strong> card, you can add or remove an earjack (headset) device. You can add a 3-wire or 4-wire device.</li>
+<li>In the <strong>USB</strong> card, you can connect or disconnect a USB device.</li>
+<li>In the <strong>RSSI</strong> card, you can set the RSSI (remote signal strength indicator) information level.</li>
+<li>In the <strong>SDCard</strong> card, you can attach or detach an SD card to or from the emulator at runtime. You can attach a <strong>4G</strong>, <strong>8G</strong>, <strong>16G</strong>, or <strong>32G</strong> SD card.
+
+<div class="note">
+ <strong>Note</strong>
+ The same SD card cannot be attached to multiple emulators at the same time.
+</div>
+</li>
+</ul>
+
+<p>Device information set using the control panel is reflected on the indicator bar of the emulator screen.</p>
+
+<h3>Providing Location Data</h3>
+<p>In the <strong>Location</strong> card, you can provide simulated responses to location data requests:</p>
+<ul>
+<li>Injecting map markers
+<p>In the <strong>Map Image</strong> section, right-click the desired map locations and click <strong>Inject Markers</strong> to send the location data to the emulator.</p></li>
+<li>Manually entering location coordinates
+<p>In the <strong>Manual</strong> section, enter the coordinates and click <strong>Inject Location</strong> to send the location data to the emulator. The range of the latitude, longitude, altitude, and horizontal accuracy is from -90 to 90, -180 to 180, -300 to 100000, and 0 to 100000, respectively.</p></li>
+<li>Loading a GPS log file
+<p>In the <strong>Log</strong> section, select a pre-logged GPS data file (in NMEA183 format) and click <strong>Inject Log</strong> to send the location data to the emulator.</p></li>
+</ul>
+
+<h3>Providing NFC Data</h3>
+<p>In the <strong>NFC</strong> card, you can test near-field communication (NFC) features.</p>
+<div class="note">
+ <strong>Note</strong>
+ The control panel only sends NFC-related events to the emulator. There is no actual information exchange between the control panel and emulator. Therefore, for information exchange features, such as writing information to an NFC tag, the emulator simply displays a success message.
+</div>
+<ul>
+<li>Creating NFC data exchange format (NDEF) messages
+<p>An NDEF message contains 1 or more NDEF records. In the <strong>NDEF Message</strong> section:</p>
+
+ <ol>
+ <li>Select the record type name format.</li>
+ <li>Enter the record type name, ID, and payload.</li>
+ <li>Click <strong>Add</strong>.</li>
+ </ol>
+
+<p>You can add multiple NDEF records in the NDEF message.</p>
+
+ <p>Click <strong>Edit</strong> or <strong>Remove</strong> to modify or delete a selected record.</p>
+ </li>
+ <li>Attaching and detaching NFC tags
+<p>In the <strong>NDEF Tag</strong> section:</p>
+ <ol>
+ <li>Select the tag type.</li>
+ <li>Click the switch to attach or detach the tag.
+<p>If the NDEF record list is not empty, an NDEF message is created using this list and the attach message is sent to the emulator with the NDEF message.</p></li>
+ </ol>
+ </li>
+<li>Creating a peer-to-peer (P2P) data connection
+<p>In the <strong>PEER TO PEER</strong> section:</p>
+ <ul>
+ <li>To inform the emulator that a new device has been discovered, click <strong>P2P Discovered</strong>.</li>
+ <li>To send the emulator an NDEF message, click <strong>P2P Send</strong>.</li>
+ <li>To inform the emulator that a connected device has been detached, click <strong>P2P Detached</strong>.</li>
+ </ul>
+ </li>
+</ul>
+
+<h3>Providing Sensor Data</h3>
+
+<p>In the control panel, you can model user actions, such as shaking, throwing, and tilting the device, for the emulator instance. In addition, you can simulate a single sensor event on the instance, or send sequences of 3-axis sensor events to the instance.</p>
+<ul><li>In the <strong>Sensor</strong> card, you can control the 3-axis sensors. The popup consists of 4 tabs, where you can adjust the acceleration, magnetic, and gyro sensors of the emulator instance. In the <strong>GUI</strong> tab, you can intuitively adjust various sensor data by using 3D graphics.
+<ul>
+ <li>GUI
+<p>In the <strong>GUI</strong> tab, you can select an active sensor and move the 3D model of the emulator instance with the 3 axis sliders or the direction buttons (<strong>Portrait</strong>, <strong>Landscape</strong>, <strong>Reverse Portrait</strong>, and <strong>Reverse Landscape</strong>). The instance monitor displays the acceleration, magnetic, and gyro values.</p>
+
+<p>To better control the movement, select the <strong>With axis</strong> check box to see the axes in the emulator image. You can also fix the Y or Z axis by selecting the <strong>X/Z</strong> or <strong>X/Y</strong> radio button, respectively. To change the emulator accelerator value in the direction of the movement, select the <strong>Move</strong> radio button.</p></li>
+ <li>Acceleration
+<p>In the <strong>Acceleration</strong> tab, you can control the acceleration of the instance along the coordinate axes. When the emulated device is stationary and vertical in portrait orientation, the acceleration value of the Y axis is 1 g (gravitational acceleration). You can control the acceleration 3-axis values from -2 g to 2 g, using the sliders.</p></li>
+ <li>Magnetic
+<p>In the <strong>Magnetic</strong> tab, you can control the magnetic field values of the instance along the coordinate axes. When the emulated device is stationary and vertical in portrait orientation, the Y axis is at true north and the magnetic field strength values are 1, 0, and -10 µT (microtesla). You can control the magnetic field 3-axis values from -2000 µT to 2000 µT, using the sliders.</p></li>
+ <li>Gyro
+<p>In the <strong>Gyro</strong> tab, you can control the gyro (rotation angle per second) of the instance along the coordinate axes. You can control the gyro 3-axis values from -573 degrees/s to 573 degrees/s, using the sliders.</p></li>
+</ul>
+<p>You can simulate a single event on the individual sensor, or use sensor data files to simulate sequences of events on the sensor. A sensor data file consists of predefined events. It is written in ASCII. By loading a data file in the <strong>Acceleration</strong>, <strong>Magnetic</strong>, or <strong>Gyro</strong> tab, you can play a sequence of predefined events. You can also add multiple data files to be played in sequence. The format of each line in the event file is:</p>
+
+ <pre class="prettyprint">
+timestamp, x, y, z
+</pre>
+
+<p>When you add the event files and click <strong>Start</strong>, the predefined events are simulated at their specified relative timestamp. The timestamp unit is 0.01 seconds. Some events can be discarded, if they exceed certain limits of performance, resource, or logic.</p></li>
+
+<li>In the <strong>Light</strong> card, you can simulate ambient light conditions using the <strong>Lux</strong> slider. The range of this value is from 0 Lux to 65635 Lux.
+<p>If automatic screen brightness is activated in the device settings, the display changes based on the simulated light value.</p></li>
+<li>In the <strong>Proximity</strong> card, you can set the proximity sensor state to <strong>Far</strong> or <strong>Near</strong>.</li>
+<li>In the <strong>Pressure</strong> card, you can control the pressure sensor using the <strong>hPa</strong> slider. The range of this value is from 260 hPa to 1260 hPa (Hectopascals).</li>
+<li>In the <strong>Ultraviolet</strong> card, you can control the ultraviolet sensor using the <strong>Index</strong> slider. The unit is UV index and the range of this value is from 0 to 15.0.</li>
+<li>In the <strong>Heart Rate</strong> card, you can control the HRM (Heart Rate Monitor) sensor. You can use the <strong>bpm</strong> slider to set the heart rate value between 0 and 220 bpm, and the <strong>ms</strong> slider to set the peak-to-peak time between 0 and 5000 ms (milliseconds).</li>
+<li>In the <strong>Pedometer</strong> card, you can simulate user movement with the device by selecting a movement pace:<ul>
+ <li><strong>Stop</strong></li>
+ <li><strong>Walk Slowly</strong></li>
+ <li><strong>Walk</strong></li>
+ <li><strong>Run Slowly</strong></li>
+ <li><strong>Run</strong></li>
+ </ul>
+</li>
+</ul>
+
+<h3>Providing Telephony Features</h3>
+
+<p>In the <strong>Telephony</strong> card, you can generate incoming calls and messages:</p>
+
+<ul>
+ <li>Generating incoming calls
+ <p>Incoming calls are generated in the <strong>Call</strong> tab.</p>
+
+<div class="note">
+ <strong>Note</strong>
+ A Mobile Termination (MT) call is made from the Emulator Control Panel to the emulator. A Mobile Origination (MO) call is made from the emulator to the Emulator Control Panel using the emulator's phone application.
+</div>
+ <p>To make an MT call:</p>
+
+ <ol>
+ <li>In the <strong>MT Call</strong> section, enter the phone number you want to imitate the call from.</li>
+ <li>Click <strong>Connect</strong>.</li>
+ <li>To hide the phone number on the emulator, select the <strong>Hidden</strong> option.
+ <p>The caller ID on the emulator is set to "Unknown".</p></li>
+ </ol>
+
+ <p>To make an MO call:</p>
+ <ol>
+ <li>Call a phone number using the emulator's phone application.<p>In the <strong>MO Call</strong> section, you can see the call ID, number, and call type.</p></li>
+ <li>To disconnect the call, click <strong>Disconnect</strong>.</li>
+ </ol>
+ </li>
+ <li>Generating messages
+ <p>SMS messages are generated in the <strong>Messaging</strong> tab. After sending a message, your application waits for the asynchronous send status message. You can generate this status report for SMS messages using the same <strong>Messaging</strong> tab.</p>
+
+ <p>To generate an SMS message:</p>
+
+ <ol>
+ <li>Enter the sender phone number you want to imitate.</li>
+ <li>Enter the message body text and click <strong>Send Msg</strong>.</li>
+ </ol>
+ <p>To generate status reports, select the sending status value for the SMS message and click <strong>Set</strong>. The available values are:</p>
+ <ul>
+ <li><strong>SMS OK(Success)</strong></li>
+ <li><strong>SMS Not Available</strong></li>
+ </ul>
+
+ <p>You can also generate MMS message status reports. To generate MMS status reports, select the sending status value for the MMS message and click <strong>Set</strong>. The available values are:</p>
-<p> </p>
+ <ul>
+ <li><strong>MMS OK(Success)</strong></li>
+ <li><strong>MMS Failure</strong></li>
+ </ul>
+ </li>
+</ul>
+
+<h3>Providing Memory Data</h3>
+
+<p>In the <strong>Memory</strong> card, you can select a specific memory status using the radio buttons:</p>
+<ul>
+<li><strong>Hard Warning (40 MB and under)</strong></li>
+<li><strong>Soft Warning (60 MB and under)</strong></li>
+<li><strong>Normal (Sufficient)</strong></li>
+</ul>
<script type="text/javascript" src="../scripts/jquery.zclip.min.js"></script>
<title>Emulator Manager</title>
</head>
-<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
+<body onload="prettyPrint()" style="overflow: auto;">
<div id="toc-navigation">
+ <div id="toc_border"><div id="toc">
+ <p class="toc-title">Content</p>
+ <ul class="toc">
+ <li><a href="#access">Accessing the Emulator Manager</a></li>
+ <li><a href="#create">Creating an Emulator Instance</a></li>
+ <li><a href="#manage_launch_emus">Managing and Launching Emulator Instances</a></li>
+ </ul>
+ </div></div>
</div>
<div id="container"><div id="contents"><div class="content">
<h1>Emulator Manager</h1>
-<p>The Visual Studio Tools for Tizen provides emulators to run your application in a virtual environment.</p>
+<p>You can use emulators to run your application in a virtual environment.</p>
-<p>In order to test the application in a variety of environments, you need a variety of emulators. The Visual Studio Tools for Tizen provides the Emulator Manager to help you easily create and manage the emulator instances.</p>
-
-<p>Basically, the Emulator Manager allows you to easily generate emulator instances from a pre-defined platform and template. In addition, you can define the settings of the virtual device, such as skin, resolution, and hardware devices.</p>
+<p>In order to test the application in a variety of environments, you need a variety of emulators. The Emulator Manager helps you easily create and manage emulator instances. Basically, the Emulator Manager allows you to generate emulator instances from a predefined platform and template. In addition, you can define the settings of the virtual device, such as skin, resolution, and hardware devices.</p>
<p>The main features of the Emulator Manager are:</p>
-
<ul>
- <li>Creating a new emulator instance or hardware profile</li>
- <li>Managing an existing emulator instance or hardware profile</li>
- <li>Deleting an emulator instance or hardware profile</li>
- <li>Launching and stopping the emulator instance</li>
+<li>Defining a new emulator instance or hardware profile</li>
+<li>Editing an existing emulator instance or hardware profile</li>
+<li>Deleting an emulator instance or hardware profile</li>
+<li>Starting and stopping the emulator instance</li>
</ul>
<h2 id="access">Accessing the Emulator Manager</h2>
<p>If you do not have the Emulator Manager installed, you can install it using the Visual Studio Tools for Tizen installer.</p>
-
<p>There are 2 different ways to access the Emulator Manager from Visual Studio:</p>
<ul>
- <li>Go to <strong>Tools > Tizen,</strong> and select <strong>Tizen Emulator Manager</strong>.</li>
+ <li>In the Visual Studio menu, go to <strong>Tools > Tizen > Tizen Emulator Manager</strong>.</li>
</ul>
-<p align="center" class="figure"><strong><strong><strong>Figure: Launch </strong></strong>the Emulator Manager in the Tools menu</strong></p>
-
-<p align="center" class="figure"><img alt="" src="../images/vs_emulatormanager_1.png" /></p>
+<p align="center"><strong>Figure: Launch the Emulator Manager in the Tools menu</strong></p>
+<p align="center"><img alt="Launch from the Tools menu" src="../images/vs_emulatormanager_1.png" /></p>
<ul>
- <li>Click <strong>Launch Tizen Emulator</strong> on the Visual Studio toolbar.</li>
+ <li>On the Visual Studio toolbar, click <strong>Launch Tizen Emulator</strong>.</li>
</ul>
-
-<p align="center" class="figure"><strong>Figure: Launch the Emulator Manager in the Visual Studio</strong></p>
-
-<p align="center"><img alt="" src="../images/vs_emulatormanager_2.png" /></p>
+<p align="center"><strong>Figure: Launch the Emulator Manager in Visual Studio</strong></p>
+<p align="center"><img alt="Launch from the Visual Studio toolbar" src="../images/cs_launch_tizen_emu.png" /></p>
<h2 id="create">Creating an Emulator Instance</h2>
-<p>The Emulator Manager can help you to select the recommended platform and template. When you need another device environment, you can edit the existing emulator instance, or create a new one with a more suitable platform and template. You can also create platforms and templates to suit your needs.</p>
+<p>The Emulator Manager can help you to select the recommended platform and template. When you need another device environment, you can edit an existing emulator instance, or create a new one with a more suitable platform and template. You can also create new platforms and templates to suit your needs.</p>
-<p align="center" class="figure"><strong><strong>Figure: Emulator Manager</strong></strong></p>
-
-<p align="center"><strong><img alt="" src="../images/vs_em_1.png" /></strong></p>
+<p align="center"><strong>Figure: Emulator Manager</strong></p>
+<p align="center"><img alt="Emulator Manager" src="../images/vs_emulator_manager.png" /></p>
<p>To create a new emulator instance:</p>
<ol>
- <li>In the Emulator Manager, click <strong><strong>Create</strong></strong>.</li>
- <li>Select the platform (system image), and click <strong><strong>Next</strong></strong>.</li>
- <li>Select the template (device definition), and click <strong><strong>Next</strong></strong>.</li>
- <li>Change properties as needed, and click <strong><strong>Finish</strong></strong>.
+ <li>In the Emulator Manager, click <strong>Create</strong>.</li>
+ <li>Select the platform (system image), and click <strong>Next</strong>.</li>
+ <li>Select the template (device definition), and click <strong>Next</strong>.</li>
+ <li>Modify the properties as needed, and click <strong>Finish</strong>.
<p>The emulator instance appears in the Emulator Manager.</p>
+<p>To view the emulator instance details, right-click the instance and select <strong>Detail</strong>.</p>
- <p>To view the detailed information, right-click the emulator to see a context menu.</p>
-
- <div class="note"><strong><strong>Note</strong></strong>
-
- <p>To run the application faster, switch on CPU VT and GPU. If CPU VT is disabled, check <a href="../../../org.tizen.studio/html/common_tools/emulator.htm#speed"><u><font color="#000080">Increasing the Application Execution Speed</font></u></a> for more information. If GPU is disabled, <a href="../../../org.tizen.studio/html/download/prerequisites.htm#emulator"><u><font color="#000080">install the latest vendor-provided graphic driver</font></u></a>.</p>
+ <div class="note"><strong>Note</strong>
+ To run the application faster, switch on CPU VT and GPU. If CPU VT is disabled, check <a href="../../../org.tizen.studio/html/common_tools/emulator.htm#speed">Increasing the Application Execution Speed</a> for more information. If GPU is disabled, <a href="../../../org.tizen.studio/html/download/prerequisites.htm#emulator">install the latest vendor-provided graphic driver</a>.
- <p>Mobile emulator supports HD(720x1280) or WVGA(480x800) resolutions.</p>
+ <p>The mobile emulator supports HD (720x1280) and WVGA (480x800) resolutions.</p>
</div>
</li>
</ol>
-<p align="center" class="figure"><strong><strong>Figure: Emulator Configuration dialog</strong></strong></p>
-
-<p align="center"><strong><img alt="" src="../images/vs_em_2.png" /></strong></p>
-
<h3>Creating Platforms</h3>
-<p>To create an emulator, you have to first select the platform. You can create, modify, and delete a custom platform, and view the generated platforms. Most application developers do not need a custom platform, but it can be useful for a platform developer.</p>
-
-<p align="center" class="figure"><strong><strong>Figure: Platforms list</strong></strong></p>
-
-<p align="center"><img alt="" src="../images/vs_em_2.png" /></p>
+<p>To create an emulator, you must first select the platform. You can create, modify, and delete a custom platform, and view the generated platforms. Most application developers do not need a custom platform, but it can be useful for a platform developer.</p>
+<p align="center"><strong>Figure: Platform list</strong></p>
+<p align="center"><img alt="Platform list" src="../images/vs_emulator_manager_config.png" /></p>
<p>To create a custom platform:</p>
<ol>
- <li>Click the create icon (<img alt="Create icon" src="../images/emulator_manager_create.png" />).</li>
- <li>In the dialog box, select a base platform and platform image file.
- <p>You can create a custom platform using a qcow2 or raw format image.</p>
-
- <p>Qcow2 is a platform image format that is released with the Tizen Studio. Using the Emulator Manager's "Export as" feature, you can also create a qcow2 image.</p>
+ <li>In the Emulator Manager, click <strong>Create</strong>.</li>
+ <li>Click <strong>+</strong>.</li>
+ <li>In the <strong>Platform Configuration</strong> dialog, select a base platform and platform image file.
+ <p>You can create a custom platform using a qcow2 or raw format image. Qcow2 is a platform image format that is released with the Tizen Studio. You can also create a qcow2 image by <a href="#export">exporting an emulator</a>.</p>
- <p>A platform image of the development stage is in the raw format. If you try launching an emulator with a raw image, you can see the current state of this image. This can be useful for platform developers.</p>
+ <p>A platform image in the development stage is in raw format. If you launch an emulator with a raw image, you can see the current state of the image. This can be useful for platform developers.</p>
</li>
- <li>Click <strong><strong>OK</strong></strong> to save your configuration and click <strong><strong>Next</strong></strong>.
- <p>The newly created platform is added to the list with a settings icon.</p>
+ <li>Click <strong>OK</strong> to save your configuration.
+ <p>The new platform is added to the list.</p>
</li>
</ol>
-<p align="center" class="figure"><strong><strong>Figure: Platform configuration</strong></strong></p>
-
-<p align="center"><strong><img alt="" src="../images/vs_em_4.png" /></strong></p>
-
-<h3>Creating Templates</h3>
-
-<p>The Emulator Manager provides several device template types. A device template refers to, for example, the screen resolution and size, and the sensors in the device specification. You can make an emulator instanced based on the desired template.</p>
-
-<p align="center" class="figure"><strong><strong>Figure: Device templates</strong></strong></p>
-
-<p align="center"><strong><img alt="Device templates" src="../images/emulator_manager_device_template2.png" /></strong></p>
-
-<p>You can create a new template from the beginning, or clone a template and change some properties.</p>
-
-<ul>
- <li>To create a new template, click the create icon (<img alt="Create icon" src="../images/emulator_manager_create.png" />) to open a dialog box. Click <strong><strong>OK</strong></strong> to save your settings.</li>
- <li>To clone a new template, click the clone icon (<img alt="Clone icon" src="../images/emulator_manager_clone.png" />), make the appropriate changes, and click <strong><strong>OK</strong></strong> .</li>
-</ul>
-
-<p>After configuring the template, click <strong><strong>Next</strong></strong>. The new device template is added to the list with a settings icon.</p>
-
-<p align="center" class="figure"><strong><strong>Figure: Template configuration</strong></strong></p>
-
-<p align="center"><strong><img alt="Template configuration" src="../images/emulator_manager_template_config2.png" /></strong></p>
-
-<h2 id="manage">Managing the Emulator</h2>
-
-<p>In the Emulator Manager, you can edit, delete, reset, and export emulator instances:</p>
-
-<ul>
- <li>To edit an emulator instance, click <strong><strong>Edit</strong></strong>, make the appropriate changes, and click <strong><strong>Confirm</strong></strong>.</li>
- <li>To delete an emulator instance, click <strong><strong>Delete</strong></strong>.</li>
- <li>To reset an emulator instance, right-click it and select <strong><strong>Reset</strong></strong>.</li>
- <li>To export an emulator instance, right-click it and select <strong><strong>Export As</strong></strong>. Specify the new image file location.
- <p>When you export the emulator instance, the same state as in the platform image is replicated.</p>
- </li>
-</ul>
+<p align="center"><strong>Figure: Platform Configuration dialog</strong></p>
+<p align="center"><img alt="Platform Configuration dialog" src="../images/vs_emulator_manager_platform_config.png" /></p>
-<h2 id="platform">Managing Platforms and Templates</h2>
-
-<p>To manage the template:</p>
+<p>To manage the created platforms:</p>
<ul>
- <li>To modify a template, click the modify icon (<img alt="Modify icon" src="../images/emulator_manager_modify.png" />), make the appropriate changes, and click <strong><strong>Confirm</strong></strong>. You can only modify the custom device templates you have created.</li>
- <li>To delete a template, click the delete icon (<img alt="Delete icon" src="../images/emulator_manager_delete.png" />). You can only delete the custom device templates you have created.</li>
+ <li>To edit a platform, click <strong>Edit</strong> (<img alt="Edit platform" src="../images/vs_emulator_manager_modify.png" />), make the desired changes, and click <strong>OK</strong>. You can only edit the custom platforms you have created.</li>
+ <li>To delete a platform, click <strong>Delete</strong> (<img alt="Delete" src="../images/vs_emulator_manager_delete.png" />). You can only delete the custom platforms you have created.</li>
</ul>
-<p>To manage the platforms:</p>
-
-<ul>
- <li>To modify a custom platform, click the modify icon (<img alt="Modify icon" src="../images/emulator_manager_modify.png" />), make the appropriate changes, and click <strong><strong>Confirm</strong></strong>. You can only modify the custom platforms you have created.</li>
- <li>To delete a custom platform, click the delete icon (<img alt="Delete icon" src="../images/emulator_manager_delete.png" />). You can only delete the custom platforms you have created.</li>
-</ul>
+<h3>Creating Templates</h3>
-<h2 align="left">Launching an Emulator Instance</h2>
+<p>The Emulator Manager provides several device template types. A device template defines, for example, the screen resolution and size, and the sensors in the device specification. You can make an emulator instance based on the desired template.</p>
-<p align="left">To launch an emulator instance:</p>
+<p align="center"><strong>Figure: Device templates</strong></p>
-<ul>
- <li>Launch the Emulator Manager and select an emulator instance on the list.</li>
- <li>Click <strong>Launch</strong>.</li>
-</ul>
+<p align="center"><img alt="Device templates" src="../images/vs_emulator_manager_device_template2.png" /></p>
-<p align="center"><strong>Figure: Launch an emulator instance</strong></p>
+<p>You can create a custom template in 2 ways:</p>
-<p align="center"><strong><img alt="" height="632" src="../images/vs_em_launch.png" width="645" /></strong></p>
+<ol>
+ <li>In the Emulator Manager, click <strong>Create</strong>.</li>
+ <li>Select a platform and click <strong>Next</strong>.</li>
+
+ <li>To create a new template:
+ <ul>
+ <li>To create a new template from the beginning:
+ <ol type="a"><li>Click <strong>+</strong>.</li>
+ <li>Define the features for the template.</li>
+ <li>Click <strong>OK</strong>.
+ <p>The new template is added to the list with a settings icon.</p></li>
+ </ol></li>
+ <li>To create a new template based on an existing one:
+ <ol type="a"><li>Select the template you want to clone.</li>
+ <li>Click <strong>clone template</strong> (<img alt="Clone icon" src="../images/vs_emulator_manager_clone.png" />).</li>
+ <li>Make the desired changes.</li>
+ <li>Click <strong>OK</strong>.
+ <p>The new template is added to the list with a settings icon.</p></li>
+ </ol></li>
+ </ul>
+</li></ol>
+<p align="center"><strong>Figure: Template Configuration dialog</strong></p>
+<p align="center"><img alt="Template Configuration dialog" src="../images/vs_emulator_manager_template_config2.png" /></p>
+
+<p>To manage the created templates:</p>
<ul>
- <li>The selected emulator is booted after a few seconds.</li>
+ <li>To edit a template, click <strong>edit template</strong> (<img alt="Edit template" src="../images/vs_emulator_manager_modify.png" />), make the desired changes, and click <strong>OK</strong>. You can only edit the custom templates you have created.</li>
+ <li>To delete a template, click <strong>delete</strong> (<img alt="Delete" src="../images/vs_emulator_manager_delete.png" />). You can only delete the custom templates you have created.</li>
</ul>
-<p align="center"><strong>Figure: Launched emulator instance</strong></p>
+<h2 id="manage_launch_emus">Managing and Launching Emulator Instances</h2>
-<p align="center"><img alt="" src="../images/vs_em_launched.png" /></p>
+<p>In the Emulator Manager, you can launch, edit, delete, reset, and export emulator instances:</p>
+<ol>
+ <li>Launch the Emulator Manager.</li>
+ <li>Select an emulator instance from the list.</li>
+ <li>Manage the instance:
<ul>
- <li>The debug and launch options are activated after the emulator has booted. The name of the emulator instance is displayed on the toolbar.</li>
+<li>To launch the emulator, click <strong>Launch</strong>.
+<p>The debug and launch options are activated after the emulator has booted. The name of the emulator instance is displayed on the Visual Studio toolbar.</p>
+<p align="center"><img alt="Emulator instance on Visual Studio toolbar" src="../images/vs_emulator_activated_debug.png" /></p></li>
+<li>To edit an emulator, click <strong>Edit</strong>, make the desired changes, and click <strong>Confirm</strong>.</li>
+<li>To delete an emulator, click <strong>Delete</strong>.</li>
+<li>To reset an emulator, right-click it and select <strong>Reset</strong>.</li>
+<li id="export">To export an emulator, right-click it and select <strong>Export as</strong>. Specify the new image file location.
+ <p>When you export the emulator instance, the state of the platform image is replicated.</p></li>
</ul>
-
-<p align="center"><strong>Figure: Activated debug option</strong></p>
-
-<p align="center"><img alt="" src="../images/vs_em_activated_debug.png" /></p>
-
-<h2 id="control"> </h2>
-
-
+</li>
+</ol>
<script type="text/javascript" src="../scripts/jquery.zclip.min.js"></script>
<script type="text/javascript" src="../scripts/showhide.js"></script>
<title>Log Viewer</title>
</head>
-<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
+<body onload="prettyPrint()" style="overflow: auto;">
<div id="toc-navigation">
+<div id="toc_border"><div id="toc">
+ <p class="toc-title">Content</p>
+ <ul class="toc">
+ <li><a href="#create_log_msgs">Creating Log Messages</a></li>
+ <li><a href="#launch">Launching the Log Viewer</a></li>
+ <li><a href="#filter">Understanding and Filtering Logs</a></li>
+ </ul>
+ </div></div>
</div>
<div id="container"><div id="contents"><div class="content">
<h1>Log Viewer</h1>
-<p>This topic explains how to insert logging methods to your code and check the logs of your application in the <span>Log Viewer</span>.</p>
+<p>You can debug your application by inserting logging methods to your application code, running the application, and checking the application logs in the Log Viewer tool.</p>
-<h2 id="view">Viewing Logs in Log Tabs</h2>
+<p>The Log Viewer helps you debug your application by capturing all the events logged by the platform and your application. The Log Viewer shows the logs through the <a href="../../../org.tizen.guides/html/native/error/system_logs_n.htm">dlog logging service</a>. The service consists of the dlogutil and dlog library. You can also see logs with the <code>dlogutil</code> command in the CLI environment, and create log entries with the dlog library.</p>
-<p> If you want to open the <span>Log Viewer</span>, go to <span>Tools > Tizen > Tizen Log Viewer </span>in the Visual Studio menu.</p>
+<p align="center"><strong>Figure: Log Viewer</strong></p>
+<p align="center"><img alt="Log Viewer" src="../images/logviewer_keyword_filter.png" /></p>
-<p align="center" class="figure"><span>Figure: Log Viewer Menu</span></p>
+<p>The Log Viewer displays a log table consisting of the following fields:</p>
-<p align="center" class="figure"><span><img alt="" height="138" src="../images/logviewer_entry_point.png" width="631" /></span></p>
-
-<p align="center" class="figure"> </p>
-
-<p>The Log Viewer helps you debug your application by capturing all the events logged by the platform and your application. The Log Viewer shows the logs through the <a href="../../../org.tizen.guides/html/native/error/system_logs_n.htm">dlog logging service</a>. The service consists of the dlogutil and dlog library. You can also see logs with the <code>dlogutil</code> command in the CLI environment, and create log entries with the dlog library.</p>
-
-<p> </p>
+<ul>
+ <li><strong>Time</strong>: log time</li>
+ <li><strong>Level</strong>: priority level indicates the urgency of the log message</li>
+ <li><strong>Pid</strong>: process ID</li>
+ <li><strong>Tid</strong>: thread ID</li>
+ <li><strong>Tag</strong>: identification of the log message source</li>
+ <li><strong>Msg</strong>: log message</li>
+</ul>
-<p align="center" class="figure"><span>Figure: Log Viewer</span></p>
+<h2 id="create_log_msgs">Creating Log Messages</h2>
-<p align="center"><img alt="" height="539" src="../images/logviewer_default.png" width="700" /></p>
+<p>You can create a log message in your application with the dlog library. Before using the dlog library, make sure you know which priorities and tags to use and how to send the message to the log device. With appropriate properties and tags, it is easy to filter and check messages.</p>
-<h3>Creating a Log Message</h3>
+<p>For more information, see the <a href="../../../org.tizen.guides/html/native/error/system_logs_n.htm">System Logs</a> guide.</p>
-<p>You can create a log message in your application with the dlog library. Before using the dlog library, make sure you know which priorities and tags to use and how to send the message to the log device. With appropriate properties and tags, it is easy to filter and check the messages.</p>
+<h2 id="launch">Launching the Log Viewer</h2>
+<p>To launch the Log Viewer, in the Visual Studio menu, go to <strong>Tools > Tizen > Tizen Log Viewer</strong>.</p>
-<p>For more information, see the <a href="../../../org.tizen.guides/html/native/error/system_logs_n.htm">System Logs</a> guide.</p>
+<p align="center"><strong>Figure: Log Viewer launch</strong></p>
+<p align="center"><img alt="Log Viewer launch" src="../images/logviewer_entry_point.png" /></p>
<h2 id="filter">Understanding and Filtering Logs</h2>
-<p>The log table consists of the following fields:</p>
-
-<ul>
- <li><span>Time</span>: log time</li>
- <li><span>Level</span>: priority level indicates the urgency of the log message</li>
- <li><span>Pid</span>: process ID</li>
- <li><span>Tid</span>: thread ID</li>
- <li><span>Tag</span>: identification of the log message source</li>
- <li><span>Msg</span>: log message</li>
-</ul>
-
-<p align="center" class="figure"><span>Figure: Log table fields</span></p>
-
-<p align="center"><img alt="" height="150" src="../images/logviewer_keyword_filter.png" width="800" /></p>
<p>In the log table, you have the following options and functions:</p>
<ul>
<li>Log level filtering option
- <p>In the Log Viewer, you can filter the log messages using the <span>V</span> (verbose), <span>D</span> (debug), <span>I</span> (info), <span>W</span> (warning), <span>E</span> (error), and <span>F</span> (fatal) buttons to show specific log messages suitable to the selected type.</p>
+ <p>In the Log Viewer, you can filter the log messages using the <strong>V</strong> (verbose), <strong>D</strong> (debug), <strong>I</strong> (info), <strong>W</strong> (warning), <strong>E</strong> (error), and <strong>F</strong> (fatal) buttons to show the log messages matching the selected type.</p>
</li>
<li>Keyword filtering option
- <p>You can filter the log messages by selecting one of the <span>PID</span>, <span>Tag</span>, and <span>Message</span> options, or entering keywords in the bottom of the Log Viewer. The keywords must be separated by a space.</p>
+ <p>You can filter the log messages by selecting one of the <strong>PID</strong>, <strong>Tag</strong>, and <strong>Message</strong> options, or entering keywords in the bottom of the Log Viewer. The keywords must be separated by a space.</p>
</li>
<li>Scroll lock
- <p>The log table shows the latest logs by default. This can make you uncomfortable when checking the specified log. Enable scroll lock when checking a specified log.</p>
+<p>The log table shows the latest logs by default. While the application is running, the log table scrolls as new logs are added to the table. To stop the table from scrolling while you are checking a specific log, click the <strong>Scroll Lock</strong> button (<img alt="Scroll lock button" src="../images/logviewer_scroll_lock.png" />).</p>
</li>
<li>Clearing the table
- <p>You can remove all log messages from the log tab by clicking the Clear button.</p>
+ <p>You can remove all log messages from the log tab by clicking <strong>Clear</strong>.</p>
</li>
<li>Exporting logs to a file
- <p>You can export the current log messages in the Log Viewer and save them as a log file by clicking the Export button.</p>
+ <p>You can export the current log messages in the Log Viewer and save them as a log file by clicking <strong>Export</strong>.</p>
</li>
</ul>
<title>Tizen Manifest Editor</title>
</head>
-<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
+<body onload="prettyPrint()" style="overflow: auto;">
<div id="toc-navigation">
+ <div id="toc_border"><div id="toc">
+ <p class="toc-title">Content</p>
+ <ul class="toc">
+ <li><a href="#editing">Editing the Manifest File</a></li>
+ <li><a href="#hierarchy">Manifest Element Hierarchy</a></li>
+ <li><a href="#manifest">Manifest Elements</a></li>
+ </ul>
+ </div></div>
</div>
<div id="container"><div id="contents"><div class="content">
+
<h1>Tizen Manifest Editor</h1>
-<p>A Tizen .Net application project consists of exactly 1 manifest file, called <code>tizen-manifest.xml</code>, which is used to describe the application information. The manifest file is composed of XML elements, which include the root <a href="#manifest"><manifest></a> element and its child elements representing application information, such as <code><version></code>, and <code><privileges></code>. The <a href="#hierarchy">child elements are organized into a specific hierarchy</a>. The elements can have attributes associated with them, providing more information about the element.</p>
+<p>A Tizen .NET application project contains a manifest file, called <code>tizen-manifest.xml</code>, which is used to describe the application information. The manifest file is composed of XML elements, which include the root <a href="#manifest"><manifest></a> element and its child elements representing application information, such as <code><version></code>, and <code><privileges></code>. The <a href="#hierarchy">child elements are organized into a specific hierarchy</a>. The elements can have attributes associated with them, providing more information on the element.</p>
-<h2 id="editing" name="editing">Editing the Manifest File</h2>
+<h2 id="editing">Editing the Manifest File</h2>
-<p>There are 2 different ways to edit the <code>tizen-manifest.xml</code> file:</p>
+<p>There are 2 different ways to edit the <code>tizen-manifest.xml</code> file:</p>
<ul>
- <li>Use the text editor to modify the XML structure directly:
- <p align="center" class="figure"><span>Figure: Text Editor</span></p>
-
- <p align="center"><img alt="" height="294" src="../images/manifest_text_editor.png" width="958" /></p>
+ <li>Use the manifest editor to modify the manifest in a form editor:
+ <p>Double-click the <code>tizen-manifest.xml</code> file in the <strong>Solution Explorer</strong> view.</p>
+ <p align="center"><strong>Figure: Manifest editor</strong></p>
+ <p align="center"><img alt="Manifest editor" src="../images/vs_manifest_overview.png" /></p>
+ </li>
+ <li>Use the text editor to modify the XML structure directly:
<ol>
- <li>Right-click the <code>tizen-manifest.xml</code> file in the <span>Solution Explorer</span>.</li>
- <li>Select <span>Open with > XML (Text) Editor</span>.</li>
+ <li>Right-click the <code>tizen-manifest.xml</code> file in the <strong>Solution Explorer</strong> view.</li>
+ <li>Select <strong>Open with > XML (Text) Editor</strong>.</li>
</ol>
+ <p align="center"><strong>Figure: Text editor</strong></p>
+ <p align="center"><img alt="Text editor" src="../images/vs_manifest_text_editor.png" /></p>
</li>
- <li>Use the manifest editor to modify the manifest in a form editor:
- <p>Double-click the <code>tizen-manifest.xml</code> file in the <span>Solution Explorer</span>.</p>
- <p align="center" class="figure"><span>Figure: Manifest editor</span></p>
- </li>
</ul>
-<p align="center"><img alt="" height="692" src="../images/manifest_overview.png" width="739" /></p>
+<div class="note"><strong>Note</strong>
+The <code>tizen-manifest.xml</code> file must conform to both the standard XML file format and the Tizen .NET application specification requirements. Editing the manifest file XML structure with the text editor is intended for advanced users only. If the file does not conform to the standard and the requirements, errors can occur during installation.</div>
-<div class="note"><span><strong>Note</strong></span><br />
-The <code>tizen-manifest.xml</code> file must conform to both the standard XML file format and the Tizen .Net application specification requirements. Editing the manifest file XML structure with the text editor is intended for advanced users only. If the file does not conform to the standard and requirements, errors can occur during installation.</div>
+<h2 id="hierarchy">Manifest Element Hierarchy</h2>
-<h2 id="hierarchy" name="hierarchy">Manifest Element Hierarchy</h2>
+<p>The Tizen .NET application manifest file consists of XML elements organized in a hierarchy. The following tree structure shows the relationship between the elements of the <code>tizen-manifest.xml</code> file.</p>
-<p>The Tizen .Net application manifest file consists of XML elements organized in a hierarchy. The following tree structure shows the relationship between the elements of the <code>tizen-manifest.xml</code> file.</p>
-
-<table>
+<table style="border:none;">
<colgroup>
<col width="10%" />
<col width="10%" />
</colgroup>
<tbody>
<tr>
- <td colspan="7"><code><a href="#manifest_element"><manifest></a></code></td>
+ <td colspan="7"
style="border:none;"><code><a href="#manifest_element"><manifest></a></code></td>
</tr>
<tr>
- <td> </td>
- <td colspan="6"><code><a href="#author"><author></a></code></td>
+ <td style="border:none;"> </td>
+ <td colspan="6"
style="border:none;"><code><a href="#author"><author></a></code></td>
</tr>
<tr>
- <td> </td>
- <td colspan="6"><code><a href="#description"><description></a></code></td>
+ <td style="border:none;"> </td>
+ <td colspan="6"
style="border:none;"><code><a href="#description"><description></a></code></td>
</tr>
<tr>
- <td> </td>
- <td colspan="6"><code><a href="#profile_element"><profile></a></code></td>
+ <td style="border:none;"> </td>
+ <td colspan="6"
style="border:none;"><code><a href="#profile_element"><profile></a></code></td>
</tr>
<tr>
- <td> </td>
- <td colspan="6"><code><a href="#ui"><ui-application></a></code></td>
+ <td style="border:none;"> </td>
+ <td colspan="6"
style="border:none;"><code><a href="#ui"><ui-application></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td colspan="5"><code><a href="manifest_elements.htm#label"><label></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="5"
style="border:none;"><code><a href="manifest_elements.htm#label"><label></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td colspan="5"><code><a href="manifest_elements.htm#icon"><icon></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="5"
style="border:none;"><code><a href="manifest_elements.htm#icon"><icon></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td colspan="5"><code><a href="manifest_elements.htm#appcontrol"><app-control></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="5"
style="border:none;"><code><a href="manifest_elements.htm#appcontrol"><app-control></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td colspan="5"><code><a href="manifest_elements.htm#metadata"><metadata></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="5"
style="border:none;"><code><a href="manifest_elements.htm#metadata"><metadata></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td colspan="5"><code><a href="manifest_elements.htm#datacontrol"><datacontrol></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="5"
style="border:none;"><code><a href="manifest_elements.htm#datacontrol"><datacontrol></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td colspan="5"><code><a href="manifest_elements.htm#bg-category"><background-category></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="5"
style="border:none;"><code><a href="manifest_elements.htm#bg-category"><background-category></a></code></td>
</tr>
<tr>
- <td> </td>
- <td colspan="6"><code><a href="#shortcut-list"><shortcut-list></a></code></td>
+ <td style="border:none;"> </td>
+ <td colspan="6"
style="border:none;"><code><a href="#shortcut-list"><shortcut-list></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td colspan="5"><code><a href="#shortcut"><shortcut></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="5"
style="border:none;"><code><a href="#shortcut"><shortcut></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td> </td>
- <td colspan="4"><code><a href="manifest_elements.htm#icon"><icon></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="4"
style="border:none;"><code><a href="manifest_elements.htm#icon"><icon></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td> </td>
- <td colspan="4"><code><a href="manifest_elements.htm#label"><label></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="4"
style="border:none;"><code><a href="manifest_elements.htm#label"><label></a></code></td>
</tr>
<tr>
- <td> </td>
- <td colspan="6"><code><a href="#account"><account></a></code></td>
+ <td style="border:none;"> </td>
+ <td colspan="6"
style="border:none;"><code><a href="#account"><account></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td colspan="5"><code><a href="#accountprovider"><account-provider></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="5"
style="border:none;"><code><a href="#accountprovider"><account-provider></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td> </td>
- <td colspan="4"><code><a href="#icon"><icon></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="4"
style="border:none;"><code><a href="#icon"><icon></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td> </td>
- <td colspan="4"><code><a href="manifest_elements.htm#label"><label></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="4"
style="border:none;"><code><a href="manifest_elements.htm#label"><label></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td> </td>
- <td colspan="4"><code><a href="#capability"><capability></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="4"
style="border:none;"><code><a href="#capability"><capability></a></code></td>
</tr>
<tr>
- <td> </td>
- <td colspan="6"><code><a href="#privileges"><privileges></a></code></td>
+ <td style="border:none;"> </td>
+ <td colspan="6"
style="border:none;"><code><a href="#privileges"><privileges></a></code></td>
</tr>
<tr>
- <td> </td>
- <td> </td>
- <td colspan="5"><code><a href="#privilege"><privilege></a></code></td>
+ <td style="border:none;"> </td>
+ <td style="border:none;"> </td>
+ <td colspan="5"
style="border:none;"><code><a href="#privilege"><privilege></a></code></td>
</tr>
<tr>
- <td> </td>
- <td colspan="6"><code><a href="#feature"><feature></a></code></td>
+ <td style="border:none;"> </td>
+ <td colspan="6"
style="border:none;"><code><a href="#feature"><feature></a></code></td>
</tr>
</tbody>
</table>
-<h2 id="manifest" name="manifest">Manifest Elements</h2>
+<h2 id="manifest">Manifest Elements</h2>
-<p>The following sections summarize the elements used in the <code>tizen-manifest.xml</code> file of the .Net application.</p>
+<p>The following sections summarize the elements used in the <code>tizen-manifest.xml</code> file of a Tizen .NET application.</p>
<h3 id="manifest_element"><manifest> Element</h3>
-<p>This element contains the manifest information of the Tizen .Net application. The <code><manifest></code> element is an easily readable description of the Tizen package and serves as a container for the other elements of the configuration document.</p>
+<p>This element contains the manifest information for a Tizen .NET application. The <code><manifest></code> element is an easily-readable description of the Tizen package and serves as a container for the other elements of the configuration document.</p>
-<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>
</li>
</ul>
-<p><span>Expected children (in the following order):</span></p>
+<p><strong>Expected children (in the following order):</strong></p>
<table border="1">
<tbody>
</tbody>
</table>
-<p align="center" class="figure"><span>Figure: Editing the <manifest> element in the manifest editor</span></p>
+<p align="center"><strong>Figure: Editing the <manifest> element in the manifest editor</strong></p>
-<p align="center" class="figure"><img alt="" height="669" src="../images/manifest_editing.png" width="724" /></p>
+<p align="center"><img alt="Editing the manifest element in the manifest editor" src="../images/vs_manifest_editing.png" /></p>
-<p id="attributes"><span>Attributes:</span></p>
+<p id="attributes"><strong>Attributes:</strong></p>
<ul>
<li>
<p><code>api-version</code></p>
- <p>API version number for the application (available value: number in the "x.y.z" format, where z is optional, for example, <code>3.0</code>)</p>
+ <p>API version number for the application (available value: number in the "x.y.z" format, where z is optional, for example, <code>3.0</code>)</p>
</li>
<li>
<p><code>install-location</code></p>
- <p>Installation location for the application (available value: <code>"auto"</code>)</p>
+ <p>Installation location for the application (available value: <code>"auto"</code>)</p>
- <div class="note"><strong><span>Note</span></strong>This attribute is read-only. Do not attempt to modify it.</div>
+ <div class="note"><strong>Note</strong>This attribute is read-only. Do not attempt to modify it.</div>
</li>
<li>
<p><code>package</code></p>
- <p>Package of the application (available value: <code>"org.tizen.applicationName"</code>)</p>
+ <p>Package of the application (available value: <code>"org.tizen.<applicationName>"</code>)</p>
</li>
<li>
<p><code>type</code></p>
- <p>Package type of the application (available value: <code>"tpk"</code>)</p>
+ <p>Package type of the application (available value: <code>"tpk"</code>)</p>
- <div class="note"><strong><span>Note</span></strong>This attribute is read-only. Do not attempt to modify it.</div>
+ <div class="note"><strong>Note</strong>This attribute is read-only. Do not attempt to modify it.</div>
</li>
<li>
<p><code>version</code></p>
</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<manifest xmlns="http://tizen.org/ns/packages" api-version="3.0" package="org.tizen.uiapp" version="1.0.0">
- <author>.....</author>
- <description>.....</description>
- <profile name="mobile"/>
- <ui-application>.....</ui-application>
- <shortcut-list>.....</shortcut-list>
- <account>.....</account>
- <privileges>.....</privileges>
- <feature>.....</feature>
-</manifest></pre>
+ <author>.....</author>
+ <description>.....</description>
+ <profile name="common"/>
+ <ui-application>.....</ui-application>
+ <shortcut-list>.....</shortcut-list>
+ <account>.....</account>
+ <privileges>.....</privileges>
+ <feature>.....</feature>
+</manifest>
+</pre>
<h3 id="author"><author> Element</h3>
<p>This element represents the creator of the Tizen package.</p>
-<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>
</li>
</ul>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li>
</li>
</ul>
-<p><span>Expected value:</span></p>
+<p><strong>Expected value:</strong></p>
<ul>
<li>Package creator name in string</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
-<author email="email@email.com" href="http://test.com">author</author></pre>
+<author email="email@email.com" href="http://test.com">author</author>
+</pre>
<h3 id="description"><description> Element</h3>
<p>This element contains an easily readable description of the Tizen package.</p>
-<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 or more (optional)</li>
</ul>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li><code>xml:lang</code>
</li>
</ul>
-<p><span>Expected value:</span></p>
+<p><strong>Expected value:</strong></p>
<ul>
<li>Description value in string</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<description xml:lang="en-us">This is a sample</description>
<h3 id="profile_element"><profile> Element</h3>
-<p>In Tizen .Net application, the <code><profile></code> element set to common. This element has no child elements.</p>
+<p>In a Tizen .NET application, the <code><profile></code> element must be set to <code>common</code>. This element has no child elements.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1</li>
</ul>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li><code>name</code>
- <p>Profile name (available values: <code>common</code>, <code>mobile</code>, <code>tv</code>)</p>
+ <p>Profile name (available values: <code>common</code>, <code>mobile</code>, <code>tv</code>)</p>
</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<profile name="common"/>
<h3 id="ui"><ui-application> Element</h3>
-<p>This element contains the manifest information of a Tizen .Net UI application with a graphical user interface (GUI).</p>
+<p>This element contains the manifest information for a Tizen .NET UI application with a graphical user interface (GUI).</p>
-<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 or more (optional)</li>
</ul>
-<p><span>Expected children (in the following order):</span></p>
+<p><strong>Expected children (in the following order):</strong></p>
<table border="1">
<tbody>
</tbody>
</table>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li><code>appid</code>
<p>Application executable file path (string)</p>
</li>
<li><code>hw-acceleration</code>
- <p>Indicates the application hardware acceleration status (available values: not defined (depends on the system setting), <code>on</code> (use hardware acceleration), <code>off</code> (do not use hardware acceleration))</p>
+ <p>Indicates the application hardware acceleration status (available values: not defined (depends on the system setting), <code>on</code> (use hardware acceleration), <code>off</code> (do not use hardware acceleration))</p>
<p>By default, this value is not defined.</p>
</li>
<li id="launch_mode"><code>launch_mode</code>
- <p>Application launch mode (available values: <code>single</code> (launched as a main application), <code>group</code> (launched as a sub application), <code>caller</code> (caller application))</p>
+ <p>Application launch mode (available values: <code>single</code> (launched as a main application), <code>group</code> (launched as a sub application), <code>caller</code> (caller application))</p>
- <p>By default, this value is set to <code>single</code>.</p>
+ <p>By default, this value is set to <code>single</code>.</p>
</li>
<li><code>multiple</code>
- <p>Indicates whether the application can be launched as a multiple (available values: <code>true</code>, <code>false</code>)</p>
+ <p>Indicates whether the application can be launched as a multiple (available values: <code>true</code>, <code>false</code>)</p>
- <div class="note"><strong><span>Note</span></strong>This attribute is read-only. Do not attempt to modify it.</div>
+ <div class="note"><strong>Note</strong>This attribute is read-only. Do not attempt to modify it.</div>
</li>
<li><code>nodisplay</code>
- <p>Indicates whether the application is shown in the app-tray (available values: <code>true</code>, <code>false</code>)</p>
+ <p>Indicates whether the application is shown in the app tray (available values: <code>true</code>, <code>false</code>)</p>
</li>
<li><code>taskmanage</code>
- <p>Indicates whether the application is shown in the task manager (available values: <code>true</code>, <code>false</code>)</p>
+ <p>Indicates whether the application is shown in the task manager (available values: <code>true</code>, <code>false</code>)</p>
</li>
<li><code>type</code>
- <p>Tizen application type (available values: <code>dotnet</code>)</p>
+ <p>Tizen application type (available value: <code>dotnet</code>)</p>
- <div class="note"><strong><span>Note</span></strong>This attribute is read-only. Do not attempt to modify it.</div>
+ <div class="note"><strong>Note</strong>This attribute is read-only. Do not attempt to modify it.</div>
</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
-<ui-application appid="org.tizen.uiapp" exec="uiapp" hw-acceleration="on" launch_mode="single"
- multiple="false" nodisplay="false" taskmanage="true" type="dotnet">
- <label>uiapplication</label>
- <label xml:lang="en-gb">testlang</label>
- <icon>uiapp.png</icon>
- <app-control>
- <operation name="http://tizen.org/appcontrol/operation/dial"/>
- <mime name="application/vnd.ms-excel"/>
- </app-control>
- <metadata key="testkey" value="testvalue"/>
- <datacontrol access="ReadOnly"
- providerid="http://uiapp.com/datacontrol/provider/uiapp" type="Sql"/>
-</ui-application></pre>
+<ui-application appid="org.tizen.uiapp" exec="uiapp" hw-acceleration="on" launch_mode="single"
+ multiple="false" nodisplay="false" taskmanage="true" type="dotnet">
+ <label>uiapplication</label>
+ <label xml:lang="en-gb">testlang</label>
+ <icon>uiapp.png</icon>
+ <app-control>
+ <operation name="http://tizen.org/appcontrol/operation/dial"/>
+ <mime name="application/vnd.ms-excel"/>
+ </app-control>
+ <metadata key="testkey" value="testvalue"/>
+ <datacontrol access="ReadOnly"
+ providerid="http://uiapp.com/datacontrol/provider/uiapp" type="Sql"/>
+</ui-application>
+</pre>
<h3 id="shortcut-list"><shortcut-list> Element</h3>
<p>This element contains the shortcut template list used for adding a shortcut to the home screen.</p>
-<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 (optional)</li>
</ul>
-<p><span>Expected children:</span></p>
+<p><strong>Expected children:</strong></p>
<table border="1">
<tbody>
</tbody>
</table>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<shortcut-list>
- <shortcut>.....</shortcut>
+ <shortcut>.....</shortcut>
</shortcut-list>
</pre>
-<h3 id="shortcut"><shortcut> Element</h3>
+<h4 id="shortcut"><shortcut> Element</h4>
<p>This element contains the information that indicates the shortcut for the application on the home screen.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 (optional)</li>
</ul>
-<p><span>Expected children:</span></p>
+<p><strong>Expected children:</strong></p>
<table border="1">
<tbody>
</tbody>
</table>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li><code>appid</code>
<li><code>extra_data</code>
<p>Data for user content (string)</p>
- <p>Shortcut element property in the manifest file</p>
+ <p>Shortcut element property in the manifest file.</p>
</li>
<li><code>extra_key</code>
<p>Key for user content (string)</p>
- <p>Shortcut element property in the manifest file</p>
+ <p>Shortcut element property in the manifest file.</p>
</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<shortcut appid="org.example.shortcut" extra_data="data" extra_key="key">
- <icon>shortcut.png</icon>
- <label>shortcut</label>
- <label xml:lang="en-us">short</label>
+ <icon>shortcut.png</icon>
+ <label>shortcut</label>
+ <label xml:lang="en-us">short</label>
</shortcut>
</pre>
<h3 id="account"><account> Element</h3>
-<p>This element contains a set of user accounts and account provider-related information in the Tizen application.</p>
+<p>This element contains a set of user accounts and account provider-related information for a Tizen application.</p>
-<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 (optional)</li>
</ul>
-<p><span>Expected children:</span></p>
+<p><strong>Expected children:</strong></p>
<table border="1">
<tbody>
</tbody>
</table>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<account>
- <account-provider>.....</account-provider>
+ <account-provider>.....</account-provider>
</account>
</pre>
-<h3 id="accountprovider"><span><account-provider> Element</span></h3>
+<h4 id="accountprovider"><account-provider> Element</h4>
-<p>This element contains a specific service provider or user account protocol-related information.</p>
+<p>This element contains specific service provider or user account protocol-related information.</p>
-<p><span>Expected children:</span></p>
+<p><strong>Expected children:</strong></p>
<table border="1">
<tbody>
</tbody>
</table>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li><code>appid</code>
<p>This can be used for launching or terminating the application explicitly.</p>
</li>
<li><code>multiple-accounts-support</code>
- <p>Indicates whether multiple accounts are supported (available values: <code>true</code>, <code>false</code>)</p>
+ <p>Indicates whether multiple accounts are supported (available values: <code>true</code>, <code>false</code>)</p>
</li>
<li><code>providerid</code>
<p>ID of the account provider (string)</p>
</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<account-provider appid="org.tizen.uiapp" multiple-accounts-support="false" providerid="org.tizen.uiapp">
- <icon>.....</icon>
- <label>.....</label>
- <capability>.....</capability>
+ <icon>.....</icon>
+ <label>.....</label>
+ <capability>.....</capability>
</account-provider>
</pre>
-<h3 id="icon"><span><icon> Element</span></h3>
+<h4 id="icon"><icon> Element</h4>
-<p>This element contains the account provider icon image. Since the icons are used in the device under settings, the account icons are placed in a shared directory.</p>
+<p>This element contains the account provider icon image. Since the icons are used on the device under <strong>Settings > Accounts</strong>, place them in a shared directory.</p>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li><code>section</code>
- <p>Usage information of the icon image (available values: <code>account</code> (image size: 72 x 72 for density xhigh and 48 x 48 for density high), <code>account-small</code> (image size: 45 x 45 for density xhigh and 30 x 30 for density high))</p>
+ <p>Usage information for the icon image (available values: <code>account</code> (image size: 72 x 72 for density xhigh and 48 x 48 for density high), <code>account-small</code> (image size: 45 x 45 for density xhigh and 30 x 30 for density high))</p>
</li>
</ul>
-<p><span>Expected value:</span></p>
+<p><strong>Expected value:</strong></p>
<ul>
<li>Icon file name</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<icon section="account">uiapp.png</icon>
<icon section="account-small">uiapp.png</icon>
</pre>
-<h3 id="capability"><span><capability> Element</span></h3>
+<h4 id="capability"><capability> Element</h4>
-<p>This element contains the account provider capability. The capabilities are defined as <code>http://<VENDOR_INFORMATION>/account/capability/<NAME></code>.</p>
+<p>This element contains the account provider capability. The capabilities are defined as <code>http://<VENDOR_INFORMATION>/account/capability/<NAME></code>.</p>
-<p><span>Expected value:</span></p>
+<p><strong>Expected value:</strong></p>
<ul>
<li>IRI string</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<capability>http://tizen.org/account/capability/calendar</capability>
<h3 id="privileges"><privileges> Element</h3>
-<p>This element contains a set of required privileges for the Tizen application.</p>
+<p>This element contains the set of required privileges for a Tizen application.</p>
-<p>Applications that use sensitive APIs must declare the required privileges in the <code>tizen-manifest.xml</code> file.</p>
+<p>Applications that use sensitive APIs must declare the required privileges in the <code>tizen-manifest.xml</code> file.</p>
-<p>Click <span>Add </span>to open the <span>Add Privilege</span> dialog.</p>
+<p>Click <strong>Add</strong> to open the <strong>Privileges</strong> dialog.</p>
-<p align="center" class="figure"><span>Figure: Editing the <privileges> element in the manifest editor</span></p>
+<p align="center"><strong>Figure: Editing the <privileges> element in the manifest editor</strong></p>
-<p align="center" class="figure"><img alt="" height="700" src="../images/manifest_privileges.png" width="802" /></p>
+<p align="center"><img alt="" src="../images/vs_manifest_privileges.png" /></p>
-<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 (optional)</li>
</ul>
-<p><span>Expected children:</span></p>
+<p><strong>Expected children:</strong></p>
<table border="1">
<tbody>
</tbody>
</table>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<privileges>
- <privilege>.....</privilege>
+ <privilege>.....</privilege>
</privileges>
</pre>
-<h3 id="privilege"><span><privilege> Element</span></h3>
+<h4 id="privilege"><privilege> Element</h4>
-<p>This element contains the required privileges for the Tizen application.</p>
+<p>This element contains a required privilege for a Tizen application.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 or more (optional)</li>
</ul>
-<p><span>Expected value:</span></p>
+<p><strong>Expected value:</strong></p>
<p>Name (mandatory, the URI of the Device API privilege)</p>
<li><code>http://tizen.org/privilege/account.read</code></li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<privilege>http://tizen.org/privilege/application.admin</privilege>
<p>The element is used to define the hardware and software components for the Tizen application. In order to use or access an API that is specialized for each vendor or platform, the feature must be declared. This element has no child elements.</p>
-<p align="center" class="figure"><span>Figure: Editing the <feature> element in the manifest editor</span></p>
+<p align="center"><strong>Figure: Editing the <feature> element in the manifest editor</strong></p>
-<p align="center" class="figure"><img alt="" height="698" src="../images/manifest_features.png" width="840" /></p>
+<p align="center"><img alt="Editing the feature element in the manifest editor" src="../images/vs_manifest_features.png" /></p>
-<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 or more (optional)</li>
</ul>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
- <li><code>name</code> (mandatory, a feature key URI)
+ <li><code>name</code> (mandatory, a feature key URI)
- <p>Item name used in feature-based filtering in the Tizen Store, for example, <code>"http://tizen.org/feature/camera"</code>, <code>"http://tizen.org/feature/fmradio"</code></p>
+ <p>Item name used in feature-based filtering in the Tizen Store, for example, <code>"http://tizen.org/feature/camera"</code> or <code>"http://tizen.org/feature/fmradio"</code></p>
</li>
</ul>
-<p><span>Expected value:</span></p>
+<p><strong>Expected value:</strong></p>
<ul>
<li><code>true</code></li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<feature name="http://tizen.org/feature/camera">true</privilege>
-<feature name="http://tizen.org/feature/fmradio">true</privilege></pre>
-
-
-
+<feature name="http://tizen.org/feature/fmradio">true</privilege>
+</pre>
<script type="text/javascript" src="../scripts/jquery.zclip.min.js"></script>
<title>Using Additional Manifest Elements</title>
</head>
-<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
+<body onload="prettyPrint()" style="overflow: auto;">
<div id="toc-navigation">
+
+ <div id="toc_border"><div id="toc">
+ <p class="toc-title">Content</p>
+ <ul class="toc">
+ <li><a href="#appcontrol"><app-control> Element</a></li>
+ <li><a href="#bg-category"><background-category> Element</a></li>
+ <li><a href="#datacontrol"><datacontrol> Element</a></li>
+ <li><a href="#icon"><icon> Element</a></li>
+ <li><a href="#label"><label> Element</a></li>
+ <li><a href="#metadata"><metadata> Element</a></li>
+ </ul>
+ </div></div>
</div>
<div id="container"><div id="contents"><div class="content">
<h1>Using Additional Manifest Elements</h1>
-<p>The following sections summarize some of the common child elements used in the <code>tizen-manifest.xml</code> file of the .Net application.</p>
+<p>The following sections summarize some of the common child elements used in the <code>tizen-manifest.xml</code> file of a Tizen .NET application.</p>
-<h2 id="appcontrol" name="appcontrol"><app-control> Element</h2>
+<h2 id="appcontrol"><app-control> Element</h2>
<p>This element represents Tizen application control configuration information.</p>
-<p>For more information on the relationship between the elements, see the
<a href="manifest_editor.htm#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="manifest_editor.htm#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 or more (optional)</li>
</ul>
-<p><span>Expected children:</span></p>
+<p><strong>Expected children:</strong></p>
<table border="1" id="feature">
<tbody>
</tbody>
</table>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<app-control>
- <operation name="http://tizen.org/appcontrol/operation/compose"/>
- <uri name="testuristring"/>
- <mime name="application/pdf"/>
+ <operation name="http://tizen.org/appcontrol/operation/compose"/>
+ <uri name="testuristring"/>
+ <mime name="application/pdf"/>
</app-control>
</pre>
<p>This element represents the operation type of the application control.</p>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li><code>name</code>
- <p>Name of the application control, for example, <code>http://tizen.org/appcontrol/operation/compose</code></p>
+ <p>Name of the application control, for example, <code>http://tizen.org/appcontrol/operation/compose</code></p>
</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<operation name="http://tizen.org/appcontrol/operation/compose"/>
<p>This element represents the URI scheme of the application control.</p>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li><code>name</code>
</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<uri name="testuristring"/>
<p>This element represents the MIME type of the application control.</p>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li><code>name</code>
</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<mime name="application/pdf"/>
</pre>
-<h2 id="bg-category" name="bg-category"><background-category> Element</h2>
+<h2 id="bg-category"><background-category> Element</h2>
-<p>This element represents the category of the application running on the background.</p>
+<p>This element represents the category of an application that runs in the background.</p>
-<p>For more information on the relationship between the elements, see the
<a href="manifest_editor.htm#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="manifest_editor.htm#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 or more (optional)</li>
</ul>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li><code>value</code>
</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<background-category value="download"/>
</pre>
-<h2 id="datacontrol" name="datacontrol"><datacontrol> Element</h2>
+<h2 id="datacontrol"><datacontrol> Element</h2>
<p>This element represents configuration information for the Tizen data controls.</p>
-<p>For more information on the relationship between the elements, see the
<a href="manifest_editor.htm#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="manifest_editor.htm#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 or more (optional)</li>
</ul>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li><code>access</code>
</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<datacontrol access="WriteOnly" providerid="http://uiapp.com/datacontrol/provider/uiapp" type="Sql"/>
</pre>
-<h2 id="icon" name="icon"><icon> Element</h2>
+<h2 id="icon"><icon> Element</h2>
<p>This element represents the icon relative or absolute file path for the Tizen application.</p>
-<p>For more information on the relationship between the elements, see the
<a href="manifest_editor.htm#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="manifest_editor.htm#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 (optional)</li>
</ul>
-<p><span>Expected value:</span></p>
+<p><strong>Expected value:</strong></p>
<ul>
<li>Icon path</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<icon>testicon.png</icon>
</pre>
-<h2 id="label" name="label"><label> Element</h2>
+<h2 id="label"><label> Element</h2>
<p>This element represents the label value for the Tizen application. It is a set of human readable names for the Tizen application according to the language.</p>
-<p>For more information on the relationship between the elements, see the
<a href="manifest_editor.htm#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="manifest_editor.htm#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 or more (optional)</li>
</ul>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li><code>xml:lang</code>
</li>
</ul>
-<p><span>Expected value:</span></p>
+<p><strong>Expected value:</strong></p>
<ul>
<li>Label value in string</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
<label>testlabel</label>
<label xml:lang="en-gb">testlabel</label>
</pre>
-<h2 id="metadata" name="metadata"><metadata> Element</h2>
+<h2 id="metadata"><metadata> Element</h2>
<p>This element represents user-defined key-value pairs for the application.</p>
-<p>For more information on the relationship between the elements, see the
<a href="manifest_editor.htm#hierarchy">element hierarchy</a>.</p>
+<p>For more information on the relationship between the elements, see the
<a href="manifest_editor.htm#hierarchy">element hierarchy</a>.</p>
-<p><span>Occurrences:</span></p>
+<p><strong>Occurrences:</strong></p>
<ul>
<li>1 or more (optional)</li>
</ul>
-<p><span>Attributes:</span></p>
+<p><strong>Attributes:</strong></p>
<ul>
<li><code>key</code>
</li>
</ul>
-<p><span>For example:</span></p>
+<p><strong>For example:</strong></p>
<pre class="prettyprint">
-<metadata key="testkey" value="testvalue"/></pre>
+<metadata key="testkey" value="testvalue"/>
+</pre>
<script type="text/javascript" src="../scripts/jquery.zclip.min.js"></script>
<title>Project Wizard</title>
</head>
-<body onload="prettyPrint()" style="overflow: auto;">
+<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
<div id="toc-navigation">
-<div id="toc_border">
-<div id="toc">
-<p class="toc-title">Content</p>
-
-<ul class="toc">
- <li><a href="#template">Template</a></li>
- <li><a href="#profile">Profile</a></li>
-</ul>
-</div>
-</div>
</div>
<div id="container"><div id="contents"><div class="content">
<h1>Project Wizard</h1>
-<p align="left">The Project Wizard of Visual Studio Tools for Tizen is a tool that is used to create a Tizen .Net application project.</p>
-
-<p align="left">The Visual Studio Tools for Tizen provides 3 project templates. When you create a new project, you can select a specific template, which the Project Wizard uses to automatically create basic functionalities for the application. The default project files and folders are also created.</p>
-
-<p align="left">In the Project Wizard, you can select a templates and profile to create the project. In addition, you can set basic project properties, such as the project name, package name and location.</p>
+<p>The Project Wizard in Visual Studio Tools for Tizen is used to create a Tizen .NET application project.</p>
-<p align="left">To open the Project Wizard, select <strong>File > New > Project > Templates > Visual C# > Tizen</strong>.</p>
+<p>In the Project Wizard, you can select a template and profile to create the project. In addition, you can set basic project properties, such as the project name, package name, and location.</p>
-<h2 align="left" id="template">Template</h2>
-
-<p align="left">You can select a template for your project. The Project Wizard creates the project based on the selected template.</p>
-
-<p align="center"><strong>Figure: Selecting the template</strong></p>
-
-<p align="center"><img alt="" height="653" src="../images/pw1.png" width="941" /></p>
-
-<p align="left">Visual Studio Tools for Tizen provides 3 templates with a basic structure where you can start the native application project:</p>
+<p>The Project Wizard provides 3 project templates:</p>
<ul>
- <li><strong>Blank App (Tizen Xamarin.Forms Portable)</strong>
-
- <ul>
- <li>Use this template for creating a Tizen Xamarin Application (mobile and TV)</li>
- <li>Also use this template in case of adding Tizen Project to Xamarin Forms solution.</li>
- </ul>
- </li>
- <li><strong>Blank App (Tizen Xamarin.Forms Single)</strong>
- <ul>
- <li>Use this for creating a Tizen Xamarin Application in a single project without PCL (Portable Class Library).</li>
- </ul>
- </li>
- <li><strong>Class Library (Tizen)</strong>
- <ul>
- <li>Use this for creating a blank class library.</li>
- </ul>
- </li>
+<li><strong>Blank App (Tizen Xamarin.Forms Portable):</strong> Template project for creating a Tizen Xamarin Application (for mobile and TV devices). Also use this template for adding a Tizen project to a Xamarin.Forms solution.</li>
+<li><strong>Blank App (Tizen Xamarin.Forms Single):</strong> Template project for creating a Tizen Xamarin Application in a single project without PCL (Portable Class Library).</li>
+<li><strong>Class Library (Tizen):</strong> Template project for creating a blank class library.</li>
</ul>
-<p align="left">After selecting a template and setting the location in your local repository, Click <strong>OK</strong>.</p>
-
-<h2 align="left" id="profile">Profile</h2>
-
-<p align="left">In case of Blank App (Tizen Xamarin.Forms Portable), the Tizen Project Wizard is shown for setting the project name and selecting the profile that you want to add in your solution.</p>
-
-<p align="center"><strong>Figure: Selecting the profile</strong></p>
+<p>When you create a new project with a specific template, the Project Wizard automatically creates basic functionalities for the application based on the template. The default project files and folders are also created.</p>
-<p align="center"><img alt="" height="300" src="../images/pw2.png" width="700" /></p>
-
-<p align="left">To move to the next step, select the profile, and click <strong>OK</strong>.</p>
-
-<p>The solution illustrated in the following figure contains both profiles (mobile and TV).</p>
-
-<p align="center"><strong>Figure: Solution containing mobile and TV profiles</strong></p>
-
-<p align="center"><img alt="" height="537" src="../images/vstools_solution.png" width="341" /></p>
+<p>To create a Tizen .NET application project:</p>
+<ol>
+ <li>To open the Project Wizard:
+ <ol type="a">
+ <li>In the Visual Studio menu, go to <strong>File > New > Project > Templates > Visual C# > Tizen</strong>.</li>
+ <li>Select a template for your project.
+ <p>The Project Wizard creates the project based on the selected template.</p></li>
+ <li>Set the basic project properties, such as the project name and its location in your local repository, and click <strong>OK</strong>.</li>
+ </ol>
+ <p align="center"><img alt="Selecting the template" src="../images/vs_project_wizard_template.png" /></p>
+ </li>
+ <li>If you selected the <strong>Blank App (Tizen Xamarin.Forms Portable)</strong> template, the Tizen Project Wizard dialog opens.
+ <p>Define the package name, select the profiles that you want to add to your solution, and click <strong>OK</strong>.</p>
+ <p align="center"><img alt="Tizen Project Wizard dialog" src="../images/vs_project_wizard_properties.png" /></p></li>
+</ol>
+
+<p>The following figure shows a new .NET application project solution that contains both mobile and TV profiles.</p>
+<p align="center"><strong>Figure: Solution with mobile and TV profiles</strong></p>
+<p align="center"><img alt="Solution with mobile and TV profiles" src="../images/vstools_solution.png" /></p>
<script type="text/javascript" src="../scripts/jquery.zclip.min.js"></script>
<script type="text/javascript" src="../scripts/showhide.js"></script>
<script type="text/javascript" src="../scripts/common.js" charset="utf-8"></script>
<script type="text/javascript" src="../scripts/core.js" charset="utf-8"></script>
<script type="text/javascript" src="../scripts/search.js" charset="utf-8"></script>
- <title>Overview</title>
+ <title>Visual Studio Tools for Tizen</title>
</head>
<body class="no-toc" onload="prettyPrint()" style="overflow: auto;">
<div id="container"><div id="contents"><div class="content">
- <h1>Overview</h1>
-
-<p>Visual Studio Tools for Tizen Preview provides <span>Tizen-specific tools to improve your productivity:</span></p>
+ <h1>Visual Studio Tools for Tizen</h1>
+<p>Visual Studio Tools for Tizen Preview provides Tizen-specific tools to improve your productivity:</p>
<ul>
- <li><strong><a href="../tools/project_wizard.htm">Project Wizard</a></strong><br />
- <span>The Project Wizard is a tool that is used to create a Tizen .NET application project.</span></li>
- <li><strong><a href="../tools/certificate_manager.htm">Certificate Registration</a></strong><br />
- The certificates can be created, edited, removed, and set as active in the Certificate Manager. The active certificates are used when packaging your application.</li>
- <li><strong><a href="../tools/manifest_editor.htm">Tizen Manifest Editor</a></strong><br />
- The Tizen Manifest Editor is a tool that is used to edit Tizen <span>manifest file, called </span><code class="prettyprint"><span class="pln">tizen</span><span class="pun">-</span><span class="pln">manifest</span><span class="pun">.</span><span class="pln">xml</span></code><span>, which is used to describe the application information. </span></li>
- <li><a href="../tools/emulator_manager.htm"><strong>Emulator Manager</strong></a><br />
- The Emulator Manager provides emulators to run your application in a virtual environment.</li>
- <li><a href="../tools/emulator_control_panel.htm"><strong>Emulator Control Panel</strong></a><br />
- <span>The Emulator Control panel allows you to run the application in the emulator, and test a variety of user scenarios, such as network access, audio input and out, and text messages. </span></li>
- <li><strong><span><a href="../tools/device_manager.htm">Device Manager</a></span></strong><br />
- The Device Manager <span>is a standalone tool that provides information of connected Tizen devices or emulators for application debugging.</span></li>
- <li><strong><a href="../tools/log_viewer.htm"><span>Log Viewer</span></a></strong><br />
- The Log Viewer <span>helps you debug your application by capturing all the events logged by the platform and your application.</span></li>
-
- <li><strong><a href="../tools/api-privilege_checker.htm">API and Privilege Checker</a></strong><br />
- The API Checker tool checks for API and privilege usage violations in the application code. It helps you to identify and fix potential problems in the application code related to API and privilege use.</li>
+ <li><a href="project_wizard.htm">Project Wizard</a>
+ <p>The Project Wizard is used to create a Tizen .NET application project. You can select from various project templates that make it easier for you to start coding your application. When you create a new project with a specific template, the Project Wizard uses it to automatically create basic functionalities and default project files and folders for the application.</p></li>
+ <li><a href="certificate_manager.htm">Certificate Manager</a>
+ <p>The Certificate Manager is used to create a certificate profile and register author and distributor certificates. Before installing your application on a device or submitting it to the Tizen Store, you must sign it with a certificate profile while packaging your application.</p></li>
+ <li><a href="manifest_editor.htm">Tizen Manifest Editor</a>
+ <p>The manifest editor allows you to edit the Tizen application manifest with a text or form editor. The application manifest contains the application configuration, including specific features and more general runtime settings.</p></li>
+ <li><a href="emulator_manager.htm">Emulator Manager</a>
+ <p>The Emulator Manager allows you to create multiple Tizen emulator instances, for testing your application in an environment similar to a real device.</p></li>
+ <li><a href="emulator_control_panel.htm">Emulator Control Panel</a>
+ <p>The emulator controls allow you to control the emulator instance and test a variety of user scenarios, such as network access, audio input and output, and text messaging.</p></li>
+ <li><a href="api-privilege_checker.htm">API and Privilege Checker</a>
+ <p>The API Checker tool checks for API and privilege usage violations in the application code. It helps you to identify and fix potential problems in the application code related to API and privilege use.</p></li>
+ <li><a href="device_manager.htm">Device Manager</a>
+ <p>The Tizen Device Manager is used to manage connected Tizen devices and emulator instances. You can also browse files on the device, and transfer files between it and the host computer.</p></li>
+ <li><a href="log_viewer.htm">Log Viewer</a>
+ <p>The log viewer allows you to check the logs of your application based on the logging methods you have inserted into your code. It helps you to debug your application by capturing all the events logged by the platform and your application.</p></li>
</ul>
<toc label="Tizen .NET Preview" topic="html/cover_page.htm">
-<topic href="html/cover_page.htm" label="Introduction">
- <topic href="html/cover_page.htm" label="What's New"></topic>
- <topic href="html/introduction/overview.htm" label="Overview"></topic>
+<topic href="html/cover_page.htm" label="Overview">
+ <topic href="html/introduction/whats_new.htm" label="What's New"></topic>
<topic href="html/introduction/roadmap.htm" label="Roadmap"></topic>
</topic>
-<topic href="html/getting_started/download.htm" label="Getting Started">
- <topic href="html/getting_started/download.htm" label="Download"></topic>
+<topic href="html/getting_started/getting_started_cover.htm" label="Getting Started">
<topic href="html/getting_started/installing.htm" label="Installing Visual Studio Tools for Tizen"></topic>
<topic href="html/getting_started/first_app.htm" label="Creating Your First Tizen .NET Application"></topic>
- <topic href="html/getting_started/porting_xamarinforms.htm" label="Porting Xamarin.Forms Apps to Tizen using Visual Studio"></topic>
+ <topic href="html/getting_started/cross_platform_project.htm" label="Creating Tizen Projects as Cross-platform Solutions"></topic>
+ <topic href="html/getting_started/porting_xamarinforms.htm" label="Porting Xamarin.Forms Applications to Tizen"></topic>
</topic>
<topic href="html/tools/tools_overview.htm" label="Visual Studio Tools for Tizen">
- <topic href="html/tools/tools_overview.htm" label="Overview"></topic>
<topic href="html/tools/project_wizard.htm" label="Project Wizard"></topic>
<topic href="html/tools/certificate_manager.htm" label="Certificate Manager"></topic>
<topic href="html/tools/manifest_editor.htm" label="Tizen Manifest Editor">
</topic>
<topic href="html/tools/emulator_manager.htm" label="Emulator Manager"></topic>
<topic href="html/tools/emulator_control_panel.htm" label="Emulator Control Panel"></topic>
+ <topic href="html/tools/api-privilege_checker.htm" label="API and Privilege Checker"></topic>
<topic href="html/tools/device_manager.htm" label="Device Manager"></topic>
<topic href="html/tools/log_viewer.htm" label="Log Viewer"></topic>
- <topic href="html/tools/api-privilege_checker.htm" label="API and Privilege Checker"></topic>
</topic>
</toc>
projects / sdk / online-doc.git / commitdiff
