Not sure why it works that way in VS 2003, but the behavior you are seeing is by design. The build waits for the executable to complete before continuing. This is so that any output that the executable will generate is available for the next step, even through it is post-build.
You could very easily write an executable that would run another executable as a background process and then exit. This would allow you to continue the build in those cases where you don't need to worry about waiting. ...Glenn On Wed, Sep 17, 2008 at 5:17 AM, July <[EMAIL PROTECTED]> wrote: > > Hi all, > > this is my first post, so please be patient with me. > > I would like to run a .exe in a post-build event with Visual Studio > 2008, for example notepad.exe. > Visual Studio starts the application, the notepad window pops up and > that's it. The build waits until I close notepad. The VS GUI is all > grey and debugging is not possible until notepad is closed again. > > This might be great for unit testing and such, but I don't want VS to > wait until my external application has terminated. > > It works fine in VS 2003. I searched the web thoroughly, but didn't > find a hint anywhere. > > July > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://cm.megasolutions.net/forums/default.aspx -~----------~----~----~----~------~----~------~--~---
