This project has moved and is read-only. For the latest updates, please go here.


VersionFileDialog fails in x64


Problem contain attempting to use CCNetConfig on Win64.
THe latest build will run, and allow you to select a config file & version, but crashes immediately after that.
System.ArgumentException: The path is not of a legal form.
at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
at System.IO.FileInfo..ctor(String fileName)
at CCNetConfig.UI.MainForm.OpenConfigurationFile()
at CCNetConfig.UI.MainForm.openConfigurationToolButton
THe crash happens in OpenConfigurationFile, by the lines
      CreateConfigurationNode ( vfd.SelectedVersion );
      this.addProjectToolButton.Enabled = true;
      FileInfo file = new FileInfo ( vfd.FileName );
      if ( file.Exists ) {
vfd.FileName is null. As far as I can deduce, the HandleNotifyMessage of VersionFileDialog just doesn't work in x64 (so _fileNames is never filled, so FileName is always null).


camalot wrote Jun 7, 2007 at 6:16 PM

ok, I will see if i can address this issue ASAP

JamesCurran wrote Jun 7, 2007 at 8:04 PM

Note, the first two words of the original description should be "Problems continue" (ok, so I can't type...)

And I guess you can see now what motivated my other issue: Fixing VersionFileDialog would probably be just as big a task as removing it.

And x64 support is important. CCnet is intended to be run a remote/rack-mounted/back-office server and those machines will be increasingly 64-bits in the coming years.

the_skipster wrote Oct 24, 2007 at 5:35 AM

Might be able to find some insight here:

wrote Nov 27, 2007 at 3:32 PM

wrote Nov 28, 2007 at 6:14 PM

wrote Feb 12, 2008 at 7:44 PM

wrote Apr 18, 2008 at 5:23 PM

wrote Jun 9, 2008 at 10:33 AM

wrote Nov 14, 2008 at 4:18 AM

allender wrote Nov 14, 2008 at 4:20 AM

any update on the x64 issue? It's been over a year :-( The same problem still exists in the VersionFileDialog

camalot wrote Nov 21, 2008 at 4:01 AM

As I do not have an x64 processor, and no one with one offered up any support, I am sorry to say that this has been sitting here. I know the issue is still present and I should have an x64 by the end of the month that should allow me to start to try and tackle this one.

wrote Dec 1, 2008 at 9:54 AM

wrote Dec 7, 2008 at 9:11 PM

wrote Dec 7, 2008 at 9:13 PM

Associated with changeset 44644.

dodgyrabbit wrote Jun 25, 2009 at 2:56 AM

Seems like this is still an issue when running it on a 64 bit machine... but you can work around it.
Force the program to run in 32 bit mode on a 64 bit machine. Simply execute this from the command line:
corflags CCNetConfig.exe /32bit+

Alternatively, compile from source and set the target as x86.

You can find corflags.exe under C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin or something similar.

wrote Feb 14, 2013 at 7:05 PM

wrote May 16, 2013 at 9:01 AM

wrote May 16, 2013 at 9:01 AM

wrote Jun 14, 2013 at 7:50 AM