Fallen at first hurdle using C# Example in OCC6.2

Hello Ernest,
I dont know much about the C# example of OpenCascade, but there is a .NET warpper for many OpenCascade classes:

http://www.opencascade.org/org/community/projects/?project_id=218

best regards
Gerhard

Hi Ernest,

- is shell.dll in the EXE-directory of the application? If not just copy the output files of all projects into one directory.
- as far as I know in VS Express you cannot mix different languages in one solution (it was so before but might have changed). In that case you would have to compile the projects separately and copy corresponding files into the same directory.

I use VS professional. I guess, I used the provided sample from OCC5.2 and it worked fine. OK there are some bugs but at least I was able to start the application.

Pawel

Hi Ernest,

I’ve updated the MakeBottle sample and you can download it from:- (watch out for the case sensitive path)

http://www.myxyz.co.uk/Downloads/Development/

Let me know if it works for you.

Jonathan

I've had a very similar problem. I get the FileLoadException for shell. The odd thing is that with a try catch around the load, somehow the shell does manage to load the second time. However, there is another problem that on some machines that I have installed the release of the application it will crash again. One factor seems to be that I have tried it on a machine that did not have Visual Studio and it did not work, but then when I install Visual Studio the application will work. I was thinking that this might be just that the Visual C++ Runtime library needs to be installed, but haven't had much luck fixing it. I added the Visual C++ Runtime as a prerequisite to the project and tried installing the redistributable C++ runtime library, but still no luck.

I tried doing dependency walker on the application and shell, but it did not find anything that was not being referenced.

I also tried using the Modules feature in Visual Studio to see which dlls are actually used when the shell is loaded and I added these dlls to the application install directory, but this did not help either. I wasn't sure whether I needed to set the dlls to register and/or set them as system (msvcp80.dll, etc.), but I tried some of these things and was not able to fix the problem.

Any ideas of anything to try? It seems like the underlying issue is that the "Form2 newForm = new Form2();" line does not work, but I guess that something installed with visual studio has some sort of debugging feature that catches it and fixes the reference somehow??? I'm not very comfortable with DLLs, so there may be something trivial that I am not doing that could solve the problem. Thanks for any advice.