Lex Li

We cherry-picked your change in [this fork](https://marketplace.visualstudio.com/items?itemName=lextudio.vscode-axaml) and shipped as release 11.0.35.

Resolved in #313

We resolved this issue in [our fork](https://marketplace.visualstudio.com/items?itemName=lextudio.vscode-axaml).

This extension doesn't write anything to the OUTPUT panel of VS Code. So, you'd better describe clearly what you wanted to report.

VS Code itself bundles the syntax file from this extension already, so in latest VS Code releases you don't even need to install this extension. Thus, when you said .rst...

This is the wrong place to report pyasn1 issues. Please visit https://github.com/pyasn1/pyasn1

The command to create new Avalonia projects doesn't verify .NET runtime presence, so it fails like you describe if no runtime is available. We have fixed it in [this fork](https://marketplace.visualstudio.com/items?itemName=lextudio.vscode-axaml)...

@FrightRisk please create your own issue and follow the wizard to provide necessary information. Lingering under another issue doesn't help much as your case can be different in several ways.

BTW, you shouldn't be using the old 0.11 release. The new 0.95.2 works very well for me. Check out #899 for more details.

The old `nextCmd` is actually GET NEXT based WALK operation. This was only fixed in recent releases, where `nextCmd` and `walkCmd` are both presented and serve different purposes.