> solution/project files first have to be converted. And converting from the
> command line is not possible (believe me: I searched all docs, googled for
> two days).
There is this batch file supplied in the Visual Studio help and on the MS
website...
// when running this at the command line,
// call it with CScript so you don't get UI.
// example: CScript convert.js e:\yourprojects\old.dsp
e:\yourprojects\new.vcproj
// NOTE: full path required to both input and output files
// or set default script engine to the command line doing this first
// example: CScript //H:CScript
// Once you set the environment, run the .js file like a .bat file
// To have a batch file loop through all the .dsp files
// in a directory, write a batch file that looked like this
// (Windows NT 4 or Windows 2000 only)
// CScript //H:CScript //Nologo
// for /R %%i in (*.dsp) do convert.js %%i >> .\Convert.log
var vcProj = new ActiveXObject("VisualStudio.VCProjectEngine.7.1");
var objFile = new ActiveXObject("Scripting.FileSystemObject");
var objArgs = WScript.Arguments;
// check the arguments to be sure it's right
if (objArgs.Count() < 2)
{
WScript.Echo("VC6 or 5 DSP Project File Conversion");
WScript.Echo("Opens specified .dsp and converts to VC7.1 Format.");
WScript.Echo("Will create project file with .vcproj extension");
WScript.Echo("\n\tusage: <full path\project.dsp> <full
path\project.vcproj>");
WScript.Quit(1);
}
WScript.Echo("\nConverting: "+ objArgs.Item(0));
// If there is a file name of the .vcproj extension, do not convert
var vcProject = vcProj.LoadProject(objArgs.Item(0));
if (!objFile.FileExists(vcProject.ProjectFile))
{
// specify name and location of new project file
vcProject.ProjectFile = objArgs.Item(1);
// call the project engine to save this off.
// when no name is shown, it will create one with the .vcproj name
vcProject.Save();
WScript.Echo("New Project Name: "+vcProject.ProjectFile+"\n");
}
else
{
WScript.Echo("ERROR!: "+vcProject.ProjectFile+" already exists!\n");
}
...but that's overkill for a problem that should be fixed in the first
place.
> > I think we may be better off redoing how our version resource
> > definitions are handled so that we can ditch the vcproj support entirely
> > and just let VS convert dsp's (even Whidbey converts dsps) -- the
> > resource definitions are the only reason VSNet screws up when it
> > converts Subversion dsp files.
>
> Oh no! Please don't. If you do that, then I can forget having a build
script
> for TSVN because I then _must_ build Subversion "manually" first, i.e. not
> from the command line.
Agreed. It should build a valid vcproj file.
Sly
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 22 11:45:33 2004