Visual Studio move project to a different folder

Question

How do I move a project to a different folder in Visual Studio  I am used to this structure in my projects   -- app ---- Project Something ---- Project SomethingElse   I want to rename the whole namespace SomethingElse to SomethingNew  what s the best way to do that  without manually going into  sln file

User · Answer

Close your solution in VS2012 Move your project to the new location Open your solution Select the project that failed to load In the Properties tool window  there an editable    File path    entry that allows you to select the new project location Set the new path Right click on the project and click reload

User · Answer

No sure why all answers have overlooked at the most simple solution  Just run the  quot Command Prompt app quot   in the windows bar search for CMD and it will appear automatically  then just type the following  command  change the path where relevant for your own case   robocopy  E C  Users Peter source repos D  Peter repos  What robocopy does is to  quot copies file data from one location to another  quot  and the  quot secret source quot  is the   E that means   quot Copies subdirectories  This option automatically includes empty directories  quot  Enjoy     -

User · Answer

Summary   rename-and-move in VS2019 with git  retaining git history  leveraging R  a bit  automatic dependent project reference updating  important for sln s with many projects  we have  gt 200  I have been using the following steps to rename-and-move C  projects in Visual Studio 2019   This process uses R  to adjust namespaces   The git history is retained by doing a  quot git mv quot   avoiding add delete history drop   Two phases   1  rename the project in place and 2  move the project   Uses tip from base2 re unloading projects   Rename  VS   Solution Explorer   right-click project   Rename  e g   Utils Foo to Foo   VS   Solution Explorer   right-click project   Properties   change assembly name  default namespace and Assembly Information fields Do 1 and 2 for corresponding test project  e g   Utils Foo Tests  VS   Solution Explorer   right-click projects  production and test    Refactor   Adjust Namespaces XAML files that use the project may need to be updated  manually or with an appropriate global search and replace  Rebuild All Commit    to commit changes before moves   Note   The folder in Windows Explorer remains the old name to this point  e g   Utils Foo    This is fixed in the move steps  Move This method  1  retains git history  2  leverages R  to adjust namespaces atomically and 3  updates dependent projects en masse  avoids tedious manual editing of dependent sln and csproj files    unload all the projects in the solution  so that removal of the target project does not trigger changes in dependent projects  VS   select all solution folders under the Solution   right-click Unload Projects  move folders using git  so history is maintained    a  open Developer Command Prompt for 2019 b  git status  to illustrate    nothing to commit  working tree clean     c  git mv the project e g   git mv  quot C  Code foo foo Utils Foo quot   quot C  Code Foo quot  d  git status to view verify change  remove the project  VS   Solution Explorer   select project   right-click   Remove  since all projects are unloaded  this will correctly NOT remove the references to it in dependent projects   re-add the project  to the new location in the tree in Solution Explorer   a  VS   Solution Explorer   select target parent folder   right-click   Add   Existing Project  reload all projects  IMPORTANT   Confirm that   csproj files for dependent projects have been updated   VS   Team Explorer   Changes   double-click any dependent csproj listed   inspect-verify ProjectReference path change   Manually fix paths in the single moved   csproj file  Use Notepad    or other text editor  to fix the paths   Often this can be done with a simple search-and-replace  e g                to          This will update    a  GlobalAssmeblyInfo cs references b  paths to packages c  paths to Dependency Validation diagram files d  paths to ruleset paths  e g    lt CodeAnalysisRuleSet gt             SolutionDependencyValidation IgnoreWarnings ruleset lt  CodeAnalysisRuleSet gt    Close and re-Open the solution  to get the project references into good shape   Save All  Close Solution  I prefer to delete bin and obj folders to be clean of history  Re-open Solution  Validate  a  VS   Team Explorer   Changes i  should see Staged Changes that reveal the files that moved ii  should see dependent projects    csproj  that were nicely updated review the csproj diffs and notice that the paths have been beautifully updated    this is the magic that avoids laboriously manually updating the csproj files using a text editor  b  in Windows Explorer  verify old location is empty c  Clean Solution  Rebuild Solution  Run unit tests  Launch apps in sln   Commit

User · Answer

It s easy in VS2012  just use the change mapping feature    Create the folder where you want the solution to be moved to    Check-in all your project files  if you want to keep you changes   or rollback any checked out files  Close the solution  Open the Source Control Explorer  Right-click the solution  and select  Advanced -  Remove Mapping     Change the  Local Folder  value to the one you created in step  1  Select  Change   Open the solution by double-clicking it in the source control explorer

User · Answer

in visual studio comunity 2019  i did what Victor David Francisco Enrique says  but needed only to delete the  vs invisbile folder

User · Answer

I tried the suggestion to remove and re-add the project  but then fixing up dependencies can be a pain   I use this approach    Move the project folder   If the project is in source control  do the move using source control commands   Edit the solution file in a text editor  There should be only one path that you need to change

User · Answer

I figured out this try this it worked for me   In visual studio 2017 community edition it creates a project at this path  C  Users mark source repos mipmaps mipmaps  This will create a access to file is denied issue  Now  you can fix that this way   close your visual studio process  Then  find your project and copy the project folder But  first make a Sub-folder Named Projects inside of your visual studio 2017 folder in documents  Next  paste the project folder inside of your visual studio 2017 Project folder not the main visual studio 2017 folder it should go into the Sub-folder called Projects  Next  restart Visual studio 2017 Then  choose Open project Solution Then  find your project you pasted in your visual studio 2017 Projects folder Then clean the Project and rebuild it   It  should build and compile just fine  Hope  this Helped out anybody else  Not to sure why Microsoft thought building your projects in a path where it needs write permissions is beyond me

User · Answer

Copy the project folder to new destination Remove your project from solution  Right-click the project in  Solution Explorer  and choose  Remove   Then add existing project to solution  Right-click the project in  Solution Explorer  and choose  Add  then  Existing project   Change path to  packages  folder in  YourProjectName csproj  file  Open in notepad and change paths for linked packages

User · Answer

Group related projects together using solution folders  See http   msdn microsoft com en-us library vstudio c6c756s6 v vs 100  aspx

User · Answer

Remove the project from your solution by right-clicking it in the Solution Explorer window and choosing Remove   Move the entire project folder  including subdirectories wherever you want it to go   Add the project back to your solution   Namespace names is something completely different  just edit the source code

User · Answer

In VS 2015   Unload your project in the solution explorer Create a new solution Copy the projects to the new solution s folder Right click the solution  add existing project  If you use some framework such as MVC  you may need to add the reference in the reference manager

User · Answer

I wanted the changes in Git to be shown as moves renames instead of delete  amp  adds  So I did a combo of the above and this post   mkdir subdirectory git mv -k       subdirectory   check to make sure everything moved  see below  git commit   And adjust the paths of the projects and of the assemblies from the nuget Pkg s in the sln file via a text editor

User · Answer

I had the same problem  I solved with move the references and in less than 15 minutes  without change the references   For me the solution was simple    Move your files where you need  Delete the folder with name  vs  Must be as not visible folder  Open the solution file   sln  using a simple editor like note or notepad    Change the reference where your file is  using the following structure  if you put your project in the same folder remove the previous folder or the reference        if you put in a above folder add the reference       or the name of the folder  Save the file with the changes  Open the project file   csproj  and do the same  remove or add the reference  Save the changes  Open the solution file    Examples   In solution file   sln    Original  Project   FAE04EC0-301F-11D3-BF4B-00C04F79EFBC       PATH1 UI    ScannerPDF PATH1 UI PATH1 UI csproj     A26438AD-E428-4AE4-8AB8-A5D6933E2D7B   Project   FAE04EC0-301F-11D3-BF4B-00C04F79EFBC       PATH1 DataService    ScannerPDF PATH1 DataService PATH1 DataService csproj     ED5A561B-3674-4613-ADE5-B13661146E2E    New  Project   FAE04EC0-301F-11D3-BF4B-00C04F79EFBC       PATH1 MX UI    PATH1 MX UI PATH1 UI csproj     A26438AD-E428-4AE4-8AB8-A5D6933E2D7B   Project   FAE04EC0-301F-11D3-BF4B-00C04F79EFBC       PATH1 DataService    PATH1 DataService PATH1 DataService csproj     ED5A561B-3674-4613-ADE5-B13661146E2E     In project file    Original    New    Original reference       lib RCWF 2018 1 220 40 TelerikCommon dll  New reference     lib RCWF 2018 1 220 40 TelerikCommon dll

User · Answer

This worked for me vb2019  I copied my source project folder  I then pasted the project  and renamed the the folder to whatever  In order to break the ties back to the source project folder  I temporarily renamed the source folder  I opened my destination project  The paths to the forms and modules were re-discovered in the local folder  I went through all my forms and modules to make sure they were working  I ran the project  I closed the project  I renamed the source project folder back to is t original name  I can open both projects at the same time without errors

User · Answer

What worked for me was to    Remove the project from the solution  Edit the project file with a text editor  Update all relative paths to the  packages   In my case I had to change    packages to          packages since I moved the project to a deeper folder  Load the project back into the solution

[visual-studio] Visual Studio move project to a different folder

Examples related to visual-studio

Examples related to visual-studio-2008