Visual Studio 2022 – 17.5 Released
We’re excited to announce that Visual Studio 17.5 is now generally available. This release is full of updates that take friction out of your daily workflows making it easier for you stay in the zone while you code. Features like all-in-one search and intent-based suggestions help you move faster, while improved build and debug speeds ensure your IDE won’t slow you down.
For .NET and cloud developers, we’ve focused on improving the inner-loop dev experience. New .http/.rest files make it easier to test and iterate on your APIs directly in Visual Studio, while improved Dev Tunnels help streamline the configuration and management of your webhooks. We’ve also made it easier than ever to deploy your ASP.NET apps to containers.
Game developers can now view properties from base classes modified in an Unreal Blueprint asset without leaving the IDE. Visual Studio has improved the cross-platform development experience with a new remote file explorer, Linux Console output to the Integrated Terminal window, dev container improvements, and more.
Beyond individuals, Visual Studio also has new features to better support dev teams at scale, with exportable configuration files and a persistent update toggle helping ensure everyone on your team is working from the latest version of the tool.
This blog covers several of the top new features in Visual Studio 17.5—to see some in action, watch the Visual Studio 17.5 release video. As always lot of these features come straight from your feedback and suggestions. Your feedback is critical to help us make Visual Studio the best tool it can be!
Productivity
- All-in-one search
- Intent-based suggestions
- Debugger text visualization
- Faster .NET builds and debugger features
- Improved Razor and C# Experience
.NET and Cloud development
- API development inner-loop
- Improved Dev Tunnels configuration and management
- Containers and Azure
- Accessibility Checker
Modern C++ and game development
- Unreal Engine Blueprint References and Asset Inspector
- Macro Expansion Improvements
- C11 Atomics
- Native Arm64 Clang toolset
C++ Cross-platform and embedded development
Enterprise management
- Layout configuration management
- Winget integration
- Always update upon close
- Accessibility Feature – Adding Sounds in the Installer!
Read on to learn more about these new features.
IDE Productivity & Performance
Visual Studio’s new All-in-One Search, Intent-Based Suggestions, and Debug Visualizers are designed to boost your code navigation and understanding. With the emphasis on productivity, this release not only offers new functionalities but also reduces build and debug times, making your workflow faster and more efficient.
All-In-One Search
All-in-one-search provides users with a quick and easy way to find Visual Studio files, types, and members in your code. We’ve made significant improvements to the ordering and relevancy of results in our code search while removing the results limit without compromising on speed.
Code search now has a Preview Panel that supports code results for both C# and C++! The preview will automatically show when you perform a search so you can see the context of the selected result. You can change the panel orientation or toggle it on/off by selecting the panel icons at the top right of the window.
Enable All-In-One Search by going to Tools > Manage Preview Features > “New Visual Studio Search experience (restart required)”.
AI-Powered, Intent-Based Suggestions
Intent-Based Suggestions is a new feature that provides in-line suggestions in your editor based on your recent changes. The feature uses Machine Learning algorithms to understand the structure of repeated edits you’re trying to make to your code and suggest the change right in your flow, helping you code faster and more accurately. Try it out and experience the power of intent-based suggestions in your development workflow today!
Debugger text visualizers
We’ve improved the text visualizer with additional tooling and string manipulation options. You can now do URL Encode and Decode and Base64 Encode and Decode JWT more easily, while full theming means the text visualizer window will fit the look and feel of the rest of your IDE.
Faster .NET builds and debugger features
We have drastically improved incremental build performance by only building projects that had modifications while skipping projects that were unchanged. With Build Acceleration you can reduce incremental build times for SDK-style .NET projects by up to 80%.
We’ve also made significant performance improvements in the debugger by improving the response times of the threads window. This window is critical in debugging today’s multi-threaded applications. In this release, the thread window automatically scales with the number of threads, helping contribute to 2X faster response times compared to Visual Studio 17.4. We’ve also improved external source de-compilation speeds by up to 10X, making .NET module troubleshooting much more efficient.
Improved Razor and C# experience
To address the feedback about productivity and performance surrounding Razor and C#, we’ve focused on improving the Razor and C# experience, with support for code actions in Razor files, including some helpful shortcuts like “Remove Tag,” “Encode image in Base64,” and “Insert Image height/width.”
A lot of the feedback we received around Razor and C# editing focused on the Roslyn experience. We’ve prioritized improving performance in project configuration switching, speeding up code analysis recognition, and improving the typing experience to reduce UI delays.
Modern .NET and Cloud development
API development inner-loop
Back-end APIs and microservices play a critical part in powering modern web apps, yet for many, API development remains a pain point. Efficient development with APIs requires agility and the ability to iterate quickly. We’re on a mission to make it easier to work with APIs throughout the inner-loop lifecycle—from coding and building to debugging and testing your apps.
Our first step towards better, faster API development is the addition of .http/.rest files in ASP.NET Core Projects, along with an integrated HTTP client. These files act as terse definitions for your API endpoints, enabling you to “run” your APIs and manipulate various REST calls to iterate within parameters and see the outputs in a structured way—all from Visual Studio.
These .http/.rest files aren’t meant to replace integration and unit testing. Instead, they provide a new way to rapidly iterate on API development, as well as a common place to monitor the APIs your app may be using and investigate required inputs/outputs during development.
This is just our first step towards improving the quality-of-life for developers working with microservices in Visual Studio—stay tuned for future features in upcoming previews!
Improved Dev Tunnels configuration and management
Of course, APIs are just one way modern apps interact with each other—webhooks are also crucial for enabling information to automatically pass back and forth between different applications. Dev Tunnels play a crucial part in configuring webhooks during inner-loop processes, as they provide a way for public services to be pointed towards code that’s hosted locally on your machine. We’ve made it easier to set up Visual Studio dev tunnels by giving you more control over their configuration and creation.
This release makes it easier to manage and switch between your Dev Tunnels and specify which you want to use in any given debug session. Both features provide powerful inner-loop productivity gains for API developers in .NET, and we look forward to your feedback on them.
Containers and Azure
For .NET developers working on web apps and APIs, fast, simple container management is crucial to enabling productivity and efficiency. Visual Studio already has excellent support for deploying to services like Azure App Service and Azure Functions, but we want to extend that simplicity to container-based services like Azure Container Apps.
This release takes a significant step forward by enabling you to deploy your ASP.NET Core app to Azure Container Apps in just a few steps. Instead of relying on additional files to define your container content and build steps, you can now directly target Azure Container Apps through the Publish window and either use a pre-provisioned resource or have VS help you create one:
After creating your resource, you can leverage new .NET 7 SDK capabilities to build the container image directly using the SDK with no additional knowledge or files. This is a fast, easy way to get your code to cloud using existing, familiar tools and workflows.
Of course, with our Azure Publish capabilities, you can also choose how to deploy by selecting on-demand or have VS create a starter GitHub Actions workflow if your app is in a GitHub repository.
Accessibility Checker
Visual Studio now has an integrated Accessibility Checker that detects many common accessibility issues for XAML based desktop applications. The Accessibility Checker uses the same axe-windows engine as Accessibility Insights, which is the same accessibility testing tool the Visual Studio team uses for our own accessibility testing. The Accessibility Checker supports WPF, UWP, WinUI and MAUI (through WinUI). To access the Accessibility Checker, make sure XAML Hot Reload is enabled in the option page, then press the “Scan for Accessibility Issues” button in the XAML Live Visual Tree toolbar.
When the Accessibility Issues button is clicked, the axe-windows engine will scan the running application for accessibility issues and present them in the Accessibility Checker window. The window will list the Automation ID, Rule, Description, and a brief explanation of how to fix the issue for each item the axe-windows engine detects.
Modern C++ and Game Development
We’ve included several new productivity enhancements for C++ developers, whether you’re working on games, cross-platform, or embedded applications—including a UE Asset Inspector in Visual Studio, Hot Reload support for CMake projects, IntelliSense improvements for macro expansions, and much more. For a more in-depth overview, checkout the Visual Studio 2022 version 17.5 for C++ Developers blog post.
Unreal Engine Blueprint References and Asset Inspector
For Unreal Engine game developers, you can now view Blueprint references and associated assets directly in Visual Studio. To see Blueprint references, click on the CodeLens hints now appearing on top of C++ functions, classes, and properties. From there, you can click on the Blueprint CodeLens hint and select a reference to open the Asset Inspector. Learn more by reading our Unreal Engine Announcement Blogpost.
Macro Expansion Improvements
We’ve also added several improvements to IntelliSense macro expansion designed to provide more effective, appealing and easier to read macro expansions inside Quick Info. Not only have we added recursive expansion in more contexts, but you can also now copy the expansion to the clipboard or expand the macro inline through options in the IntelliSense pop-up window. In addition, Macro expansion inside quick info will now have a formatted display and monospaced font.
C11 Atomics
Users will be pleased to learn we’ve expanded our standard library features to include C11 atomics in MSVC. Initial support is only for lock-free atomics and can be found under the /experimental:c11atomics flag, in /std:c11 mode or later.
Native Arm64 Clang toolset
While Visual Studio 17.4 introduced Arm64 support, we’ve expanded Arm64 capabilities with native Arm64 Clang toolset in our LLVM workload, enabling native compilation on Arm64 machines.
C++ Cross-platform and embedded development
For cross-platform and embedded developers, we’ve added several new features that help streamline your workflows beyond Windows.
Linux Improvements
We have moved the Linux Console into the Integrated Terminal to make it easier to interact with the remote Linux Machine. The integrated console window allows you to provide input as well as seeing console output.
When you’re using a Dev Container for application development, you can now run them on remote machines. We have also added the ability to open an interactive shell in the running container in the Integrated Terminal.
New CMake capabilities
With this version of Visual Studio, we’ve also added several new CMake capabilities to speed up compiling workflows. You can now build and test multiple CMake targets at once from the CMake Targets View in Solution Explorer. We’ve also enabled hot reload for CMake projects and added support for the latest CMakePresets.json files, making it easy to share settings across your development and CI environments while ensuring consistency.
Concurrent serial port monitoring
Embedded developers who have more than one serial device, or TCP connection with SWO traces, will be happy to find they can now open more than one serial port monitor at a time.
Enterprise management
Deploying any application across a large enterprise brings unique challenges. Visual Studio has improved the experience for creating and managing offline layouts for deploying Visual Studio. We’ve also made it easier for developers to decide and control when updates are applied on their local machine.
Customizing a Layout using a .config file
It is now possible to use an exported configuration file to configure the contents of an offline layout. This capability was one of our top-voted Developer Community suggestions, and it requires the latest Visual Studio installer that ships with Visual Studio 17.5. To use this capability, first export a Visual Studio configuration file that you want to replicate in your layout, and run the following command:
vs_enterprise.exe --layout c:\layout --config c:\my.vsconfig --useLatestInstaller
This functionality extends all the way back to Visual Studio 2017 assuming you pass in the required --useLatestInstaller parameter. It’s also possible to add components to an existing layout. If you’ve already created a layout containing one workload, you can add configuration for additional components and workloads to that layout by using the exact same syntax above.
Winget integration
Visual Studio 2022 and 2019 are now supported and available on Winget, the Windows Package Manager tool. Going forward, all Visual Studio updates will now automatically be available on Winget as part of our release process.
By default, winget only installs the core Visual studio workload. However, you can take advantage of winget’s --override switch along our new --config switch and use winget to do a customized installation. For example:
winget install --id Microsoft.VisualStudio.2022.Community --override "--passive --config c:\my.vsconfig"
Please note that during the winget repo ownership transition, we’ve updated the existing directory structure to better reflect how we ship and maintain Visual Studio. This does mean that if you have existing scripts or commands that depend on the prior Winget directory structure or package identification, you may need to make a one-time fix to align with our changes.
Always Update on Close
It’s now possible to configure Visual Studio to automatically apply updates when it closes. This setting is configurable on a per instance basis of Visual Studio. You can, for example, set your Previews to check for updates when you close the Preview, but your regular production Visual Studio instance can continue to be updated on demand. You can find this option in the Tools > Options > Product Updates dialog. Read more about how to get the most out of updates for Visual Studio on Microsoft Learn.
Accessibility Feature – Adding Sounds in the Installer!
We are continuously improving the Visual Studio customization experience to help you be more productive. Many of you are probably using the recently added audio cues in the Visual Studio editor and now we have added audio cues to the Installer! The audio cue alerts the user that the operation was finished on the installer or that there was an error by playing a sound. This includes install, update, modify, and many other operations done by installer or any error dialogs while trying requested operation. This feature is on by default, but you can turn it off by following the instruction outlined here: Disable sounds in the installer – Visual Studio Feedback.
Share Your Feedback and Stay Connected!
As you use Visual Studio, let us know what you love, what you like, and where you’d like us to improve. You can share feedback with us via Developer Community: report any bugs or issues via report a problem and share your suggestions for new features or improvements to existing ones.
Stay connected with the Visual Studio team by following us on YouTube, Twitter, LinkedIn, Twitch and on Microsoft Learn.
As always, we appreciate the time you’ve spent reporting issues and hope you continue to give us feedback on how we’re doing and what we can improve.
Light
Dark
74 comments
Is build acceleration enabled by default or we need to turn it on explicitly via AccelerateBuildsInVisualStudio msbuild property?
It’s currently not enabled by default. Setting AccelerateBuildsInVisualStudio to true will enable it (in a Directory.Build.props file ideally, so it applies to all your projects). See https://aka.ms/vs-build-acceleration for more info on the feature, and share any questions/issues you have with it at https://github.com/dotnet/project-system/issues.
Visual Studio 2022 is such a memory hog,… GBs of RAM used for simple ASP.NET Core projects, and memory consumption skyrockets while debugging.
The Visual Studio is an old nag; it’s ripe for a complete rewrite, but it would be best if Rider were released under some catchy Microsoft brand… for example, Windows Studio. (Sorry!)
So much this. The debugging experience especially. Nothing tops the Flashy McFlashyface on shutdown because so many resources are consumed:
https://developercommunity.visualstudio.com/t/Visual-Studio-Debugger-Still-Takes-Forev/10237621
And don’t even get me started about Razor/Blazor development right now 😭 If it didn’t work so well in runtime/production I would easily be on another technology stack.
Here too,
several GB of RAM only to load and debug a solution with few projects, 100% CPU for minutes. Need a supercomputer to make normal tasks.
I can’t believe it! It’s indecent..
And if you close a solution and leave VS open for a couple of days without opening another solution, it only releases a small amount of that memory back to the OS. It releases more if you didn’t do any debugging.
Right now, I am debugging a solution from 11 years ago, with 103 .NET Framework 4.5 projects, one of them being Web Forms. It’s taking 2.6GB of memory on a 16GB system. At the same time, 4 different browser windows open, two of them running one MS Teams each, simultaneously, and a Server Studio window for IBM Informix access (that one is really a piece of work, let me tell you).
Don’t get me wrong, 2.6GB is a lot, but I think it’s within what’s considered acceptable. You could say it takes a lot for just a few, simple projects. But it scales well when things start to get thick and heavy. The whole things stays very much snappy throughout the time. I also noticed that if I just leave VS idle for 15 minutes, let’s say, while debugging, it releases some 400MB of RAM.
As a side note, I opened the latest version of VS 2019 a couple of days ago just out of curiosity, and it’s so slow compared to VS 2022, that I couldn’t stand it for very long.
There is a lot to improve, but there is also a lot to appreciate 🙂
Perhaps your experience with memory consumption is difference due to targeting .NET Framework (Full) 4.5; vs. .NET Core (v5, v6, v7).
This growing memory issue, in my view causes barrier to entry, as one must equip themselves with Rolls-Royce class computer to be in .NET “Core” eco-system, with Visual Studio 2022 being de-facto IDE.
Ease of use, productivity, etc… are all beneficial to choosing .NET “Core”, especially with the work on WebAssembly. However, not everyone starting with C#/.NET may have powerful computer, and may choose a different platform.
Currently Visual Studio 2022 run on .NET Framework (Full) runtime; maybe Microsoft could re-target (build) Visual Studio 2022 on .NET “Core” — and thus get many of the performance benefits incurred on .NET “Core” runtime.
I hope All-In-One Search can like ReSharper C++ “search in everywhere”, include code comment, not only files, types, and members
like this : https://www.jetbrains.com/resharper-cpp/features/#navigation-and-search
After updating Visual Studio for Mac to this new 17.5 release, I was missing the Android emulators + the My Mac (McCatalyst) in the debug menu of my MAUI project. Also the target-platform Android was not visible in the project properties.
My old (pre 17.5) .CSPROJ file contains the following configuration:
But when I generating a new 17.5 project the TargetFrameworks configuration was a little bit different:
The solution for me was to replace the TargetFrameworks value in my current project with the new (expected?) values.
Still no XAML designer for .NET MAUI projects.
Hi Johan, this is not currently on the roadmap, but we are investing in multiple ways to make creating your XAML UIs easier with different types of tooling including XAML Hot Reload, Live Preview, and more.
Anyone else having issues with their intellisense not working on their C++ project after having updates to 17.5 ? (I was on 17.4.4 previously where it worked nicely)
Hi Rasmus. Please log a feedback ticket on developer community so that the engineering team can take a look.
https://developercommunity.visualstudio.com/home
Hi Anthony, I have reported this here https://developercommunity.visualstudio.com/t/Intellisense-not-working-on-large-C-pr/10295025
Yes, I have, so I have to roll back 17.4.5
Yep – I’m running a multi CMake project as my main work environment, Intellisense completely broken after upgrade.
Is there documentation for what .http/.rest files are? You show an example of .http but I have no idea what a .rest file is.
Hi MgSam, we are working to get some docs created. In the next few days we should hopefully be posting a new blog post here. This support was inspired by this OSS VSCode extension https://marketplace.visualstudio.com/items?itemName=humao.rest-client. There’s some more info on the syntax there. We don’t currently support all the features of that language, but we are going to be closing the gaps soon.
Pretty disappointing to see no love spent on SQL, even simple things like “go to definition” or “find all references” don’t work in SQL files
1. “Improved Razor and C# experience”. Did you fix triple quotes in Razor Editor issue? https://developercommunity.visualstudio.com/t/Triple-quotes-string-does-not-work-in-Ra/10202001 (And why did you close it without _any_ link to “another” post?)
2. “Brace Pair Colorization”. It’s awful. Deep blue color on black theme? Really? Green parenthesis? Are you kidding? Switched back to “Rainbow Braces” extension – it’s just splendid (btw for “What’s new” screenshot you used Rainbow Braces extension’s colors).
Hi Eugene. The triple quotes issue in Razor hasn’t been fixed yet but is being tracked on GitHub at https://github.com/dotnet/razor/issues/7084. It looks like the feedback issue was closed without adding that link. I updated the feedback issue to add the link. Sorry about that!
Daniel, thanks for the link! Will track it! 🙂
Hey Eugene, thank you for the feedback on Brace Pair Colorization. We’re currently working with the design team on changing some of the colors as well as adding an option for developers to customize the braces colors. We’re hoping to make those changes available in the next Preview version.
Also when I create, say, *.sql file, then editor creates a tab with it but immediately switches to another tab. Have to activate SQL tab myself.
I don’t see any updates on a Windows on ARM machine 🙁
False alarm, it just appeared!
What is your impression of Visual Studio on Windows ARM?
Those new ARM-based laptops are looking good…
When will Visual Studio fix switching between CMake view and Folder view and make them separate tabs. Its such a pain to just switch between to them.
When in solution mode, Solution Explorer supports creating as many new views for the given solution via context menu > “New Solution Explorer View”. This is not currently available for Open Folder mode (used by CMake). I’ve opened a suggestion ticket for this – please upvote: https://developercommunity.visualstudio.com/t/New-Solution-Explorer-View-should-also/10288348
Marian: Ohh, is opening a CMake project now separated out from Open Folder? Previously, to open a CMake project, one would naturally expect to go to File | Open | Project, and then choose the CMakeLists.txt file, but that didn’t actually work. On the other hand, to merely open a folder like VS Code for browsing, one would expect to do File | Open | Folder, except that actually opens a project 🙃. That was sooo confusing. So if “Open Folder” now just opens a folder, and “Open Project” now also properly can open a CMake project, that’s a very intuitive improvement.
I know there was talk of finally integrating Visualizers into the VS Extension model instead of them being their own separate API. Has that work now happened? Are there docs?
new VS 17.5 breaks older version of EF. Now I can’t use the option update from database, the update wizard keep on asking me to choose my data connection.
I have the same problem!
Same for me. It works in VS 2019, but VS 2022 17.5 I get an error message.
Something like this: https://stackoverflow.com/questions/61776217/visual-studio-2019-unable-to-convert-runtime-connection-string-to-its-design-tim
I have the same issue. Also if I try to search for the edmx file using the new All In One search experience – when I click on the search result to open that file- it says “The document is already open. Do you want to close it?” after which it does not let me navigate to the file (I can only get to it by scrolling to it now in Solution Explorer). I assume it thinks it is open as it is being displayed in the new search preview area editor.
Thank you for reporting this issue. Can you log a developer community bug and drop the link here in the comments so I can follow up with the product team and others can add their own data to the issue?
https://developercommunity.visualstudio.com/
Same for me in 17.5.
Had to downgrade to 17.4.5
For me release 17.5 has been one big disaster.
– bind:after bug with Blazor
– not able to update database with older EF version (database first).
Nothing left for me than to uninstall and go back to 17.4 orso.
I wish the devs would give more priority to making the product stable, than to add new features. Intellisense is 90% of the time broken. Error list is always full of bullshit, have to find the real errors in the compilation output, automatic aligning the code with ctrl-k-d? Well good luck with Blazor code. Aligning is wrong on all kind of places.
Sorry I just have to rant. Just way too many problems with VS. Get your shit right.
– Blazor / Razor is just one big disaster in regards to Intellisense, Syntax Highlighting and Error detection and has been for a loooong time :-/
– Update from Database EF Framework is just weird how that slipped through. But i guess that everyone is so busy looking at and working with Core that they neglegted to check regression in .NET Framework solutions. I’m still sad that Visual Studio doesn’t offer any UI / tools for DB First scenarios except some obscure Command line 🙁
The bind:after issue is being fixed in a servicing release of the .NET sdk. See here for more info: https://github.com/dotnet/razor/issues/8315#issuecomment-1447219503
I’m not 100% sure it was the 17.5 update because I bounce between 17.4 and 17.5 Preview versions but for several weeks now the build process for solutions goes off in the weeds, at least once a day, and never comes back. Doesn’t matter what solutions I load or how many projects, I start a build and it starts building projects and then at some point the build stops responding and never comes back. Have to restart VS at that point. Might be related to multiple VS instances running but something has definitely broken. Even did a VS repair (because Report a Problem stopped working) and the problem persists. Unfortunately you have no way of knowing that things have gone wrong because VS just shows the build progress indicator and the last message from the build. Unless you’re monitoring the build time then you might not realize it is hung. I have a solution that builds in about 15 seconds but ran for over 4 minutes before I terminated it.
I would report the bug but Developer Community always does the same thing: misunderstands the problem even though you provided clear steps, blames your configuration, asks for duplicate steps (even if you provided them) and then closes the issue as not reproducible. If I could reproduce it then I would avoid doing whatever is causing the problem in the first place. It is basically a waste of time to report it.
That is a common issue in 17.4 – the build sometimes ‘freeze’ and it has to be stopped and VS restarted.. 🙁
Great update – but note I am only able to do editing in the ‘All-In-One Search’ Code search preview area if I filter to “files”. Items returned under the categories of “types” or “members” return only an uneditable readonly preview. As the default ctrl-T can return any of those three for a search phrase it feels inconsitent and confusing that only some of the returned results are editable – and felt for a long time like nothing was editable (until I noticed the above pattern). Is that a bug or intended?
Hello Ian, thank you for sharing feedback on the consistency of the editing experience in the preview panel! Would you please provide more insights on the editing capabilities you’d like to use in the preview while searching?
Hi, do you know if this new version improves something about using R with visual studio? I use an OSX M1 processor and despite often experiencing problems with Visual studio correctly connecting to all the extension/accessories run to be able to connect to the R shell correctly. Recently I have also experienced visual studio no exporting figures generated in an R code. None of these problems happen while using Rstudio, so Visual Studio still has a lot to improve to convince R users. It is very annoying to have to troubleshoot something different almost every day to make R work in Visual Studio without problems, and a few days later it is not working again because of the same reasons or something else.
“support for the latest CMakePresets.json files” ?
Nope, you are supporting version 5 while version 6 was released in November 2022…
The new search is great–and very fast. Alas, it isn’t searching .vue files.
Hi,
After updating MS Visual Studio to version 17.5 I have one issue with the build of a target through CMakeLists.txt on Linux machine (WSL).
In MS Visual Studio 2022 17.5 is now absent the option –target in the command line.
I think that is the reason why I am unable to build any target on a remote Linux machine.
This option at least still exists in the build from MSVS 2019.
I have only CMakeSettings.json file, no additional settings in other json-files.
How it looks in my MSVS output window:
Starting copying files to the remote machine.
Finished copying files (elapsed time 00h:00m:00s:419ms).
cd $HOME/MyProject/build;/usr/local/bin/cmake –build $HOME/MyProject/build –clean-first –config Debug;
[1/1] Cleaning all built files…
Cleaning… 0 files.
ninja: no work to do.
How to resolve this problem?
Thanks.
Please let Dan Roth and Javier know the bind:after feature in blazor is now broken *in the SDK* again (not just Intellisense). This updated SDK must not get pushed out to Azure or any build servers or production apps will start to fail.
The code on Javier’s page here will break (not compile) if pasted into a Blazor Server app:
https://github.com/javiercn/BindGetSetAfter701/blob/main/BindGetSetAfter701/Client/Pages/Index.razor
Regards,
David
The bind:after issue is being fixed in a servicing release of the .NET sdk. See here for more info: https://github.com/dotnet/razor/issues/8315#issuecomment-1447219503
When can we expect a new UI? The current one UI design gives me feeling that I was using Office 2003.
Please no new UI… most of us use VS professionally, it needs to be efficient, not look flashy.
I’m not against evolutionary improvements to the UI, there’s definitely room for it. But given how pretty much every other software UI overhaul of the past 15 years turned out, I fear I know exactly where it would be going: hiding or removing 90% of functionality because “it could be confusing” to someone, adding 2-3 clicks and levels of indirection to every action (see Windows 11), and spreading everything out over so much whitespace that you’ll be spending half of your workday scrolling.
yes, please NO new UI.
When I click on a variable in an Angular template, it does not highlight other usages of that variable, and I cannot “Find All References” for that variable, like I can when I’m clicking on the same variable in the TypeScript code. Am I doing something wrong, or is this just something Visual Studio cannot do yet?
Also, if I move the template into the component declaration TypeScript file, it gets worse. Then it does not even recognize it as HTML anymore. It’s just a plain-text string then. So that doesn’t solve the problem.
We don’t need more features, we need a more stable IDE
After updating to Visual Studio 17.5 when I try to update my database in Entity Framework edmx file it always ask to specify the connection string.. it is something that was working well before for many years.
I have the same problem
Ditto! Anyone find a solution to this?
Don’t know if this is the same issue, but we have some EF 4 that we can no longer do a model update from the database, as EF 5 is the earliest version that is allowed. We were not expecting a point release to have a dropping of support.
Hey Chris , I Am Using EF 6 But I Have Same Issue.
Visual Studio 2022 Community (64-bit) Version 17.5.1
Blazor Standard Templates
.Net 7.0 Blazor WebAssembly Hosted RELEASE build is getting blocked by my managed anti-virus.
.Net 7.0 Blazor WebAssembly Hosted DEBUG builds OK.
.Net 6.0 Blazor WebAssembly Hosted DEBUG builds OK.
.Net 6.0 Blazor WebAssembly Hosted RELEASE builds OK.
.Net 7.0 Blazor WebAssembly Standalone RELEASE builds OK.
Anit-Virus Message
The file has been quarantined.C:\Temp4\BlazorNet7\BlazorNet7\Client\obj\Release\net7.0\BlazorNet7.Client.dll is malware of type Gen:Variant.Marsilia.26982
Testing Update
Workaround Solution Summary: Properties: Build > General > Optimize code > Untick ‘Release’
Details
ERROR: Could not find the “C:\….\BlazorNet7.Client.dll”.
Project: BlazorNet7.CLient
File: Microsoft.NET.Sdk.BlazorWebAssembly.6_0.targets
Line 238:- <GZipCompress …
Something has happened with this release. You could start 17.4 fairly quickly, but 17.5 takes 10-30 seconds longer to start. Why is this?
The long start time seems to have gone in 17.5.1.
Nice new features. But, this new update of VS hogs up on the CPU. I have a 6 Cores 12 Threads machine. Still, everything feels so slow. Earlier, I had a 4 Cores 4 Threads i5 3rd Gen machine with which I ran VS 2015 2017 and 2019 from 2016 to 2021 with no issues. Please we don’t need more features in VS, we need VS to be efficient memory and CPU wise. Also, I don’t know why I don’t like Razor Pages and Blazor.
Procesador Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz, 2901 Mhz, 6 procesadores principales, 6 procesadores lógicos
Memoria física instalada (RAM) 32,0 GB
Microsoft Visual Studio Professional 2022 (64 bits) – Current w license
Versión 17.5.1
using .net framework 4.7.2 small solution…
73% CPU 5.5GB just when project loaded…
17.4 works fine, my pc was silent, now Ive fan running high all day..
“Something is rotten in the state of Denmark”
We have systems with entity framework 4.0 and it seems like 17.5.1 no longer supports this version of enity framework (being able to update a model from the database). Is there any workaround for this?
Thanks,
After Updating The edmx file not updating ,
Integrated http client, nice feature. I use daily the REST Client extension in VS Code. But I will by happy to use it directly inside Visual Studio. But 3 things are missing for me :
1) having variables who read values from Windows Environment Variables (for passwords)
2) having a notion of environment (production, test, dev, …) with proper variables
3) read body of request from a file (if it is not allready possible)
Any chance to see theses improvements one day ?
What happened to sticky scroll from the 17.5 preview?
I’ve just updated to 17.5.3.
The Find All in Current Project and Entire Solution seems to be broken.
First, a simple search of my php files is very slow compared to how it used to be and something with more text it doesn’t ever seem to find even though I’m looking at it in the php file.
I’ve never had problems like this in Visual Studio Community 2022.
Can I remove the update?
Thanks,
Jeffery
Is SSDT ready for VS 2022 – 17.5? We use VS mostly for SSIS package design and implementation.