Forum

Hi,

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p> </o:p>

I just purchased the library for the first time and downloaded version 2.51. I used UI libraries from the different vendor before, but it did not support some features that you have. The problem is that when I launched the build Wizard none of the libraries built in VS2005. So, when wizard finished, I’ve launched the VS and found out that all original include and library directories for C++ projects have been removed from the registry and only directories for the Prof-UIS were added. Obviously, the built failed because C++ compiler was unable to find any standard header files and libs. Now I have to restore my VS2005 configuration manually. This would take sometime before I can try to compile the libraries again. Is this a known issue?

<o:p> </o:p>

Anyway, being a new user, I find this first experience with this software quite disappointing!

<o:p> </o:p>

Stan

<o:p> </o:p>

This issue is known. This is reproduced in the way when you run the Prof-UIS 2.50 Integration Wizard without running Visual Studio 2005 at least once before. We even discussed this issue with a specialist from the Visual Studio 2005 development team. In fact, Visual Studio 2005 does not get completely installed until you run it at least once. The include folders list of the Visual Studio 2005 is stored in the VCComponents.dat file that is typically located in the following folder:
C:\Documents and Settings\***WindowsUserName***\Local Settings\Application Data\Microsoft\VisualStudio\8.0\VCComponents.dat

The VCComponents.dat file is a UNICODE file which has the format of INI file. We can send you the initial version of this file.

We will fix this issue in the next major version.

While I’ve tried to unsuccessfully compile version 2.51, you’ve released 2.52. :) But I am afraid to install it now because I don’t want to restore my VS config again... Was this issue fixed in the new release?

2.51 and 2.52 are minor releases. They are distributed as ZIP files which should be extracted into the folder where the latest major release (2.50) are installed. You can also use the source code from minor releases on a clean machine. Each minor release does not bring any new bugs into the support tools of the last released major version. We would like to ask you to provide us with all the details of the building problems in conjunction with information about all the installed libraries/MS Platform SDKs on your machine. This will let us help you more efficiently and let you avoid the problems.