Visual Studio closes all opened scripts when creating new script in Unity

I don't know if this is a Visual Studio issue, or a Unity issue.

How can I stop this from happening?

 

The act of creating a new script causes Unity to re-execute the "Assets -> Open C# Step," which wipes out the

.csproj

and

.sln

files and regenerates them.

AFAIK there's no way to both have this very-handy functionality and suppress it from triggering each time you add a new script.

When I pop back to Unity to create a new script, I just always save all scripts in Visual Studio, or even just close VS completely.

 

Well then let me ask you this -

Is there any way to batch open the "recent files" list in Visual Studio? Also, is there a way to increase that list, as it seems to be limited to 10 (I typically have a lot more than that open at any given time)?

 

These questions both seem better suited to google. I know I have tweaked the count of recent files, but the last time I even used recent files in VS was 1999 or 2000.

Do you know about Command-Period (or Ctrl-period) to search stuff in VS? it's SUPER-powerful. It's that little search box in the upper right. That is almost 100% of how I navigate in VS. It finds methods, variables, filenames, classes, etc.

 

Point taken

That doesn't mean other people don't use it.

No, I didn't know that, so thanks for the heads up ;-)

OH, and quit stalkin me dude.. (that was just a joke)

 

I found this earlier, and was curious if this is related to what I am experiencing -

https://docs.microsoft.com/en-us/vi...oads-or-visual-studio-losing-all-open-windows

I read the article, and verified that I do have the proper targeting packs installed.

Something else that bothers me is that this is a recent development. I don't remember VS closing all my tabs when I first started working with Unity a few months ago. That article seems to suggest that this isn't intended behavior..

I'm on 2021.2.16f1, if that makes any difference.


EDIT: This does not happen in VS 2019. I'm currently using VS2022 preview, but ran a test in 2019.

 

+1 for it not happening in VS2019.
This is very frustrating, especially in the early stages of a project, where I'm working on a script and find that, oh, I need to make another one. Oop, have to re-open them all again. Ah, need another script. Sigh

 

Try using the full release of VS 2022, instead of the preview. That seems to function correctly, at least for me.

 

I am using the full release. v17.2.0
I did try the preview, just to see if maybe that worked for me, for some reason. It did not. Reverting back to full release.

Edit: I've updated packages, restarted, re-created csproj and sln files, it's still closing scripts when I make a new one

 

have same problem, now way to fix it?

 

This seems to be a Visual Studio issue. This is happening to me since updating Visual studio, while I haven't changed Unity versions on any of my projects. This includes projects across both Unity 2020 and 2021.

So I'm guessing this is something in the recent update causing this. 17.2 seems a bit shonky overall, as I've had other various features of it crash or not work on me as well.

Hopefully a future update fixes this.

 

My fix was to just go back to VS 2019

 

There is a Visual Studio 2022 v17.2.1. Was wondering if the patch update fixes this issue? (The 17.2.32516 is referred to as 17.2.1 patch release build number).

 

I just updated and unfortunately, the issue still persists.

 

Same news here. It's infuriating. Back to Visual Studio 2019.

 

Ugh, I just uninstalled VS 2019, thinking there is no need to use it when VS 2022 is out.

 

Same Here.

 

Hello folks, sorry for that.

This issue is tracked here:
https://developercommunity.visualstudio.com/t/VS-Tools-for-Unity:-All-Opened-Files-Get/10041889

 

Hey thanks for the update.

The option provided in the work around doesn't seem to be present in the preview version listed in the the linked help ticket. Anything that's gotta be done to expose that option?

 

bump, same issue for me too

 

Yep, this is only happening in VS2022. I did not happen back in VS2019.

 

I recommend the free "Workspace Manager" VS extension as a little helper for people who need to keep working with VS2022. With it you can save all opened documents and load them conveniently.

 

A fix for this issue has been internally implemented and is being prepared for release. We'll update you once it becomes available for download.

 

Thanks!

 

Fixed in version 17.2.3.

A fix for this issue has been released! Install the most recent release from https://visualstudio.microsoft.com/downloads/.

Thank you for providing valuable feedback which has helped improve the product.

 

It works again! Thank you and also thank you OP for posting this thread!

 

Awesome, thanks!

 

Hello. It is reproduced with Unity 2021.3.14f1 and Visual Studio 17.4.1
It happens when existing cs file is duplicated within Unity with Ctrl+D keys, but not 100%.

 

@sailro Another repro step for this: in Visual Studio, save an opened script as "Save as...". Unity compiles, and all files are reverted.
Another repro: rename the class name, and specify you'd like rename the file as well.

These are a pretty frequent use case, quite annoying. Repros with 17.4.4