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
It would be useful for people not using CSI or dotnet-script - especially those using custom CSX hosts - to be able to predefine using statements and assembly references via .rsp files. Those are standard files already used by the compiler itself and look like this: https://github.com/dotnet/roslyn/blob/version-2.4.0/src/Interactive/csi/csi.rsp
In our case, we'd pick up the references used there and use them as globally imported namespaces / references when constructing CSX project system. Configuration proposal - inside omnisharp.json, under script node, as rspPath property. For example:
Since omnisharp.json can be global, you could even - in one sweep - configure your entire DEV box if you wanted.
The text was updated successfully, but these errors were encountered:
Spun off from dotnet/vscode-csharp#1856
It would be useful for people not using CSI or dotnet-script - especially those using custom CSX hosts - to be able to predefine using statements and assembly references via
.rsp
files. Those are standard files already used by the compiler itself and look like this: https://github.com/dotnet/roslyn/blob/version-2.4.0/src/Interactive/csi/csi.rspIn our case, we'd pick up the references used there and use them as globally imported namespaces / references when constructing CSX project system. Configuration proposal - inside
omnisharp.json
, underscript
node, asrspPath
property. For example:Since
omnisharp.json
can be global, you could even - in one sweep - configure your entire DEV box if you wanted.The text was updated successfully, but these errors were encountered: