Forum
Please
Log In
to post a new message or reply to an existing one. If you are not registered, please
register.
NOTE: Some forums may be read-only if you are not currently subscribed to
our technical support services.
|
Subject |
Author |
Date |
|
|
Timothy Anderson
|
Nov 8, 2005 - 4:17 PM
|
I installed, ran the integration wizard and it complained about an NCB file being read only and then just sat there for some time. I uninstalled, deleted everything, re-installed then removed "read only" on the profuis tree and re-ran the integration wizard. It seems to be much happier now. So there appears to be some weirdness with the read only bit when running a clean install on 2.50 build for 2003 .net VC 7.1
|
|
|
Timothy Anderson
|
Nov 8, 2005 - 4:29 PM
|
Still complains about read only .ncb file weirdness, but the build goes up to the first of the "RDE" builds and then just sits there. Whatever the "RDE" builds are. It can’t possibly get more straight forward than my setup. Install. Run integration wizard. Complains. Gets stuck forever in some mystery state. I have both VS98 and VS2K3 installed on this box if that makes any difference.
|
|
|
Technical Support
|
Nov 9, 2005 - 12:23 PM
|
The problem with the read only ncb files is known to us. It occurs occasionally and only if the Visual Studio is invoked via its automation objects. We made lots of tests with Visual Basic 6.0. When receiving the end-of-build notification, we close Visual Studio and release the COM pointers. In this case the instance of Visual Studio persists up to one minute and still keeps "closed" project in "open" state. At the same time, we open the project for building the next configuration. It seems we should think about switching to NMAKE utility and MAK files instead of running Visual Studio via automation. Of course, as a workaround, you can build all the configurations with the Batch Build dialog in VS.
|
|