If there is one thing that is painfull when using Visual Studio then it is renaming your project. I typically try to keep my projectnames in sync with my current understanding of the business domain. But as I gain new insights, it can happen that I need to rename these projects to align them with the ubiquitous language.
So far, I always used a manual approach where I typically do the following:
- Rename the project file
- Rename the folder
- Change the project references in other project
If there are a lot of projects that should be renamed, it is really cumbersome to do.
Project Renamer to the rescue! This global tool does all the things above (and more) for you.
To use it, first install it as a global tool:
dotnet tool install -g ModernRonin.ProjectRenamer
After the tool is installed, you can use it from the command line, in the directory of your solution:
renameproject <oldProjectName> <newProjectName>
After asking for confirmation, it will rename the project:
D:\Projects\Test\TextGuiApp>renameproject textguiapp filebrowser
Please review the following settings:
Project: textguiapp
found at: D:\Projects\Test\TextGuiApp\TextGuiApp\TextGuiApp.csproj
Rename to: filebrowser
at: D:\Projects\Test\TextGuiApp\filebrowser\filebrowser.csproj
VS Solution folder: none
exclude:
Paket in use: no
Run paket install: yes
Run build after rename: no
Create automatic commit: yes
Git version: git version 2.28.0.windows.1-----------------------------------------------
Do you want to continue with the rename operation? [Enter=Yes, any other key=No]
Analyzing references in your projects - depending on the number of projects this can take a bit...
Project `TextGuiApp\TextGuiApp.csproj` removed from the solution.
Project `filebrowser\filebrowser.csproj` added to the solution.
[master f8d7942] Renamed textguiapp to filebrowser
3 files changed, 23 insertions(+), 11 deletions(-)
rename {TextGuiApp => filebrowser}/Program.cs (100%)
rename TextGuiApp/TextGuiApp.csproj => filebrowser/filebrowser.csproj (100%)
A new git commit was created:
Remark: The tool only works when your code is committed in a (local) GIT repo.