BUG: Profiler Extension Causes PWB to Think Build Info Changed

ID: Q73755

The information in this article applies to:

Microsoft Source Profiler for MS-DOS, versions 1.0, 1.2
Microsoft Source Profiler for OS/2, versions 1.0, 1.2

The information in this article is included in the documentation starting with Visual C++ 5.0. Look there for future revisions.

SYMPTOMS

When you attempt a build, Programmer's WorkBench may unexpectedly generate a message indicating that build options have changed if the Programmer's WorkBench extension supplied with the Microsoft Source Profiler version 1.0 or 1.2 is loaded into the Programmer's WorkBench version 1.0 or 2.0.

CAUSE

The problem occurs because the Profiler extension is rewriting parts of the .MAK file when the program list is loaded, even though it is not necessary. Because the makefile has been updated, Programmer's WorkBench determines that some build information has changed and so the error message is generated. The Profiler extension is not actually altering any of the build information, so responding No to the message box is safe (that is, you still get a completely up-to-date build).

STATUS

Microsoft has confirmed this to be a problem in the Source Profiler version 1.0. We are researching this problem and will post new information here as it becomes available.

MORE INFORMATION

This problem occurs after loading either the real-mode (PWBPROF.MXT) or protected-mode (PWBPROF.PXT) Profiler extension. If a program list is set and you select Build from the Make menu, Programmer's WorkBench generates the following message:

Build Information has changed

Do you want to rebuild everything?

If you select Yes, Programmer's WorkBench will rebuild the entire project, even though nothing has actually changed that you did not explicitly modify. Choosing No will rebuild only the modified components that you changed.

Additional query words: 1.00 1.20

Keywords : kberrmsg kb16bitonly TlsMisc
Version : :1.0,1.2
Platform : MS-DOS OS/2
Issue type :