Incompatibility with NAudio 2.0.0-beta1
See original GitHub issueWhen traing to upgrade NAudio from 1.10 to 2.0 beta 1, the code does not compile anymore and throws an error:
Gravité Code Description Projet Fichier Ligne État de la suppression
Erreur CS0012 Le type 'WaveFormat' est défini dans un assembly qui n'est pas référencé. Vous devez ajouter une référence à l'assembly 'NAudio, Version=1.10.0.0, Culture=neutral, PublicKeyToken=null'. Common.Audio C:\Users\Patrick\source\repos\Project\Common.Audio\CachedSound.cs 251 Actif
It is missing an assembly ‘NAudio, Version=1.10.0.0, Culture=neutral, PublicKeyToken=null’ and does not seem to recognize the new version.
The error occurs at this line of my code:
using (LameMP3FileWriter writer = new LameMP3FileWriter(fileName, mp3WaveFormat, bitRate))
The usings are (unchanged):
using NAudio.Wave;
using NAudio.Lame;
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
NAudio 2.0.0
Package, Downloads. Universal.Android. Class library for accelerating Xamarin.Android development. Note: If you encounter layout inflation ...
Read more >NAudio.Lame
I've been trying to find and fix an issue where on some PC's, in some cases, a null-reference exception is thrown when stopping...
Read more >NAudio will not install. · Issue #859
NAudio 2 requires netstandard2.0 compatibility, which means you should ideally be targeting at least .NET Framework 4.7. Is there any reason you ...
Read more >react-native-audio-recorder-player - npm Package Overview
This is a react-native link module for audio recorder and player. This is not a playlist audio module and this library provides simple ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m hoping that the backwards compatibility of v2 should mean that most people don’t need to stay on 1.x, but I can always backport a bugfix to the old branch if it’s needed.
Closing as not reproducible and no response received.