-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support multiple runtimes (.NET Framework and .NET Core) in Interactive Window #4788
Comments
Consider reading environment init scripts and config from user home dir. |
tmat
changed the title
Write specialized reset command for C# and VB interactive
Write specialized reset command for C# and VB interactive, support multiple runtimes
Dec 16, 2016
tmat
changed the title
Write specialized reset command for C# and VB interactive, support multiple runtimes
Support multiple runtimes (.NET Framework and .NET Core) in Interactive Window
Dec 18, 2019
We are gonna use the Core CLR that are found using VS process environment variables. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to distinguish between environment definition (32bit vs 64bit, Desktop/CoreCLR, which version of CoreCLR, etc.) and initialization script.
I propose following:
Resets to the most recently used environment without running initialization script (using “noinit” instead of “noconfig” since it’s a better name).
Resets to the most recently used environment and runs the default initialization script (if any).
Resets to the specified environment without running initialization script.
Resets to the specified environment and runs the default initialization script.
The #reset command prints out info about the environment being loaded.
Environment is a file name or a path. If an extension isn’t specified we append extension “.json”. If the path is relative we search in some predefined folder in user home directory and then in the installation directory in the interactive host.
The .json file will describe the environment in JSON format. I think we should move away from .rsp file for REPL initialization since it’s not flexible enough.
An optional initialization script is of the same name but with .csx/.vbx extension. For example:
dnx32.csx:
dnx64.csx
dnx_common.csx:
Sample session:
The text was updated successfully, but these errors were encountered: