How to migrate from v9 to v10?

v10 SDK have a lot of API changes, a lot of properties and methods remove or replaces, now SDK API not “plain” as before, we got near 200-300 properties and methods for 1 main class of each SDK, that’s too much.

Media Player SDK migration:

  1. Upgrade project to .Net 4.0 or later. .Net 2.0 – 3.5 is no longer supported.
  2. Replace VisioForge.Controls.WinForms / VisioForge.Controls.WPF to VisioForge.Controls.UI in references.
  3. Remove all properties that not found in your WinForms/XAML designer file (Form1.Designer.cs or Windows1.xaml for example). Store non-default values somethere in your code to apply them later.
  4. Update your video effects like shown in demo code and here.
  5. Update video renderer like shown in demo application.
  6. Update motion detection, chroma-key or object detection using special classes like shown in demo.

Video Capture SDK migration:

  1. Upgrade project to .Net 4.0 or later. .Net 2.0 – 3.5 is no longer supported.
  2. Replace VisioForge.Controls.WinForms / VisioForge.Controls.WPF to VisioForge.Controls.UI in references.
  3. Remove all properties that not found in your WinForms/XAML designer file (Form1.Designer.cs or Windows1.xaml for example). Store non-default values somethere in your code to apply them later.
  4. Update your video effects like shown in demo code and here.
  5. Update video renderer like shown in demo application.
  6. Update motion detection, chroma-key or object detection using special classes like shown in demo.
  7. Now SDK have special class for each available output format. You must create class instance, apply parameters and assign it to Output_Format property, instead enum that used before.

Video Edit SDK migration:

  1. Upgrade project to .Net 4.0 or later. .Net 2.0 – 3.5 is no longer supported.
  2. Replace VisioForge.Controls.WinForms / VisioForge.Controls.WPF to VisioForge.Controls.UI in references.
  3. Remove all properties that not found in your WinForms/XAML designer file (Form1.Designer.cs or Windows1.xaml for example). Store non-default values somethere in your code to apply them later.
  4. Update your video effects like shown in demo code and here.
  5. Update video renderer like shown in demo application.
  6. Update motion detection, chroma-key or object detection using special classes like shown in demo.
  7. Now SDK have special class for each available output format. You must create class instance, apply parameters and assign it to Output_Format property, instead enum that used before.
  8. File adding API has been changed, please check demo code. Now you can add multiple segments from the same source file and specify additional independent setting.
Please contact support to get help with this tutorial. Visit our GitHub page to get more code samples.
VisioForge © 2006 - 2021