tshad said:
If that works that's great. My concern is different references in the
project pointing at files that won't be there if you rename them. This used
to be a problem with VS and don't know if that is still the case.
I just tried to move the Project folder and rename the files and found
certain values in various folders that still point at the old file name.
For example:
The .vbproj has the following (CreateSVC is the old name and SearchAgents is
the new name):
ApplicationIcon = ""
AssemblyKeyContainerName = ""
AssemblyName = "CreateCSV"
AssemblyOriginatorKeyFile = ""
AssemblyOriginatorKeyMode = "None"
DefaultClientScript = "JScript"
DefaultHTMLPageLayout = "Grid"
DefaultTargetSchema = "IE50"
DelaySign = "false"
OutputType = "WinExe"
OptionCompare = "Binary"
OptionExplicit = "On"
OptionStrict = "Off"
RootNamespace = "CreateCSV"
StartupObject = "CreateCSV.Form1"
The .sln file has the old names and various GUIDs. I assume there would be
a problem if both projects use the same GUIDS:
Microsoft Visual Studio Solution File, Format Version 7.00
Project("{F184B08F-C81C-45F6-A57F-5ABD9991F28F}") = "CreateCSV",
"CreateCSV.vbproj", "{619A19B0-B845-459B-B93C-A91DD21F93BF}"
EndProject
Global
GlobalSection(SolutionConfiguration) = preSolution
ConfigName.0 = Debug
ConfigName.1 = Release
EndGlobalSection
GlobalSection(ProjectDependencies) = postSolution
EndGlobalSection
GlobalSection(ProjectConfiguration) = postSolution
{619A19B0-B845-459B-B93C-A91DD21F93BF}.Debug.ActiveCfg = Debug|.NET
{619A19B0-B845-459B-B93C-A91DD21F93BF}.Debug.Build.0 = Debug|.NET
{619A19B0-B845-459B-B93C-A91DD21F93BF}.Release.ActiveCfg = Release|.NET
{619A19B0-B845-459B-B93C-A91DD21F93BF}.Release.Build.0 = Release|.NET
EndGlobalSection
GlobalSection(ExtensibilityGlobals) = postSolution
EndGlobalSection
GlobalSection(ExtensibilityAddIns) = postSolution
EndGlobalSection
EndGlobal
The .suo file also has the old name in it.
Tom