Open staffordkierandev opened 1 year ago
I have the same issue. Don't remember which version added this but it change my flow.
You probably are not actually using the extension.
Visual studio now has a built in AddQuickFile
feature. That overrideds the Shift+F2
look at you keyboard bindings
To use this extension with Shift F2
you need to set the NewEmptyFile
binding.
Description
I use AddAnyFile by pressing Shift+F2 and typing a file name. e.g. myclass.cs. In the past, this always created the correct file for me with the public scope. However I have just recently started using the extension with Visual Studio 2022 and alas, it seems to create new class files with the internal scope. Is there a way to revert back to the preferred behavior? I write a lot of decoupled injected code so seldom use internal.
Steps to reproduce
Expected behavior: A new c# class gets created scoped as public
Actual behavior: A new c# class gets created scoped as internal