SilverScreen Solid Modeler

SilverScreen Naming Convention

SilverScreen Naming Convention

 Previous topic Next topic  

SilverScreen Naming Convention

 Previous topic Next topic JavaScript is required for the print function  

SilverPlusEllipse

 

SilverScreen Naming Convention

 

SilverScreen is named in such a way as to make the MFC platform it uses evident to developers. This is an extremely important consideration and helps to mitigate the problem known as "DLL Hell" among Windows developers.

 

In a nutshell, DLL Hell is the problem that arises when an add-on and an application share a copy of MFC. In order for a shared MFC class to have the same meaning to both, then both must have been linked to the same version of MFC.

 

For more information on DLL Hell, click the preceeding link or seach the web for the term "DLL Hell".

 

 

The following table shows which version of Visual C++ (and by association which version of MFC) was used to build SilverScreen:

 

Program name

Visual C

silver6.exe

Visual C 6 (no longer supported)

silver6D.exe

Debug compilation with Visual C 6 (no longer supported)

silver8.exe

Visual C 8

silver8D.exe

Debug compilation with Visual 8

silver9.exe

Visual C 9

silver9D.exe

Debug compilation with Visual C 9

silver10.exe

Visual C 10

silver10D.exe

Debug compilation with Visual C 10

 

 

The best way to avoid DLL Hell is to use a dependency walker to examine the edition of MFC being used by the SilverScreen with which you are working, and to then ensure that you are linking to the same edition of MFC while building your application. Finally, this common version of MFC must be installed on the client machine.