Skip to content
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

Copy Activate.ps1 activate.sh from Asp.Net Core to .Net runtime to use before VS Code. #36930

Open
jmaine opened this issue May 23, 2020 · 5 comments

Comments

@jmaine
Copy link
Contributor

jmaine commented May 23, 2020

Description

Copy these files below to the root of the .net runtime repository.

Configuration

This is to help develop the .Net runtime using VS Code like it is used in the same way for Asp.Net Core.

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label May 23, 2020
@Dotnet-GitSync-Bot
Copy link
Collaborator

I couldn't figure out the best area label to add to this issue. Please help me learn by adding exactly one area label.

@ghost
Copy link

ghost commented May 24, 2020

Tagging subscribers to this area: @ViktorHofer
Notify danmosemsft if you want to be subscribed.

@ViktorHofer
Copy link
Member

I don't see any reason why we would need these files to support VSCode? Test execution inside VS or VSCode should "just" work without any env var modification.

@jmaine
Copy link
Contributor Author

jmaine commented May 24, 2020

@ViktorHofer, I have to use those files to get Omnisharp to load the *.csproj files correctly; otherwise, I cannot use the "find declaration" or "find all references" features that Omnisharp provides.

I am using the C# extension for VS Code provided by Microsoft.

@ViktorHofer
Copy link
Member

I see, thanks for clarifying. Our goal is to deliver the desired experience without such "hacks". @Anipik is working on Intellisense support.

@jmaine can you provide repro steps so that we better understand what's currently broken in vscode? Thanks

@ViktorHofer ViktorHofer removed the untriaged New issue has not been triaged by the area owner label Jul 15, 2020
@ViktorHofer ViktorHofer added this to the Future milestone Jul 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

4 participants