Visual Studio Blog

Good read for me - just bought a MacBook Pro M1. After years of working on Windows, this is my primary development machine now. Still learning and making adjustments. Doing all JavaScript/TypeScript/React work in VS Code. Using VS for Mac for .NET work, which is an adjustment, but working so far - they're working on better M1 support in the .NET 6 timeframe, which is in preview 1 right now: https://devblogs.microsoft.com/visualstudio/visual-studio-2019-for-mac…

Auto History for Visual Studio is excellent for this use case. https://devblogs.microsoft.com/visualstudio/auto-history-extension-in-…

> it's a great implementation of the traditional stop-and-inspect debugger feature set, but that's all It provides more than that - the "Edit and Continue" feature is invaluable, allowing you to pause execution at a breakpoint and change the code, such that the new code runs when execution resumes. As an aside, Rider also has this feature, and I find it to be much faster and more reliable than VS. Visual Studio also recently got "Time Travel Debugging"[0], which lets you record execution then replay in the debugger. I haven't actually tried this yet. [0] https://devblogs.microsoft.com/visualstudio/introducing-time-travel-de…

Visual Studio for Mac has run natively on M1 (without Rosetta) since the May 22 release of Visual Studio 2022 for Mac v17.0 - https://devblogs.microsoft.com/visualstudio/visual-studio-2022-for-mac… The installer is a separate binary and currently still requires Rosetta. There's an update due out very soon (a few weeks) that will remove the Rosetta requirement. The team prioritized getting the application fully native before the installer since you spend a lot more time running the app than the installer. Also it's important to know that Visual Studio for Mac isn't the exact same application as Visual Studio (Windows). Visual Studio is 25 years old and has some Windows specific features that don't make sense on macOS. Also, Visual Studio for Mac is optimized to integrate with macOS features (e.g. accessibility and themeing). There's a lot of code shared between the editor, project system, debuggers, etc., and we try to balance making them as similar as possible while following the macOS app guidelines and conventions. Disclaimer: I'm on the .NET team at Microsoft, and work with the Visual Studio for Mac team a lot.

> Making the model write a research file Having LLMs write their prompt files was something that became a thing the moment prompt files became a thing. > then the plan and iterate on it by editing the plan file, then adding the todo list, then doing the implementation, and doing all that in a single conversation (instead of clearing contexts). That's literally what planning mode is. Do yourself a favor and read the announcement of support for planning mode in Visual Studio. Visual Studio code supported it months before. https://devblogs.microsoft.com/visualstudio/introducing-planning-in-vi…

> it's still the weird Visual Studio format .NET 9 (and VS2022) added support for the SLNX replacement format to replace the old weird solution format: https://devblogs.microsoft.com/visualstudio/new-simpler-solution-file-…

There's a rule that if something is easy to invent, a bunch of people will whip up their own versions independently, sometimes even within the same organisation. So for there's... C# scripting (CSI.exe): https://learn.microsoft.com/en-us/archive/msdn-magazine/2016/january/e… PowerShell Add-Type that allows one-file inline C# scripting: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershe… The Roslyn .CSX script files (RCSI.exe): https://devblogs.microsoft.com/visualstudio/introducing-the-microsoft-… .NET Interactive: https://github.com/dotnet/interactive ... and now this.

I usually read up on various DevBlogs like: * https://devblogs.microsoft.com/dotnet/ * https://devblogs.microsoft.com/visualstudio/ * https://devblogs.microsoft.com/dotnet/author/toub/ (for perf improvements by .NET version) * https://dotnet.microsoft.com/en-us/apps/aspnet (of course!) But it takes a while to catch-up if you are not keeping up-to-date on what is happening or coding in C#/.NET on a day-to-day basis

Seems Visual Studio Code has them: https://devblogs.microsoft.com/visualstudio/streamlining-your-debuggin… But not XCode etc.? Upon further research, it seems XCode "almost" has it: https://stackoverflow.com/questions/41193479/xcode-is-it-possible-to-g… ... it is actually a feature of LLDB, but the IDE doesn't expose it nicely, so that means you manually have to set them in the debugger console, which is annoying but less so than clicking a million breakpoints: https://volonbolon-blog.tumblr.com/post/126507197542/grouping-breakpoi…

Why must this be a mutually-exclusive situation? You can have the source code debugger log messages to the output window without having to add logging statements and recompile the affected code. This is the 21st century. see visual studio's tracepoint functionality - works in native and .Net languages, https://devblogs.microsoft.com/visualstudio/tracepoints/ sure, if you want the logging messages available for perusal when deployed in production, then this won't help. Even better - use Hot Reload and tweak your code in the debugger - https://learn.microsoft.com/en-us/visualstudio/debugger/hot-reload?vie… [edit] GDB's equivalent to tracepoint is mentioned elsewhere in this thread - https://news.ycombinator.com/item?id=42147372

You can provision a VHDX on your pre-existing NTFS volume (IIRC VHDX overhead is <=1% for Hyper-V, not sure if that's still the case and/or applies to DevDrive). But yes, I would say an additional drive is ideal. I did just that to put games on DevDrive. https://devblogs.microsoft.com/visualstudio/devdrive/ https://learn.microsoft.com/en-us/windows/dev-drive/#set-up-options

Use modern IDEs with features like Just My Code, which already help a lot. https://learn.microsoft.com/en-us/visualstudio/debugger/just-my-code?v… Also, there are scenarios where debugging without optimizations isn't an option. The issue with std::move has been solved for a while and was a VC++ bug, not C++. https://devblogs.microsoft.com/visualstudio/a-year-of-cpp-improvements…

The same place you download the x86 build: visualstudio.com See: https://devblogs.microsoft.com/visualstudio/arm64-visual-studio-is-off…

I suppose one reason is that images can be stored in many different ways in memory. For OpenCV images in C++ the Visual Studio extension Image Watch is quite nice, I think it's been around for more than 15 years: https://marketplace.visualstudio.com/items?itemName=VisualCPPTeam.Imag… There's also a recent extension called Image Preview for path references: https://devblogs.microsoft.com/visualstudio/working-with-images-just-g…

A real shame. To me, VS for Mac seemed to be converging on the level of product functionality/quality I associate with VS on Windows, only for me to find that its going away. Seems like VS Code + C# Dev Kit is going to be the future [1]. I've been using VS/Mac for some MAUI and Xamarin development and, while I can probably continue to Maui in VS Code with C# Dev Kit and another extension, there doesn't appear to be a way forward for Xamarin. And for some reason I find VS Code, with all its extensions, about as friendly as Eclipse (which is to say, not much). I much prefer the kind of integrated, native experience that Visual Studio provides (and without the Electron bloat). [1] https://devblogs.microsoft.com/visualstudio/visual-studio-for-mac-reti…

The Microsoft announcement is here: https://devblogs.microsoft.com/visualstudio/visual-studio-for-mac-reti… Previous HN submission: https://news.ycombinator.com/item?id=37325427 Visual Studio 2022 announcement: https://devblogs.microsoft.com/visualstudio/visual-studio-2022/

Related news from June: https://devblogs.microsoft.com/visualstudio/announcing-csharp-dev-kit-…

VS Code isn't being discontinued for Mac - just Visual Studio. https://devblogs.microsoft.com/visualstudio/visual-studio-for-mac-reti…

> Well, for me it IS helpful when the code block doesn't fit on single screen and I have to scroll AND there are multiple levels of brackets. Maybe they'll port this feature to VS Code. I tried it out, solves the problem you mentioned. https://devblogs.microsoft.com/visualstudio/sticky-scroll-stay-in-the-…

You can, kind of. Visual Studio 2022 for Mac 17.0 supports Apple silicon. https://devblogs.microsoft.com/visualstudio/visual-studio-2022-for-mac…

A DESIGN WITH ALL-CAPS: https://devblogs.microsoft.com/visualstudio/a-design-with-all-caps/

VS for Mac: https://devblogs.microsoft.com/visualstudio/visual-studio-2022-for-mac…

Windows has this for time travel debugging : https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/tim… Visual studio also supports TTD https://devblogs.microsoft.com/visualstudio/introducing-time-travel-de…

Nothing will beat that time Microsoft decided to put all the Visual Studio menu text in caps. They've since regained their sanity. https://devblogs.microsoft.com/visualstudio/a-design-with-all-caps/

Visual Studio has supported Developer PowerShell for a while now, and it’s possible to load it into Windows Terminal. It’s just a set of arguments. This blog post explains them: https://devblogs.microsoft.com/visualstudio/say-hello-to-the-new-visua…

I haven't used it, but Microsoft is already offering machine learning based completions with IntelliCode [1]. See also the introductory blog post. [2] It also offers sharing refined predictions within teams. I think we will see some interesting developments in this domain over the next few years. [1] https://visualstudio.microsoft.com/services/intellicode/ [2] https://devblogs.microsoft.com/visualstudio/ai-assisted-intellisense-f…

I’m not sure if you can bring your own machine[1] with GitHub Codespaces, but you can with Visual Studio Codespaces, which has the same underlying tech/featureset. (Visual Studio Codespaces was known as Visual Studio Online until last week) it basically does exactly what you want, let’s you use your dedicated local resources on another machine or remotely via the browser or using VS Code proper. I work at Microsoft on Azure but not with VS Codespaces or with GitHub Codespaces — I’m just a big fan/user/beta tester. [1]: https://devblogs.microsoft.com/visualstudio/bring-your-own-machine-to-…

The Microsoft blog post, from Nik Molnar, wasn't linked by TC. It's here: https://devblogs.microsoft.com/visualstudio/introducing-visual-studio-…

Sometimes, the devs can sneak in a hidden fix. For example, remember back when VS 2012 made menus ALL CAPS? Officially, that was the brave new world everybody was supposed to live in (https://devblogs.microsoft.com/visualstudio/a-design-with-all-caps/). Users hated it with a passion. And then it turned out that there's an undocumented registry key to re-enable the old behavior, that was leaked without much fanfare (https://www.richard-banks.org/2012/06/how-to-prevent-visual-studio-201… It was never mentioned in any official documentation, but word of mouth spread it far and wide, and its existence probably spared the worst in terms of angry user rants. Ironically, the outcry over the caps was big enough that this setting eventually got an official checkbox in a major release sometime later, and then became the default behavior again.