Navigation:  »No topics above this level«

CopyWiz - Visual Studio Project Copy Wizard

Return to chapter overviewNext page

CopyWiz can perform one or more of the following operations on Microsoft Visual Studio (versions 5 through 2017), SQL Server Management Studio, Visual Studio Tools for Office, Embarcadero Delphi, C++Builder and RAD Studio (2007 through 10.1 Berlin), Delphi Prism, Intel C++ Compiler and Visual Fortran, and other Visual Studio Shell projects and solutions:


Copy a project or solution to a new location, optionally with a new name
Rename an existing project
Fix up project directories
Replace all GUIDs in a project


Important: Always backup your files before using the wizard, especially when renaming an existing project (the existing project files will be modified in this case).


Launch CopyWiz from the Windows Start menu, or by right-clicking on a project or solutions file in Explorer and choosing Copy with CopyWiz to copy or rename the project.  An add-in/extension for launching CopyWiz is also added to the Visual Studio .NET 2002 thru 2017 IDE during installation (if checked).  To enable the extension in Visual Studio 2015, choose Tools | Extensions and Updates on the menu, enable the CopyWiz extension, and restart Visual Studio. To enable the add-in in Visual Studio 2002 thru 2013, choose Tools | Add-In Manager on the menu and check CopyWiz Add-in (also check the Startup checkbox to make the add-in available each time the IDE is started).  Then, CopyWiz can be launched by choosing Tools | CopyWiz from the Visual Studio menu bar (CopyWiz will launch pre-populated with the filename of the current solution).


Step 1


Use the first wizard screen to select the project or solution file to process.  You can choose from a list of recent projects or enter or browse to choose a file.  CopyWiz supports .sln, .*proj (all extensions ending with proj), .oxygene, .vbp, .dsp, .vcp, and .ebp files.


Step 2


After choosing a project filename and clicking Next, CopyWiz parses the file to determine its name and displays the name on the second wizard step.  The following selections are provided:


Copy to a New Location? This option determines if the selected project or solution will be copied to a new location.  If Yes is chosen, a destination folder must be selected or entered (it will be created if it doesn't already exist), and the project and its files will be copied to the new location (the original project will not be modified).  If No is chosen, the selected project will be modified in place.


Rename? If copying, this option determines if the project filename and name will be changed when the project is copied. If not copying, this specifies how to rename an existing project.  In addition to changing all project name occurrences within the project files, all project filenames that are prefixed with the project name are modified to match the new project name (and any references to these files are also updated).


Fix Up Directories? If this question is answered Yes, when copying or renaming the project, the wizard also fixes up all absolute and relative paths and filenames in the project files.  Any absolute paths are first converted to paths that are relative to the project’s location; existing relative paths are converted to the minimum necessary relative path. This can be useful for updating existing projects to fix up include paths and file paths that were incorrectly specified as absolute paths or relative paths that specified more levels than necessary.  For instance, the following table shows how path/filename strings encountered in a project located at \app1\test1\source\project1 would be fixed up:


Original Value

Fixed Up Value













Point Relative Directories Back to Original Location? This option is enabled when copying to a new location and fixing up directories.  When copying to a new location, the wizard can either:


1)If Yes is chosen, make relative paths in the project point to their original path.  For instance, if a project was copied from \app1\source\test1 to \app1\test1\source, and one of the files in the project was located at ..\common (\app1\source\common), that path would be changed to ..\..\source\common in the copied project.  This choice can be handy for moving existing projects up or down one or more levels in your project directories.
2)If No is answered, leave the canonical relative path as it was after fixing up.  In the previous sample, the path would be copied as ..\common.  Since the path would no longer point to the original file, the files in the path \app1\source\common would also be copied to a new folder \app1\test1\common by CopyWiz.


Note: Paths that specify the location of the project’s executable filename or compatible EXE are always fixed up using option 2, regardless of how this question is answered.


Replace GUIDs? If Yes is chosen, when processing a project, GUIDs in the project are identified and replaced with new GUIDs.  This is very useful when copying an existing project to prevent the old and new projects from clashing when registered; it can also be used to modify an existing project that was copied manually (if the GUIDs were not updated).


Step 3


The third wizard step is used to review and process your selections.  After reviewing the changes that will be made, click Next to begin processing.  The wizard parses the project file to determine the files that comprise the project.  Only project files located in the project directory or one of its subdirectories are processed (project files in common include directories in a lower or parallel directory level will not be copied).  C++ include files that are not part of the project will not be copied (it is recommended that these files be added to the project first).  If the project is being renamed, each filename in the project that begins with the project filename root is renamed to match the new project name.  For instance, in a project MyApp.dsp being copied and renamed to NewApp, the project files MyApp.cpp and MyAppView.cpp would be copied as NewApp.cpp and NewAppView.cpp.


The project file and its constituent files are traversed, and if the project name is being changed, any instances of the old project name/filename root are replaced with the new project name (any binary files in the project are copied unchanged); any path/filename strings are updated as necessary; and all GUIDs are replaced with new ones (VC++ projects only).  If the project is being copied to a new location, the original files are not modified, and the new files are written to the destination path; if the project is not being copied, the existing project files are modified.


Step 4


After processing is complete, the last wizard step is displayed.  To open the new or updated project immediately, check the checkbox and click Finish.  The project will be opened in its associated application, where it can be built, modified, and debugged as needed.



The first time a new .dsp is opened, the Visual C++ IDE will create a .dsw for it and display a message about it finding an associated workspace file and opening it instead.
When a new Visual Studio .NET 2002 (or newer) project is opened, it will prompt to create a new .sln file for the project when first saving or building.