Preparing for 4.0.250 release

unosquare · May 20, 2018 · 310c45d · 310c45d
1 parent cd76596
commit 310c45d
Show file tree

Hide file tree

Showing 5 changed files with 6 additions and 6 deletions.
diff --git a/README.md b/README.md
@@ -12,9 +12,9 @@
 
 ## 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-04-25) - Release 3.4.240 is now available, (see the <a href="https://github.com/unosquare/ffmediaelement/releases">Releases</a>)
+- Current Status: (2018-05-20) - Release 3.4.250 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-3.4.2-win32-shared.zip">3.4.2 (32-bit)</a>
+- FFmpeg Version: <a href="https://ffmpeg.zeranoe.com/builds/win32/shared/ffmpeg-4.0-win32-shared.zip">3.4.2 (32-bit)</a>
 
 *Please note the current NuGet realease might require a different version of the FFmpeg binaries than the ones of the current state of the source code.*
 

diff --git a/Support/readme.txt b/Support/readme.txt
@@ -2,7 +2,7 @@ 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.0-win32-shared.zip).
-2. Your FFmpeg build (see the bin folder) should have 3 exe files and 8 dll files. Copy all 11 files to a folder such as (c:\ffmpeg)
+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)
 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"

diff --git a/Unosquare.FFME.Common/Unosquare.FFME.Common.csproj b/Unosquare.FFME.Common/Unosquare.FFME.Common.csproj
@@ -4,7 +4,7 @@
   <PropertyGroup>
     <TargetFrameworks>netstandard2.0;net461</TargetFrameworks>
     <RootNamespace>Unosquare.FFME</RootNamespace>
-    <Version>4.0.2.250</Version>
+    <Version>4.0.250</Version>
     <Authors>Mario Di Vece and Contributors to the FFME project</Authors>
     <Company>Unosquare SA de CV</Company>
     <Product>FFME Cross-Platform Media Engine</Product>

diff --git a/Unosquare.FFME.Windows.Sample/Properties/AssemblyInfo.cs b/Unosquare.FFME.Windows.Sample/Properties/AssemblyInfo.cs
@@ -40,5 +40,5 @@
 // You can specify all the values or you can default the Build and Revision Numbers
 // by using the '*' as shown below:
 // [assembly: AssemblyVersion("1.0.*")]
-[assembly: AssemblyVersion("2018.5.1.*")]
+[assembly: AssemblyVersion("2018.5.20.*")]
 [assembly: AssemblyFileVersion("4.0.250")]
diff --git a/Unosquare.FFME.Windows/Properties/AssemblyInfo.cs b/Unosquare.FFME.Windows/Properties/AssemblyInfo.cs
@@ -31,5 +31,5 @@
 // You can specify all the values or you can default the Build and Revision Numbers
 // by using the '*' as shown below:
 // [assembly: AssemblyVersion("1.0.*")]
-[assembly: AssemblyVersion("2018.5.1.*")]
+[assembly: AssemblyVersion("2018.5.20.*")]
 [assembly: AssemblyFileVersion("4.0.250")]