Lars Willemsen
Lars Willemsen
Experiencing the same issues as described above, also using virtual desktop. Obnoxious, as it's one of the primary reasons to use the extension and completely essential for it to enhance...
This should probably be streamlined more than it is now. I ran into the same problem.
Same issue. Getting the appropriate workloads and templates has been an absolute nightmare so far.
I was able to fix this issue downloading the templates manually through the dotnet CLI. But I pretty much immediately ran into another issue described in #112 after that
For me this could also be prevented by downgrading from the current 0.9.2 to 0.8.1 as described in #782. `cargo install wasm-pack --version 0.8.1` I ran into the same issue...