The preferable way to develop EPLAN API applications is to reference the API assemblies directly in a .NET project using CLI programming languages like C# (C Sharp), Visual Basic.Net, C++/CLI. You could do this by just using a text editor and calling the compiler from a DOS box -- like described in the topics "Creating add-ins in CSharp" or "Creating add-ins in Visual Basic.Net".
The much more convenient way of developing involves the use of an Integrated Development Environment (IDE). We recommend the use of Microsoft Visual Studio, but there are also free development environments like SharpDevelop. How you would start an API project in the Visual Studio is described in the topic "EPLAN .Net API".
The EPLAN API has explicitly been tested and released for Microsoft Windows 7, 8 and 10.
It is not recommended to use EPLAN API in separate, children threads. It could lead to problems because such configuration wasn't tested nor predicted by API designers.
Currently when debugging applications, w3u.exe process is detached at the beginning of debug. This happens because w3u.exe from Electric P8 folder calls eplan.exe from 'Platform' folder. In order to continue debugging, please attach to process eplan from 'Platform' folder. Another solution is to start debugging eplan.exe in the 'Platform' folder, with 'Variant' argument, for example:
/Variant:"Electric P8"
