Upgrade Guide: Migrating Your App to fsMediaLibrary.NET

10 fsMediaLibrary.NET Tips Every .NET Developer Should Know

1. Understand supported platforms
   Confirm which .NET runtimes and target platforms (e.g., .NET Framework, .NET Core/.NET 5+) the library supports before integrating—mismatched runtime versions cause build/runtime errors.

2. Use the latest stable release
   Prefer the latest stable package version to get bug fixes and security patches. Check the project’s release notes for breaking changes before upgrading.

3. Manage permissions early
   Media access often requires runtime permissions (especially on mobile or sandboxed environments). Request and verify read/write permissions at app startup or before media operations to avoid failures.

4. Optimize for large libraries
   When enumerating or displaying many media items, load metadata lazily, page results, and avoid loading full-resolution files until needed to reduce memory and I/O overhead.

5. Cache thumbnails and metadata
   Generate and cache thumbnails and commonly used metadata (dimensions, duration, timestamps) locally to improve scrolling performance and reduce repeated disk/network access.

6. Handle different media formats
   Expect varied image/video codecs and container formats. Implement fallback handling or conversion paths for unsupported formats, and gracefully surface errors to users.

7. Use asynchronous APIs
   Prefer async/await and non-blocking I/O operations provided by the library to keep UI responsive—avoid synchronous file reads on the UI thread.

8. Respect EXIF and orientation
   Read EXIF orientation and rotation metadata for images and apply it when rendering thumbnails or full images to avoid incorrectly oriented displays.

9. Implement robust error handling and retries
   File access can fail due to locks, removable media, or transient OS issues. Use retries with backoff for transient errors and clear user-facing messages for permanent failures.

10. Profile and monitor performance
    Measure memory, CPU, and I/O during media operations. Use profiling tools and logging to find hotspots (e.g., decoding, resizing) and optimize by batching, throttling concurrent operations, or using native acceleration.

If you want, I can expand any tip into code samples (synchronous vs. async thumbnail loading, caching strategies, permission checks) for your target .NET version.