Forum

Hello,

On a new WinXP SP2 EN system, I installed VS2005 Pro. WITHOUT LAUNCHING IT for the 1st time(I really regret that), I installed Prof-uis 2.50. When it came to the compile and integrate the dlls. "An unhandled win32 exception occurred in devenv.exe[1728]".

It seems to me, at the first launching of VS, it scans and set the environment paths(include/lib/bin etc). With Prof-uis doing its virgin launch, Prof-uis interrupts VC’s normal procedure and replaced the standard paths with the prof-uis path instead of appending (option->projects->vc++ dir). I found this tragedy when I found that VC could not compile the Wizard-generated projects. A completely uninstallingg VS and reinstalling it doesn’t help, Then I manaully add the standard include and lib path. it then can compile a few Wizard-generated projects, or even profuilib. However, when I try to compile profuidll, "An unhandled win32 exception occurred in devenv.exe[1728]" returns.

Can you please tell me how to solve the problem? Or can you please publish the DEFAULT includes/lib paths of vc++, so that I can manually fill them. Thank you .

Sorry come back bugging again. However I just found something might help you to make you product better.



I did reinstall VS 2005 several times, I tried both pro and team suite on the same computer, harvesting the same problem. then I gave up.



What dirves me to continue this thread is that, I have a chance to test the library on another computer with another copy of VS 2005 pro(different license). And I met the same problem. So my previous analysis could have been wrong.



I am sure you have no problem and have tested your code on a few platforms before releasing. But I suspect the problem lies in the multilanguage resource file(or MS’s rc compiler) that you may not have tested.



The computers I have tried are all WinXP En SP2, but in order to support Chinese Characters display, I made some changes to "Regional and language options": languages tab -> installed files for Eastern Asian Languages; Advanced tab ->select "Chinese(PRC)" for non-Unicode programs.



I doubt this is the cause because such a setting afftects me while compiling BOOST library, VS complains illegal characters found in files, some source code has being messed up by the current encoding page.



What differs in you code is, VS crashes on cleaning the project. Another supporting reason is I used to translate the .rc fiel for you(and got rewarded with a license, thanks). I notified you that I could not compile the project with the translation on MY computer.



I don’t know much how the RC file and RC compiler supports multi languages. So I cannot submit more analysis. Hope it helps to find the bug.



This is a excellent piece of library, I regret I cannot use it with a license :-(

This crashing behavior cannot be assumed to be a Prof-UIS bug because you can compile it when switching the locale to English. Of course, the compiled resources should be the same not depending on the current Windows locale. We understood the inconvenience you have. But it should not be extremely difficult to compile the needed Prof-UIS configurations under English locale and then use them under Chinese.

Yes, I did restored the folders. Then I can go through successfully with all other projects except Profuisdll_800.sln, which crashes the ide.
So I think that the folder issue is not the cause of the crash, and am inclined to find the cause in the project settings of Profuisdll_800.sln. Then when I deleted the profuisdll.rc from the project. The solution compiled successfully and generated a .dll file without crashing the ide.

My questions are 1)how come the solution compiles without the RC file, 2)how come having THAT .rc file crashes the ide on even a trial to clean the solution.

Thanks.

We have never encountered any crash of Visual Studio 2005 due to loading some resource file, nor we received such information from our users before. But, you may have noticed that Prof-UIS resources are large enough and contain resources for 28 languages. May be this is the source of the crash. In any case, it seems you could save your time if you do not attempt to find what’s wrong with Visual Studio 2005 because although it was released, lots of bugs were reported after release candidate 2. It should be easier to reinstall it.

As said before, this problem only happens to Profuis_800.sln.

Today, I opened Profuis_800.sln directly and delete profuis.rc from the solution. Then It compiles through without a crash and produced a dll file!!!

I just cannot understand it.

Can you please explain it please?

Did you restore the include folders of Visual Studio 2005 as we advised you?

We consulted with a guy from the Visual Studio 2005 development team. He advised us to get the default settings file from other location and put it into the location where Visual Studio 2005 will initialize it during the first start. We are strongly staying at the point that it is the bug in the Visual Studio 2005 design, not in Prof-UIS Integration Wizard. Nevertheless it is not difficult to initialized the Visual Studio 2005 settings in our Integration Wizard, we think we should not do the job which must be done by Visual Studio 2005 installation process. Besides, what should we do with the next releases of Visual Studio?

Hi,

Thanks for your fast and detailed reply. I downloaded your file and replaced mine. Then I launched the integration wizard. Oh, the Visual Studio Just-in-time debugger popped up again with "An unhandled win32 exception occurred in devenv.exe[1728]".

Then I reboot the computer and open Profuis_800.sln directly, compiled each project one by one, profuislib.vcproj was compiled successfully. other projects were compiled sucessfully but no linked with missing files. When it came to Profuisdll.vcproj, oops, the Visual Studio Just-in-time debugger popped up again with "An unhandled win32 exception occurred in devenv.exe[1728]". here below is found in the output window before the crash:
"------ Rebuild All started: Project: profuisdll, Configuration: ANSI Debug RDE Win32 ------
Deleting intermediate and output files for project ’profuisdll’, configuration ’ANSI Debug RDE|Win32’’

Do you have a clue about this? it seems the problem only happens to this project. Thank you!

I find a way to restore the default settings(tools->import and export settings), however the error still exists, only for profdll; whenever I try to compile this project, devenv.exe crashes.

We cannot say that that it’s a bug of the Prof-UIS Integration Wizard. It simply creates automation objects of Visual Studio and invokes its methods for loading and building projects. Visual Studio 8.0 stores the paths in the VCComponents.dat file located in this following folder:
C:\Documents and Settings\USER NAME\Local Settings\Application Data\Microsoft\VisualStudio\8.0\VCComponents.dat

with USER NAME being your Windows XP username. The VCComponents.dat file is an INI file in the UNICODE format (you can download it from here).
We guess that Visual Studio may create this file during its first startup but, if it is not the case, then it’s a bug of Visual Studio and not a bug in our wizard. If you put it correctly in the valid location, then you will save some time for retyping all the path variables.

Here is the list of default paths defined by default in Visual Studio and stored in the VCComponents.dat file:

Executable files:

$(VCInstallDir)bin
$(VCInstallDir)PlatformSDK\bin
$(VCInstallDir)PlatformSDK\common\bin
$(VSInstallDir)Common7\Tools\bin\prerelease
$(VSInstallDir)Common7\Tools\bin
$(VSInstallDir)Common7\tools
$(VSInstallDir)Common7\ide
$(ProgramFiles)\HTML Help Workshop
$(FrameworkSDKDir)bin
$(FrameworkDir)$(FrameworkVersion)
$(PATH)

Include files:

$(VCInstallDir)include
$(VCInstallDir)atlmfc\include
$(VCInstallDir)PlatformSDK\include\prerelease
$(VCInstallDir)PlatformSDK\common\include\prerelease
$(VCInstallDir)PlatformSDK\include
$(VCInstallDir)PlatformSDK\common\include
$(FrameworkSDKDir)include

Reference files:

$(FrameWorkDir)$(FrameWorkVersion)

Library files:

$(VCInstallDir)lib
$(VCInstallDir)atlmfc\lib
$(VCInstallDir)atlmfc\lib\i386
$(VCInstallDir)PlatformSDK\lib\prerelease
$(VCInstallDir)PlatformSDK\common\lib\prerelease
$(VCInstallDir)PlatformSDK\lib
$(VCInstallDir)PlatformSDK\common\lib
$(FrameworkSDKDir)lib
$(VSInstallDir)
$(VSInstallDir)lib

Source files:

$(VCInstallDir)atlmfc\src\mfc
$(VCInstallDir)atlmfc\src\atl
$(VCInstallDir)crt\src

Exclude directories:

$(VCInstallDir)include
$(VCInstallDir)atlmfc\include
$(VCInstallDir)PlatformSDK\include\prerelease
$(VCInstallDir)PlatformSDK\common\include\prerelease
$(VCInstallDir)PlatformSDK\include
$(VCInstallDir)PlatformSDK\common\include
$(FrameworkSDKDir)include
$(FrameWorkDir)$(FrameWorkVersion)