Update: the solution turned out to be simple. This is due to a Visual Studio bug, namely the new resource explorer. If you encounter a similar problem, just update the Visual Studio