# VisioForge .NET SDKs Installation Guide

Video Capture SDK .Net Video Edit SDK .Net Media Blocks SDK .Net Media Player SDK .Net

VisioForge offers powerful multimedia SDKs for .NET developers that enable advanced video capture, editing, playback, and media processing capabilities in your applications. This guide covers everything you need to know to properly install and configure our SDKs in your development environment.

# Available .NET SDKs

VisioForge provides several specialized SDKs to address different multimedia needs:

Video Capture SDK .Net - For capturing video from cameras, screen recording, and streaming
Video Edit SDK .Net - For video editing, processing, and format conversion
Media Blocks SDK .Net - For building custom media processing pipelines
Media Player SDK .Net - For creating custom media players with advanced features

# Installation Methods

You can install our SDKs using two primary methods:

# Using Setup Files

The setup file installation method is recommended for Windows development environments. This approach:

Automatically installs all required dependencies
Configures Visual Studio integration
Includes sample projects to help you get started quickly
Provides documentation and additional resources

Setup files can be downloaded from the respective SDK product pages on our website.

# Using NuGet Packages

For cross-platform development or CI/CD pipelines, our NuGet packages offer flexibility and easy integration:

Install-Package VisioForge.DotNet.Core

Additional UI-specific packages may be required depending on your target platform:

Install-Package VisioForge.DotNet.Core.UI.MAUI
Install-Package VisioForge.DotNet.Core.UI.WinUI
Install-Package VisioForge.DotNet.Core.UI.Avalonia
Install-Package VisioForge.DotNet.Core.UI.Android

# IDE Integration and Setup

Our SDKs seamlessly integrate with popular .NET development environments:

# Visual Studio Integration

Visual Studio offers the most complete experience with our SDKs:

Full IntelliSense support for SDK components
Built-in debugging for media processing components
Designer support for visual controls
NuGet package management

For detailed Visual Studio setup instructions, see our Visual Studio integration guide.

# JetBrains Rider Integration

Rider provides excellent cross-platform development support:

Full code completion for SDK APIs
Smart navigation features for exploring SDK classes
Integrated NuGet package management
Cross-platform debugging capabilities

For Rider-specific instructions, visit our Rider integration documentation.

# Visual Studio for Mac

Visual Studio for Mac users can develop applications for macOS, iOS, and Android:

Built-in NuGet package manager for installing SDK components
Project templates for quick setup
Integrated debugging tools

Learn more in our Visual Studio for Mac setup guide.

# Platform-Specific Configuration

# Target Framework Configuration

Each operating system requires specific target framework settings for optimal compatibility:

# Windows Applications

Windows applications must use the -windows target framework suffix:

<TargetFramework>net8.0-windows</TargetFramework>

This enables access to Windows-specific APIs and UI frameworks like WPF and Windows Forms.

# Android Development

Android projects require the -android framework suffix:

<TargetFramework>net8.0-android</TargetFramework>

Ensure that Android workloads are installed in your development environment:

dotnet workload install android

# iOS Development

iOS applications must use the -ios target framework:

<TargetFramework>net8.0-ios</TargetFramework>

iOS development requires a Mac with Xcode installed, even when using Visual Studio on Windows.

# macOS Applications

macOS native applications use either the -macos or -maccatalyst framework:

<TargetFramework>net8.0-macos</TargetFramework>

For .NET MAUI applications targeting macOS, use:

<TargetFramework>net8.0-maccatalyst</TargetFramework>

# Linux Development

Linux applications use the standard target framework without a platform suffix:

<TargetFramework>net8.0</TargetFramework>

Ensure required .NET workloads are installed:

dotnet workload install linux

# Special Framework Support

# .NET MAUI Applications

MAUI projects require special configuration:

Add the VisioForge.DotNet.Core.UI.MAUI NuGet package
Configure platform-specific permissions in your project
Use MAUI-specific video view controls

See our detailed MAUI guide for complete instructions.

# Avalonia UI Framework

Avalonia projects provide a cross-platform UI alternative:

Install the VisioForge.DotNet.Core.UI.Avalonia package
Use Avalonia-specific video rendering controls
Configure platform-specific dependencies

Our Avalonia integration guide provides complete setup instructions.

# SDK Initialization for Cross-Platform Engines

Our SDKs include both Windows-specific DirectShow engines (like VideoCaptureCore) and cross-platform X-engines (like VideoCaptureCoreX). The X-engines require explicit initialization and cleanup.

# Initializing the SDK

Before using any X-engine components, initialize the SDK:

// Initialize at application startup
VisioForge.Core.VisioForgeX.InitSDK();

// Or use the async version
await VisioForge.Core.VisioForgeX.InitSDKAsync();

# Cleaning Up Resources

When your application exits, properly release resources:

// Clean up at application exit
VisioForge.Core.VisioForgeX.DestroySDK();

// Or use the async version
await VisioForge.Core.VisioForgeX.DestroySDKAsync();

Failing to initialize or clean up properly may result in memory leaks or unstable behavior.

# Video Rendering Controls

Each UI framework requires specific video view controls to display media content:

# Windows Forms

// Add reference to VisioForge.DotNet.Core
using VisioForge.Core.UI.WinForms;

// In your form
videoView = new VideoView();
this.Controls.Add(videoView);

# WPF Applications

// Add reference to VisioForge.DotNet.Core
using VisioForge.Core.UI.WPF;

// In your XAML
<vf:VideoView x:Name="videoView" />

# MAUI Applications

// Add reference to VisioForge.DotNet.Core.UI.MAUI
using VisioForge.Core.UI.MAUI;

// In your XAML
<vf:VideoView x:Name="videoView" />

# Avalonia UI

// Add reference to VisioForge.DotNet.Core.UI.Avalonia
using VisioForge.Core.UI.Avalonia;

// In your XAML
<vf:VideoView Name="videoView" />

# Native Dependencies Management

Our SDKs leverage native libraries for optimal performance. These dependencies must be properly managed for deployment:

Windows: Included automatically with setup installation or NuGet packages
macOS/iOS: Bundled with NuGet packages but require proper app signing
Android: Included in NuGet packages with proper architecture support
Linux: May require additional system packages depending on distribution

For detailed deployment instructions, see our deployment guide.

# Troubleshooting Common Installation Issues

If you encounter issues during installation:

Verify target framework compatibility with your project type
Ensure all required workloads are installed (dotnet workload list)
Check for dependency conflicts in your project
Confirm proper SDK initialization for X-engines
Review platform-specific requirements in our documentation

# Sample Code and Resources

We maintain an extensive collection of sample applications on our GitHub repository to help you get started quickly with our SDKs.

These examples cover common scenarios like:

Video capture from cameras and screens
Media playback with custom controls
Video editing and processing
Cross-platform development

Visit our repository for the latest code examples and best practices for using our SDKs.

For additional support or questions, please contact our technical support team or visit our documentation portal.