No available visual studio 2005 solution

[olafvdspek]

No available visual studio 2005 solution

[GoogleCodeExporter]

Yes, this is by design.  We depend on VS2005 to read in the 2003 solution that 
we
provide, and automatically convert it.  We test with VS 8 to make sure that the
automatic conversion does the right thing, including the proper compiler flags 
etc.

Is there a problem with that scheme?  I'm declaring this bug will-not-fix, but 
if
there's a real advantage to having another sln, we can consider it.  I'm really
hoping there's not, though.

Original comment by [email protected] on 15 Nov 2007 at 1:35

• Changed state: WontFix

[GoogleCodeExporter]

I do not believe there is any problem with the scheme (in the usual sense of the
word).  VS2005 users will just have to be inconvenienced with performing the
conversion, which is not painful in this case.

If I encounter any advantages, I will look to bring them forward in the future.

Original comment by [email protected] on 15 Nov 2007 at 1:40