| |
|
|
|
|
|
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.
|
Subject |
Author |
Date |
|
|
Logan Mueller
|
Oct 16, 2003 - 7:03 PM
|
We have downloaded the Prof-UIS trial copy, and would really like to look at ProfStudio demo. Unfortunately, after compiling and running we get an assertion error in olelink.cpp. (Line 82, m_dwRegister is not zero and lpszPathName does not look valid)
Zooming out of the stack, this is caused in CMainFrame::OnCreate() when CExtControlBar::FrameInjectAutoHideAreas() is called.
Is there something I’m doing wrong? I’ve made no changes to the product. I’ve only downloaded it, compiled, and attempted to run. Can someone explain what I should do.
We have here a WindowsXP environment with VC 6.0 SP5.
|
|
|
Sergiy Lavrynenko
|
Oct 17, 2003 - 2:15 AM
|
Dear Logan,
I cannot confirm the bug you are talking about. Nevertheless, your information is very interesting because nobody told me about something similar to that before and I’d like to sort it out. Line 82 in olelink.cpp is in the COleLinkingDoc::Register() method. The COleLinkingDoc class is a CDocument-derived class. But Prof-Studio is not based on the document-view architecture. Since it does not initialize document templates (CDocTemplate-derived class instances), then the application cannot contain any CDocument-derived objects during runtime at all. If I setup a break-point at olelink.cpp line 82, it will never be reached. Please make a screen shot of the Visual Studio 6.0 Call Stack window and send it to me. This may clarify the problem.
Best regards, Sergiy.
|
|
|
Logan Mueller
|
Oct 17, 2003 - 5:20 PM
|
Just a note: on each of the computers I had problems running after compiling with VC6.0, I was able to run ProfStudio without the problem after compiling with VS .NET 2003.
|
|
|
Logan Mueller
|
Oct 17, 2003 - 1:42 PM
|
Hello Sergiy,
I’ve tried it on two other machines. (Running Windows2000 instead of XP) They both have the same problem.
The ASSERT fails after "configuring bars" message comes up on the splash screen. I have the trial version, so I can’t see the full stack since there’s no symbols. But once again, it is being caused either by CExtControlBar::FrameInjectAutoHideAreas or maybe CExtControlBar::FrameEnableDocking.
Maybe there is some ActiveX or OLE object your demo is expecting to be registered on my machine?
I bet most people who download your trial might give up on compiling ProfStudio. Because it isn’t clear at first that you can only use the "MCBS Debug" build. But when you first open the project it detaults to another build type which can’t be linked. You might want to consider saving all of your trial projects with the default build set to "MCBS Debug" instead since that’s the only one you can link. But then, any experienced developer should figure it out.
I will send a screenshot. Thank you for your help.
Kind regards,
Logan
|
|