Will the output of the .sln be at different log levels so that errors can be distinguished from warn from chitchat, and will that output be streamed? Today when you run msdev against a solution you get a silence and then 'exec failed with error code 1', leaving you a large log file to search through to find out what borke.
>>> Yes. You'll be feeding the sln file to MSBuild, which in essence is going to spin off different tasks for each project in the solution file. All the eventing goes through the standard MSBuild eventing mechanism which can be captured by any registered loggers. Our events in short are: * Error * Warning * Message (priority high, medium or low) * Status * CustomEvent (priority high, medium or low) Ok. See the comments on http://ant.apache.org/manual-1.6beta/OptionalTasks/ildasm.html to get a hint of the problem >>> I have forwarded this to the right folks. I will let you know when I hear back from them. Thank you for passing the feedback along finall, for vbc, why use a different separator for referenced libraries than csc? He have excessive hoop jumping there and need to add some more to get things fully working. >>> I don't get this. Vbc.exe /reference: System.dll, System.Data.dll Csc.exe /reference: System.dll, System.Windows.Forms.dll How are these different? They both use comma's as their separators and they both use the same switch to reference other assemblies. Thanks for the feedback! Alex Kipman ([EMAIL PROTECTED]) Program Manager MSBuild Team -- This posting is provided "AS IS" with no warranties, and confers no rights. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
