Site Map / Register

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.

Forums » Prof-UIS General Discussion » Integrate with .NET 2003 v7.1

Subject	Author	Date
Integrate with .NET 2003 v7.1	Ben Huang	Dec 28, 2005 - 2:40 AM
Right now I am facing a new problem. I am using ProfUIS v2.50 (which is more stable), and I have integrated with VC6++. There is no problem. Everything works fine. Now, I try to integrate with .NET 2003 v7.1. The following message pop-up: "class view information will not be available for vc projects because the solution NCB file C:\Program Files\FOSS Software Inc\Prof-UIS\ProfUISDLL\profuisdll_710.ncb is read-only. if your solution directory is read only or the solution path contains unicode characters, other feature will also be affected." I check the file, profuisdll_710.ncb. I am pretty sure that It is not a read-only file. Then the Integration Wizard keeps executing the next stage for a really long time (more than 40mins). The only choice that I have is to terminate the Wizard.
Re:Integrate with .NET 2003 v7.1	Technical Support	Dec 30, 2005 - 7:41 AM
Yes, we were reported about this problem. It occurs more often on slow computers and rarely on fast ones. The Integration Wizard creates an instance of Visual Studio .NET 2003 via its automation objects. Our wizard invokes methods of Visual Studio’s COM object to open solution files and build required project configurations. The problem is when the wizard receives the event when the build is finished (the event comes from Visual Studio), the wizard requests Visual Studio to close the solution file. The Visual Studio’ COM object returns execution control immediately in this case. In fact, the Visual Studio continues closing the solution in parallel mode. It is not possible to catch the end of close event because there is no such event provided by Visual Studio interfaces. We simply do 15 second wait in this case and that is enough for most of computers. But sometimes, when our wizard opens a solution to built its projects, the previously open solution is kept open by other Visual Studio instance. That is why the .NCB file becomes read-only. If this error occurs very often on your computer, please compile desired configurations of profuisdll and/or profuislib projects with Visual Studio manually (instead of using the Integration Wizard): Just open the Batch Build dialog and select the configurations you need for the profuisdll project. We plan to fix the problem described above by switching to compiling the projects with the NMAKE utility.