Skip to main content

Visual studio 2019 + Resharper. Performance tweaks

Recently had to move from one pc to another and got a feeling that Visual studio got a bit slower on startup and project load.
In addition to that, the text became blurry, so I had to google what has changed recently and how to get back proper VS experience. 

Writing this post for myself to remember where to look at next time 😊

High resolution:

DPI problems on big screens are solved with a setting "optimize rendering for screens with different pixel densities. (Using build in search helps to find option without clicking here and there). 
As text suggested, right after restart everything got sharp again.

Visual studio settings:

The first improvements suggest I found was to disable options ‘reopen docs on solution load’ and ‘restore projects hierarchy’

The next set of options comes from preview features:

Autohide tool window and startup and ‘new git experience’ if you use git.

Resharper:

For those who use Resharper, jetbrains prepared a nice set of features you can enable to make vs faster, just change then to ‘fix silently’ and on each start, it will check and disable features.

Defender:

Exclude processes:
devenv.exe, msbuild.exe

Exclude resharper cache folder 
%LOCALAPPDATA%\JetBrains\Transient

Extra tip:

Force Visual Studio to perform garbage collection
"Ctrl+Shift+Alt+F12" + "Ctrl+Shift+Alt+F12"

Did it make my VS as fast as Visual studio Code? Nope. But I got back to what I used to have on a less powerful machine.

Links:
https://docs.microsoft.com/en-us/visualstudio/ide/visual-studio-performance-tips-and-tricks?view=vs-2019
https://www.jetbrains.com/help/resharper/Speeding_Up_ReSharper.html#resharper


Labels:

Comments

Post a Comment

Popular posts from this blog

Using MinIO as on premises object storage with .NET and S3 SDK

Ever tried to find a blob store that can work on-premises as well as in a cloud, support meta-data, scale well and have .NET client libraries? I did and stopped on MinIO . Well, honestly to my surprise I was quite limited in my choice. It's free, it's open-source, it can work on-premises and has helm charts for k8s. The best thing is that its S3 compatible, so if one day you move to the cloud the only thing you`ll need to change in your code is a connection string. The easiest way to start is by starting a docker image. Pull the image: docker pull minio/minio start for testing (data will be part of the container, so after a restart, all files will be gone docker run -p 9000:9000 minio/minio server /data Or start with a mapped image in windows: docker run -p 9000:9000 --name minio1 \ -v C:\data:/data \ minio/minio server /data When the server is up you can access it by http://127.0.0.1:9000/minio/login default user/password: minioadmin/minioadmin Working wi...
Post a Comment
Read more

Avoiding distributed transactions (DTC) with SQL Server and async code

Wrapping async code in transaction scope is not as straightforward as sync one. Let's say we have some simple code: await using (var connection = new SqlConnection(connectionString)) { await using var command = new SqlCommand("select 1", connection); await connection.OpenAsync(); await command.ExecuteScalarAsync(); } We can wrap it in transaction scope and test that it still works: using var ts = new TransactionScope(); await using (var connection = new SqlConnection(connectionString)) { await using var command = new SqlCommand("select 1", connection); await connection.OpenAsync(); await command.ExecuteScalarAsync(); } ts.Complete(); But if you try to run this code you will get: "A TransactionScope must be disposed on the same thread that it was created" exception.  The fix is easy: we need to add TransactionScopeAsyncFlowOption.Enabled option to the constructor: var options = new TransactionOptions { IsolationLevel = IsolationLevel.ReadCom...
Post a Comment
Read more

Fluent-Bit and Kibana in Kubernetes cluster or minikube

Agenda I`ll show how to setup a centralized logging solution running in k8s cluster that works beyond hello world examples.I`ll use local minikube but the same charts with adjustments could be used for normal k8s cluster (the real diff usually comes with usage of persistent storage). What you need to be installed: K8s Cluster (as I said, I use minikube ) Helm ( https://helm.sh/docs/intro/install/ ) Code: https://github.com/Vfialkin/vf-observability A bit of theory first: Let’s start with how logging works by default in Docker and Kubernetes. application log appender should forward logs to standard output, this way it will be passed to Docker container.  default container logging driver will forward them to Pod where logs are stored as JSON files (see: configure logging drivers ). There are other options for log drivers like  syslog, fluentd or splunk , but for now, I’ll limit scenario to default driver. at the end all those files will end-up in a node folde...
Post a Comment
Read more