Gert Driesen wrote:
Can't we do a quick parse of the resx sources to see if they require those references ? A large number of cases do not require any references at all.
Yeah we probably could ... Just didn't/don't have time for that, and didn't see much need for it at that point ...
I had to comment it out here because it was taking up to ten seconds to compile each .resx file in the solution.
BTW- could we just skip copying resources and compile the .resx files after we copy references? I'm assuming that VS.NET would be compiling the .resx file using only the "Copy Local" references anyways, so we wouldn't be doing anything differently.
I'm working on cutting down the time for a <solution> build in our shop again (via profiling)- this is one of the biggest culprits right now. :)
I understand, but we can't sacrifice features for performance.
But on the other hand we shouldn't slow down *every* solution based build in order to satisfy some corner cases if we can avoid doing so.
No ofcourse not, if we can combine performance and features, I'm all for it ;-)
This is a really big performance drain for any build that uses references extensively. I'd say it's a good candidate for performance tuning. :)
Matt.
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
