Updating readmes and nuspec before NuGet release. Final commit of ver…

…sion 2.8

README.md

@@ -13,7 +13,7 @@
 
 ## Current NuGet Release Status
 - If you would like to support this project, you can show your appreciation via [PayPal.Me](https://www.paypal.me/mariodivece/50usd)
-- Current Status: (2018-09-23) - Release 4.0.270 is now available, (see the <a href="https://github.com/unosquare/ffmediaelement/releases">Releases</a>)
+- Current Status: (2019-03-16) - Release 4.0.280 is now available, (see the <a href="https://github.com/unosquare/ffmediaelement/releases">Releases</a>)
 - NuGet Package available here: https://www.nuget.org/packages/FFME.Windows/
 - FFmpeg Version: <a href="https://ffmpeg.zeranoe.com/builds/win32/shared/ffmpeg-4.0.2-win32-shared.zip">4.1 (32-bit)</a>
 
@@ -22,7 +22,7 @@
 ## Quick Usage Guide for WPF Apps
 
 Here is a quick guide on how to get started.
-1. Open Visual Studio (v2017 recommended), and create a new WPF Application. Target Framework must be 4.6.1 or above.
+1. Open Visual Studio (v2017 or v2019 recommended), and create a new WPF Application. Target Framework must be 4.6.1 or above.
 2. Install the NuGet Package from your Package Manager Console: `PM> Install-Package FFME.Windows`
 3. You need FFmpeg shared binaries (64 or 32 bit, depending on your app's target architecture). Build your own or download a compatible build from [Zeranoe FFmpeg Builds site](https://ffmpeg.zeranoe.com/builds/).
 4. Your FFmpeg build should have a `bin` folder with 3 exe files and some dll files. Copy all those files to a folder such as `c:\ffmpeg`

Support/ffme.win.nuspec

@@ -10,12 +10,12 @@
     <projectUrl>https://github.com/unosquare/ffmediaelement</projectUrl>
     <iconUrl>https://raw.githubusercontent.com/unosquare/ffmediaelement/master/Support/ffme.png</iconUrl>
     <requireLicenseAcceptance>true</requireLicenseAcceptance>
-    <description>FFME is a close (and I'd like to think better) drop-in replacement for Microsoft's WPF MediaElement Control. While the standard MediaElement uses DirectX (DirectShow) for media playback, FFME uses FFmpeg to read and decode audio and video. This means that for those of you who want to support stuff like HLS playback, or just don't want to go through the hassle of installing codecs on client machines, using FFME might just be the answer.</description>
+    <description>FFME is an advanced media control and a close drop-in replacement for Microsoft's WPF MediaElement Control. While the standard MediaElement uses DirectX (DirectShow) for media playback, FFME uses FFmpeg to read and decode audio and video. This means that for those of you who want to support stuff like HLS playback, or just don't want to go through the hassle of installing codecs on client machines, using FFME might just be the answer.</description>
     <summary>FFmpeg MediaElement Control (FFME)</summary>
     <releaseNotes>
       This is a release package of the Michelob build referencing bindings to FFmpeg version 4.1
       This package does not contain the required FFmpeg binaries. Please refer to the following URL for instructions on how to obtain the binaries: https://github.com/unosquare/ffmediaelement
-      Release details: https://github.com/unosquare/ffmediaelement/milestone/9?closed=1
+      Release details: https://github.com/unosquare/ffmediaelement/milestone/10?closed=1
     </releaseNotes>
     <copyright>Copyright © 2015-2019 Mario Di Vece, Unosquare SA de CV</copyright>
     <language>en-US</language>

Support/readme.txt

@@ -1,8 +1,10 @@
 How to use FFME
-In order to use the FFME MediaElement control, you will need to setup a folder with FFmpeg binaries. Here are the steps:
 
-1. You can build your own FFmpeg or download a compatible build from the wonderful Zeranoe FFmpeg Builds site: (https://ffmpeg.zeranoe.com/builds/win32/shared/ffmpeg-4.1-win32-shared.zip).
-2. Your FFmpeg build (see the bin folder) should have 3 exe files and a number of dll files. Copy all of them to a folder such as (c:\ffmpeg)
+In order to use the FFME MediaElement control, you will need to setup a folder with FFmpeg binaries and point to it from your application code.
+Here are the steps:
+
+1. You can build your own FFmpeg shared binaries or download a compatible build from the wonderful Zeranoe FFmpeg Builds site: (https://ffmpeg.zeranoe.com/builds/win32/shared/ffmpeg-4.1-win32-shared.zip).
+2. Your FFmpeg build (see the bin folder) should have 3 exe files and a number of dll files and must match your app's architecture (32-bit or 64-bit). Copy all of them to a folder such as (c:\ffmpeg)
 3. Within you application's startup code (Main method), set Unosquare.FFME.MediaElement.FFmpegDirectory = @"path to ffmpeg binaries from the previous step";.
 4. Use the FFME MediaElement control as any other WPF control!
    For example: In your MainForm.xaml, add the namespace: xmlns:ffme="clr-namespace:Unosquare.FFME;assembly=ffme.win"