Iĭo not really have a lot of free time to spend on this, but am totally open to PRs (hint hint). Some of them are hard limitations, meaning they are unlikely to go away, others are soft limitations, meaning they exist only because I simply have not gotten round to fix them yet. To do this, you prefix the new name with a relative folder. ![]() Since version 2.1.0, the tool also allows you to move projects. If anything goes wrong, all changes will be discarded. ![]() a commit of the form Renamed to will be created automatically, unless you specified a flag -no-commit.if you specified a flag -build, a dotnet build will be run just to be totally safe that everything worked well, for very cautious/diligent people :-).if you use paket as a local dotnet tool (see Soft Limitations), paket install will be run, unless you specified the flag -no-paket.all tags in other projects in your solution referencing the project will be adjusted.renaming is done with git mv so it keeps your history intact.the folder of the project file will be renamed.Renameproject ModernRonin.ProjectRenamer ModernRonin.RenameProject You use it from the command line, in the directory of your solution: bugfix: if a required tool like git cannot be found, give a proper error message.bugfix: if a project is not in a solution folder, the tools works now, too.breaking change: instead of asking the user interactively, behavior is now controlled via commandline switches.bugfix: VS solution folders containing spaces don't crash the tool anymore.bugfix: when called with unnamed arguments, old project name now is understood to come before new project name (before it was the wrong way round).feature: the detected git version is displayed in review.feature: the detected VS solution folder is displayed in review.feature: you can specify a directory to exclude from project reference updates.feature: you can move projects to different folders now instead of just renaming them.bugfix: projects in paths containing whitespace no longer crash the dotnet commands thanks to for reporting the bug.bugfix: fixed another whitespace related scenario thanks to for reporting the bug.bugfix: fixed a bug concerning nested solution folders thanks to for reporting the bug.bugfix: fixed issue when paths contained whitespace thanks to for the PR - the first contribution from anyone else :-).bugfix: tool can be used on *nix platforms now without crashing thanks to for the PR!.bugfix: fixed a potential deadlock thanks to for the PR!.feature: tool can be used on VB projects, too thanks to for the PR!.bugfix: all Import Project directives with relative paths will be correctly adjusted now. ![]() When I publish a new version, I always post at my blog under the renameproject tag, aside from updating this readme here. (You could install it as a local tool, too, but given what it does this does not really make a lot of sense.)ĭotnet tool update -global ModernRonin.ProjectRenamer Renameproject is intended to be used as a global dotnet tool. ![]() Simple drag-and-drops that only change the solution file, I hope this is acceptable. Workaround is simply to move the nested solution folder to top-level via VS, run the tool, and then move the solution folder back seeing as this is two your solution does not contain nested solution folders - the tool currently has an issue with that and will fail until I find the time to fix that, the.you have dotnetcore 3.1 or above (**note: as we are approaching the release of net7, I will soon upgrade the tool to net6).you don't have more than one solution file (.your csproj files have the same name as the folder in which they reside together with accompanying source code.you use git as a repository and have git(the executable) on your PATH.This tool takes care of this for you, provided your use-case follows a set of fairly common practices: How often have you felt the need to rename or move a C# (or VB) project? If you have come here, then you know that the most important existing IDE for C#, Visual Studio,ĭoes not really support this scenario very well.
0 Comments
Leave a Reply. |