Forum

Hi,

After having installed the package, I’ve built libraries I was interested in through the Integration Wizard. I’ve built ProfUIS, ProfSkin, and ProfAuto both in MBCS Debug and Release mode, as Zlib and LibPNG respectively in Debug and Release DLL mode (always Win32 platform). Every configuration has been built correctly, apart from ProfUIS in MBCS Debug (ProfUISDLL - Win32 MBCS Debug): there was no ProfUIS290md.dll, nor ProfUIS290md.exp or ProfUIS290md.lib (notice that no errors have been highlighted and the whole operation has been closed as succesful).

So, I checked projects configurations (Workspace -> ProfUIS_800.sln) and I discovered that the solution MBCS Debug configuration is the same as the Release one: every project configuration is set to MBCS Release, apart from ANSI ones (that are ANSI DEBUG).

I think there’s a problem (I’ve never encountered this problem with the previous versions nor with the 2.90 freeware one). What should I do to achieve the MBCS Debug version of ProfUIS library?

Other info:
OS: XP SP3
DevEnv: Microsoft Visual Studio 2005 (I’ve built libraries for this environment)

Thank you in advance,

Tom

I solved the problem about the error message I got at runtime beginning (I wrongly wrote "beginning of building operation": I was meaning runtime).

I thought the problem was related to ProfUISDLL MBCS Debug building due to the singularity of the situation: as I said in my last post, the error occurred just with the MBCS Debug version of 2.90 full library, not with the freeware one, nor with the MBCS Release version of both 2.90 freeware and full library, and I had had problems to build exactly in that configuration, as I wrote before. I’ve discovered, instead, that the error depended on a limit in the assembly loader (actually comprehensible for MBCS Debug building of the full library).
I solved using /GF parameter (enable string pooling) while compiling and building.

Thank you,

Tom

This is something new and very interesting. We added the /Zm512 compiler option to the Prof-UIS, additional libraries, all the sample projects and Prof-UIS Application Wizard generated projects. We added this compiler option more than year ago. Prof-UIS library simply exceeded the default memory limit using by all the Microsoft’s C/C++ compilers. But we never received reports about string pool related issues. Could you please try to remove the /GF parameter and replace /Zm512 with /Zm1024 or, even with /Zm2048.

I’ve seen that you use the /Zm512 parameter in your projects, but in last two posts I’m talking about building my application, not ProfUIS. I’m afraid I did not express myself not very clearly. I try to make a sum up:

1. I had problems building ProfUISDLL in MBCS Debug mode through Integration Wizard. The problem existed also building manually through the MBCS Debug configuration for the whole solution. This problem is still unsolved.

2. I manually built ProfUISDLL in MBCS Debug mode changing only its configuration (so just the project one, not the solution one) and building only that project. In this way I achieved correctly the library in MBCS Debug mode.

3. Then I built and tried to execute my application (that uses ProfUIS) in Debug mode, but I got the error message of two posts before (Exception from HRESULT: 0x80131522). I consequently thought that was possibly due to a kind of error during MBCS Debug ProfUISDLL building in consideration of: a) the problems encountered before trying to build it, and b) that fact that my application runs correctly with MBCS Debug ProfUISDLL 2.90 Freeware and both MBCS Release ProfUISDLL 2.90 Freeware and Full.

4. I’ve discovered that the error message of (3) is about an overcame limit in the assembly loader (I suppose due to the fact ProfUISDLL 2.90 Full in Debug mode is huge to load, and my application uses several other libraries too). I solved this building my application with the /GF compiler option (I’m already using the /Zm140 too, but in this case the error wasn’t related to the compiler memory need).

I hope this may help you.

Tom

As I wrote, I’ve tried to set the solution configuration to MBSC Debug, achieving only a MBCS Release general setting (so, to say, the overall configuration is called MBCS Debug, but all the projects configurations are set to MBCS Release, apart from the ANSI ones, as I wrote yesterday).

I’ve also tried setting the ProfUISDLL project (only it) to MBCS DEBUG configuration manually. After I built it, I’ve obtained the related .dll, .exp, and .lib files. However, when I tried to build my application project in Debug mode, at the very beginning of building operation, I got an error message (never encountered before):

"Eccezione non gestita di tipo ’System.IO.FileLoadException’ in Modulo sconosciuto.

Informazioni aggiuntive: Impossibile caricare il file o l’assembly ’DentalVox, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null’ o una delle relative dipendenze. Impossibile trovare o caricare un tipo. (Eccezione da HRESULT: 0x80131522)"

That in english should be something like:

"Unhandled exception of ’System.IO.FileLoadException’ type in unknown Module.

Additional information: Impossible to load the file or the assembly ’DentalVox, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null’ or one of the related dependancies. Impossible to find or load a type. (Exception from HRESULT: 0x80131522)"

Notice that this problem does not happen with the MBCS Debug version of 2.90 freeware library, nor with the MBCS Release version of the 2.90 freeware and full libraries (but I have to admit I’ve not encountered problems building them, if there’s any relationship between the problems).

Thank you,

Tom

PS: I’ve sent the Integration Wizard report file in the Support sub folder.

We just re-checked the Integration Wizard using WinXP SP3 and VS2005. It works. Please pack the log files from the .../Prof-UIS/Support/ sub folder and send them to the support mail box at this web site.
You can build any libraries manually. You can open .../Prof-UIS/Workspace/ProfUIS_800.sln solution file in VS 2005 and build the MBCS Debug configurations of the ProfUISDLL projects.