-
Notifications
You must be signed in to change notification settings - Fork 161
Issues: dotnet-script/dotnet-script
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
init command - consider highlighting when .vscode/launch.json file overwritten and not updated
#754
opened May 6, 2024 by
adamfk
Cache from different scripts refers to the same folder
bug
#752
opened Apr 22, 2024 by
orange-world-developer-two
Inconsistent argument passing in
Environment.GetCommandLineArgs()
and Args
#749
opened Feb 16, 2024 by
Pxtl
Getting "missing reference errors" in Visual Code and dotnet script.
#727
opened May 26, 2023 by
mmarvb8h
Shebang directive on top of the file breaks #r SDK parsing
bug
#723
opened May 19, 2023 by
marvfinsy
Cannot restore nuget packages if script location has %20 in path
#721
opened May 16, 2023 by
owenholloway
Is there support for equivalent of .csproj ImplicitUsings? Could it be added?
#719
opened May 11, 2023 by
charring
How to pass the NuGetInteractive option to dotnet script?
package management
#715
opened Apr 17, 2023 by
msfcolombo
Questions about formal parameters of methods in script files
needs more info
#711
opened Apr 1, 2023 by
nczsl
Referencing later NuGet client libraries leads to crash and no stack trace (unless --debug is set)
#709
opened Mar 30, 2023 by
mungojam
[feature request] Ignore Directory.Build.props/targets from ancestor directories
feature request
#701
opened Feb 14, 2023 by
amis92
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.