You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 24, 2020. It is now read-only.
Hi, I'm experimenting with converting C# files (designed for this purpose) into JavaScript. The C# files only have a reference to the System and System.Dynamic namespaces only (nothing else is allowed). My plan was to use the parsing to break it all apart, then traverse the expression tree to output JavaScript. I wanted to confirm if this is the right course, or is it best to add all syntax trees in a "project content" object, compile it, and somehow use/analyze that instead? My goal is to trap any errors, such as parsing, and unresolved semantics, and let the user know if something they did is not supported/wrong. I figured out the parsing errors part (via the demo), and I also know where the namespaces are. I don't understand how to check for unresolved types or semantics to determine if something the user is doing is not allowed/not supported...? For example, I'm only loading the mscorlib and System.Core.dll assemblies into a project content object. If, after compiling, a type is "unresolved" because I didn't load that library, then I need to find it and tell the user. Thanks.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I'm experimenting with converting C# files (designed for this purpose) into JavaScript. The C# files only have a reference to the System and System.Dynamic namespaces only (nothing else is allowed). My plan was to use the parsing to break it all apart, then traverse the expression tree to output JavaScript. I wanted to confirm if this is the right course, or is it best to add all syntax trees in a "project content" object, compile it, and somehow use/analyze that instead? My goal is to trap any errors, such as parsing, and unresolved semantics, and let the user know if something they did is not supported/wrong. I figured out the parsing errors part (via the demo), and I also know where the namespaces are. I don't understand how to check for unresolved types or semantics to determine if something the user is doing is not allowed/not supported...? For example, I'm only loading the mscorlib and System.Core.dll assemblies into a project content object. If, after compiling, a type is "unresolved" because I didn't load that library, then I need to find it and tell the user. Thanks.
The text was updated successfully, but these errors were encountered: