I would caution everyone to not forget the whole purpose of using Visual Studio is to make development by Visual Studio users easier, not harder. Generating .sln files that can be loaded in this way, even if the generation operation takes less than 1 second, would still result in 800 .sln files. This would be somewhat bizzare, since Visual Studio can have only one .sln file open at once. There are inter-project dependencies that would be lost, to name one of numerous problems that would arise.
Our effort should focus on getting the integration done the way it should be. Doing that might make the performance problems moot. If it turns out that the problems still exists, it will be easy to scale back. Right now, as it stands, the cake is not yet fully baked. -John From: ros-dev-boun...@reactos.org [mailto:ros-dev-boun...@reactos.org] On Behalf Of Timo Kreuzer Sent: Friday, January 11, 2013 3:17 PM To: ReactOS Development List Subject: Re: [ros-dev] Notice Of Intent - Visual Studio Build of ReactOS Am 11.01.2013 06:48, schrieb BinSys: I suggest a sln file in each directory. Only a sln file is too big, very slow to load. I agree, but before changing this, we should measure a possible performance impact on the configure operation. (We are talking about generating a few hundred solution files) I don't know if it has any impact at all (especially for non-VS build), but you never know... _____ No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.2890 / Virus Database: 2637/6025 - Release Date: 01/11/13
_______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
