search

microsoft / vscode-dotnettools

This is a feedback repository to capture issues logged for the C# Dev Kit and related extensions from Visual Studio Code
Other
228 stars 12 forks source link

Easy and clear build and publish features #461

Open thenexus00 opened 1 year ago

thenexus00 commented 1 year ago

Type: Feature Request

One of the things I like about the Mac Visual Studio is how it has the easy build, debug and publish options.

Could the run and debug that exists when you do go to debug and the overing little control be turned into a proper perminant (or otpion to keep on) bar with the controls here and similar features from visual studio (mac). It needs to be clear so you know what build mode your on and so on and better and clearer publish options.

Extension version: 0.4.10 VS Code version: Code 1.81.1 (Universal) (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:20:33.924Z) OS version: Darwin x64 22.6.0 Modes:

thenexus00 commented 1 year ago

As a note. You do have "run and debug" on the left sidebar. It does introduce a similar layout as in visual studio mac for run but it only reads the launch settings file.

thenexus00 commented 1 year ago

Also, I understand that there is a launch settings file but the amount of setup you need to do int here and if others pick these things up for different environments, peoples machines (Path to browsers) etc is a bit much. VC Code needs that auto pickup and easy to use and quick options VC Mac has.

I actually have both. Some coding is faster in VSC but the intelisense, showing overloads etc is still clunky in VSC so I will often use VCMac for that as well the actual build, publish and debug. It is just easier and quicker there.

timheuer commented 1 year ago

Hi @thenexus00 thanks for taking the time for the suggestions here. First primarily, we are an extension that plugs in to the VS Code shell -- so some of your suggestions are actually more for VS Code as this extension is a provider of data/debuggers/etc but the primary UI interaction is from VSCode.

  • Very clear play,pause,stop button at the top

As you noted, this exists once you are in the debug view but only until you get there -- this would be a request for VS Code (microrosft/vscode)

  • Breadcrumb style option list for the launch settings and app settings

Can you explain this one a bit more?

There is no clear and easy way to publish

Do you mean publish the output (e.g., dotnet publish or right-click publish)?

On the debugger side, you actually don't need a launch settings file for most cases (it is still helpful for some). If you have an open C# file and F5 without a launch.json file you will get our debug provider (It's labeled "C#") and will launch the app: https://code.visualstudio.com/docs/csharp/debugging#_debug-with-f5

thenexus00 commented 1 year ago

What we need from VS Mac: This is in the scope if a c# dotnet (core) project but the same/similar issues for other similar projects.

Top area: https://www.dropbox.com/s/qyz6cnilpusb27x/Screenshot%202023-09-01%20at%209.56.17%20am.png?dl=0 An option to have this always showing in some form for quick access.

Auto pickup of launch and app settings: https://www.dropbox.com/s/qyz6cnilpusb27x/Screenshot%202023-09-01%20at%209.56.17%20am.png?dl=0 No messing with overly complicated VSC specific settings JSON on top. Properly picking up what is already configured. Noting you have the release and debug as well.

Auto pickup for browser options: https://www.dropbox.com/s/8qyik6d2xk7s8d8/Screenshot%202023-09-01%20at%209.56.25%20am.png?dl=0 Just picks things up automatically which is great. If your a team of windows and mac users are using VSC right now you have to have a launch JSON with specific paths to their browsers and their machines etc and that just becomes insanely complicated. You say it can work without but I and what I can see others complaining about the EOL of VS mac are all saying the same or similar things.

Better Package management: https://www.dropbox.com/s/ja0vqnshndy27cb/Screenshot%202023-09-01%20at%209.56.36%20am.png?dl=0 The actual nuget package management on VC is just bad when your in it and in VC Mac the way you can see updates and then apply them... https://www.dropbox.com/s/d3phfmnbax1278n/Screenshot%202023-09-01%20at%209.56.40%20am.png?dl=0

It is just a lot easier and more efficient to manage.

Same with the Publish process as well.

Visual Studio Code has a lot going for it and it has been great but over time the lack of proper UI work has shown and all the team has done mainly is command line, settings file, JSON this and that updates with minimum UI. The debug options layout was bad years ago and unchanged and the bottom bar is just a mess now, especially with extensions having limit places to put their extra functionality in place.

None of this is big stuff but before you EOL the Mac IDE putting some effort into VSC and not just features there but implemented in a clunky way. There has been this whole push from MS for the uniformity and platform agnostic nature. You need to put some of the love in there for the non Windows folk, and really even the Windows folk. The latest VC for PC is OK but it is still clunky and dated UI, VC Mac has way better implementations in many aspects. I can see internally the thoughts of having VC and VSC have clear differences but if your removing other dedicated IDE for other platforms and pointing people to VSC - You need to step up more and put that work into it. Again I do not think its hard with the UI improvements. You can take queues from VC Mac on the bottom bar with spacing and layout tweaks to help that from being a mess. The sidebar clutter, better debug, publish, build and tree tweaks - People will start to feel better about things.