Welcome to the Lounge

The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.

I do that all the time.
It goes in my bin, which permanently deletes it after 30 days.
I keep pretty much all work mail and most personal mail, but newsletters, order confirmations, build status updates, etc. go right into the bin folder (after having read them).
Or mail like "here's my contact details". I create a Contact, save the details there and delete the mail.
Sometimes even mails with attachments that I should read. I download the attachment, put it where it belongs (like source control or ticketing system) and delete the mail.
That said, I still nearly have around 3000 mails saved since 2010.

Everything before that time somehow got lost when I took a new email address and apparently(?) purged my old account.
I have no idea what happened, but it was quite a shock when I found out at the time.
However, I can't say I ever missed any of those deleted mails, I think we keep them mostly for a little piece of mind and "just in case".

Some of us are AR (anally retentive) about cleaning up our work space. Besides the automatic 30 day cleanup I will happily empty the trash and junk folders whenever I like, often when the hind brain is working on a problem.

Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP

It seems that in VS2017, you cannot (easily) clear the MRU list. It appears that some bright spark at MS decided that the MRU is VERY important and needs to be protected.

Clear MRU list in Visual Studio 2017"The increase the isolation and resilience of VS 2017, it uses now a private registry hive. "
By WHY??? It's just a list of files that you opened. Why does this need to be protected????

In the end, it sounds like you're going to have to uninstall/reinstall VS2017...

".45 ACP - because shooting twice is just silly" - JSOP, 2010-----You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010-----When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013

It might be that they integrated the MRU totally in with the win7 shell MRU stuff. It kinda looks like it based on the jumplist. If so, you couldn't clear it without also clearing those files out of your "Recent Documents" and other areas where doc history is kept.

I'm not sure they do it this way. I've never looked into it. But it's a possibility. Maybe try clearing your recent docs if windows will let you. see what happens.

When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.

What you have to remember is that if what you think is important differs from what a marketing moron at ms thinks important, then you have got your priorities wrong, and need to just do as you're told.

go to Tools->Options, select the Environment/General option. Set 'Items to show in recently used files list' to 1 (I said it wasn't quite clearing the list...) & press OK. Then if you want to get back to 10, change it again...

Such a thing I did, sort of, before the company went VM for almost every user. This ran from an area I carved out on a local server.

My applications would be installed and updated by the same application - it was actually a launcher which, prior to launching the application, would check a script of instructions.

For simple updates, it would compare file dates - but it also allowed roll-back, adding and deleting files and folders, and even total removal of itself, all based upon a script. One of the items in the script that was updated was the script, itself, which allowed not only for updates being added for newly installed files (for example) but even recursive construction. Uploading a new script version would trigger rerunning the entire procedure (unless disabled).

In case you do build your updater, you may wish to incorporate any of the above you may not yet have considered adding (or shun them, as appropriate).

With the VM's it all went away as the keepers of the server and it's "Golden Image" became the method for updates. Very much less efficient.