<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>C# on DVLUP</title><link>/en/tags/c%23/</link><description>Recent content in C# on DVLUP</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 02 Jan 2020 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/c%23/index.xml" rel="self" type="application/rss+xml"/><item><title>Custom TypingStarted and TypingEnded Events</title><link>/en/blog/2020.01.02-custom-typingstarted-and-typingended-events/</link><pubDate>Thu, 02 Jan 2020 00:00:00 +0000</pubDate><guid>/en/blog/2020.01.02-custom-typingstarted-and-typingended-events/</guid><description>&lt;p&gt;You know that little indicator in a chat that shows if someone is currently typing? I am working on a new post (coming soon, link will be here) that uses SignalR to communicate who is currently typing in a chat room along with the messages themselves.&lt;/p&gt;&#10;&lt;p&gt;To determine who is typing, I use a timer and the &lt;code&gt;TextChanged&lt;/code&gt; event. The timer logic itself is straightforward, in the &lt;code&gt;TextChanged&lt;/code&gt; event starts a timer.&lt;/p&gt;</description></item><item><title>Draw Your Own Xamarin Pie Chart dynamically</title><link>/en/blog/2019.04.18-draw-your-own-pie-chart-dynamically/</link><pubDate>Thu, 18 Apr 2019 00:00:00 +0000</pubDate><guid>/en/blog/2019.04.18-draw-your-own-pie-chart-dynamically/</guid><description>&lt;p&gt;In this tutorial, I&amp;rsquo;ll show you how to draw your own pie chart just using lines and a list of data items. The code itself is in C#, but the concept can be used on any platform that has a drawing library and ArcSegments.&lt;/p&gt;&#10;&lt;p&gt;&lt;img src="../../../en/blog/2019.04.18-draw-your-own-pie-chart-dynamically/2019-04-18_13-44-40.png" alt=""&gt;&lt;/p&gt;&#10;&lt;p&gt;You can view the entire solution in &lt;a href="https://gist.github.com/LanceMcCarthy/b64ee5afdd27b125b8b47816799306e0" target="_blank" rel="noopener"&gt;this GitHub Gist&lt;/a&gt;&#10;. Okay, let&amp;rsquo;s get started!&lt;/p&gt;&#10;&lt;h2 id="setting-up"&gt;Setting Up&lt;/h2&gt;&#10;&lt;p&gt;The first thing you&amp;rsquo;ll need to understand is how the platform&amp;rsquo;s drawing library makes arcs. In this code, I&amp;rsquo;ll be using &lt;a href="https://docs.telerik.com/devtools/xamarin/controls/path/path-overview" target="_blank" rel="noopener"&gt;RadPath&lt;/a&gt;&#10; from &lt;a href="https://www.telerik.com/xamarin-ui" target="_blank" rel="noopener"&gt;Telerik UI for Xamarin&lt;/a&gt;&#10; most libraries work the same way. RadPath lets you use a custom Geometry which has &lt;a href="https://docs.telerik.com/devtools/xamarin/controls/path/getting-started/geometry-structure#radarcsegment" target="_blank" rel="noopener"&gt;RadArcSegment&lt;/a&gt;&#10; object, which has helpful &lt;strong&gt;StartAngle&lt;/strong&gt; and &lt;strong&gt;SweepAngle&lt;/strong&gt; properties.&lt;/p&gt;</description></item><item><title>Talk to the View</title><link>/en/blog/2019.04.16-talk-to-the-view/</link><pubDate>Tue, 16 Apr 2019 00:00:00 +0000</pubDate><guid>/en/blog/2019.04.16-talk-to-the-view/</guid><description>&lt;p&gt;There are many scenarios where a UI component might not have a Command or bindable property available for certain features that you need to access from the view model. There is a simple, but powerful, thing you can do to allow this and not break MVVM or testing capability, leverage the Interface.&lt;/p&gt;&#10;&lt;h2 id="scenario"&gt;Scenario&lt;/h2&gt;&#10;&lt;p&gt;Let&amp;rsquo;s imagine the scenario where we have a special ListView control that has a &lt;strong&gt;HighlightItem&lt;/strong&gt; method that can only be called with a direct reference to that control. There isn&amp;rsquo;t a Command or DependencyProperty (aka BindableProperty in Xamarin.Forms) alternative, so it has to be done in the code behind.&lt;/p&gt;</description></item><item><title>Migrating from PCLStorage to .NET Standard 2.0</title><link>/en/blog/2018.04.19-migrating-from-pclstorage-to-net-standard-2-0/</link><pubDate>Thu, 19 Apr 2018 00:00:00 +0000</pubDate><guid>/en/blog/2018.04.19-migrating-from-pclstorage-to-net-standard-2-0/</guid><description>&lt;p&gt;If you&amp;rsquo;re a Xamarin Forms developer, you&amp;rsquo;ve likely used &lt;a href="https://github.com/dsplaisted/PCLStorage" target="_blank" rel="noopener"&gt;PCLStorage&lt;/a&gt;&#10; (or other Dependency Service) to interact with the target platform&amp;rsquo;s file system in the portable class library&amp;rsquo;s code. However, since November 2017, Xamarin.Forms now uses a .NET Standard 2.0 class library and PCLStorage is no longer supported.&lt;/p&gt;&#10;&lt;h2 id="systemiofile"&gt;System.IO.File&lt;/h2&gt;&#10;&lt;p&gt;This isn&amp;rsquo;t a problem because in .NET Core 2.0 you now have access to System.IO.File&amp;rsquo;s GetFolderPath and SpecialFolder methods (see &lt;a href="https://docs.microsoft.com/en-us/dotnet/api/system.io.file?view=netcore-2.0" target="_blank" rel="noopener"&gt;System.IO.File in .NET Core 2.0 docs&lt;/a&gt;&#10;).&lt;/p&gt;</description></item><item><title>Denied?</title><link>/en/blog/2012.12.13-denied/</link><pubDate>Thu, 13 Dec 2012 00:00:00 +0000</pubDate><guid>/en/blog/2012.12.13-denied/</guid><description>&lt;p&gt;So, you got an email from DVLUP stating that your challenge submission was denied.  Why were you denied? What did you miss?  I wanted to write this post to share the top reasons for denial and how to fix it&amp;hellip; 90% of these are due to the fact you didn&amp;rsquo;t edit your WMAppManifest file.&lt;/p&gt;&#10;&lt;p&gt;Here are the top offenders:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Not all Live Tiles Sizes&lt;/li&gt;&#10;&lt;li&gt;No animated Tiles&lt;/li&gt;&#10;&lt;li&gt;Not all WP8 resolutions&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;#1- You need to have all three tile sizes enabled for your app. Here is a list of the tile sizes from the &lt;a href="http://msdn.microsoft.com/en-US/library/windowsphone/develop/hh202948%28v=vs.105%29.aspx#BKMK_Tilesizesandresolutions" target="_blank" rel="noopener"&gt;MSDN Documentation&lt;/a&gt;&#10;. To rectify this problem, simply toggle the &amp;ldquo;Support for large Tiles&amp;rdquo; property in your WMAppManifest file. See the image in answer #2 for more details.&lt;/p&gt;</description></item></channel></rss>