In my setup program, I was calling vsdbcmd.exe, a very wonderful database tool from Microsoft, to deploy my dbschema file in C#. I used a System.Diagnostics.Process object to invoke the tool, as I’ve always done with calling command-line utilities. And as always, I redirected the process’s output and error so I could display them in my setup log file. Unexpectedly this did not work. My program was hanging, still alive, but hanging. The database was created half way, and vsdbcmd.exe was still live in task manager. However there was no CPU activities from vsdbcmd.exe. After a bunch of experiments, I found out that redirecting the process’ output was the cause of the blockage. Redirecting error was okay. Gah why can’t vsdbcmd.exe work like all the other programs?
-
Recent entries
- cshtml files getting 404 error after posted to IIS 7
- How to change authentication in IIS using C#
- iOS5 whitelist URL unauthorized using PhoneGap
- vsdbcmd.exe fails with error 0x8007000B
- vsdbcmd.exe gets blocked by its calling process
- Project not selected to build for this solution configuration
- A potentially dangerous Request.Form value was detected from the client
- SQLCMD Mode
- TFS Error MSB4062
- The working folder [source path] is already in use by the workspace [workspace name];[owner] on computer [tfs server].
-
Browse popular tags
.net framework 4.0 artificial intelligence asp.net authentication c# f# IIS ios 5 msbuild mvc phonegap sql server 2008 tfs visual studio 2010 vsdbcmd webmatrix windows forms -
Meta