I normally kick off builds from within VisualBuild. Everything was fine until I decided to upgrade to Developer 7.03. Now the same line that worked crashes in Visual Build, yet it works if I type it directly in the DOS prompt. My Visual Build has not changed at all.
The error I get now when it gets to this line is:
Unknown exception.
File : C:\Program Files\InstallShield\Developer\System\ISCmdBld.exe
Version : 7.3.0.131
Exception : e06d7363
Address : 77e8f142
Access Type :
Access Address : 00000000
Registers : EAX=0012f704 CS=001b EIP=77e8f142 EFLGS=00000206
: EBX=0012f9d8 SS=0023 ESP=0012f6fc EBP=0012f754
: ECX=00000000 DS=0023 ESI=0012f794 FS=0038
: EDX=00c10228 ES=0023 EDI=0012f724 GS=0000
Stack Trace : 004074c3 0040477a 0040395d 004031ac
: 00401072 0040695a 00407ec8 77e97d08
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
I intially thought paths had changed, etc but as I said, if I execute it directly from the command line, it works. Any ideas?
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
ISCmdBld.exe 7.03 crashes from within Visual Build
Started by
Mireille
, May 15 2002 16:36
1 reply to this topic
Posted 15 May 2002 - 20:11
The problem was that the new IsCmdBld.exe (7.03) does not recognize UNC paths, although the help file says UNC paths are acceptable. A bug was introduced because it used to work in 7.02. When I was testing directly using the command line, I was typing a local path, thus it worked. I corrected the path in Visual Build and it worked also.
Bottom, you will not be able to build a project located on a different machine from the command line unless you have a mapped drive (I didn't test that though).
Bottom, you will not be able to build a project located on a different machine from the command line unless you have a mapped drive (I didn't test that though).