Hi,
Thanks for trying to help me, even though it isn't your area of expertise. It is much appreciated!
I'm running a trial version of Version 11.1, Build 1111 08-September-2014.
The application I am trying to run is a C# solution with 31 projects. In the solution there is a Windows Service and a setup project, but mostly there are projects that will compile to dll's and associated projects that compile to executables and allow one to test the particular associated dll. The part that I have been trying to debug/record with EA would probably be classified as a Windows Application. It needs a connection to a database, and there is also a Visual Studio Addin (though not in the part that I am trying to debug at the moment).
It is compiled for x86, and some of the other projects for Any CPU. None of the projects are explicitly set to x64.
The config I mentioned is MyApplication.exe.config, and it resides in the same folder as the exe and pdb.
I have tried importing the code and writing a build script (which I got from the Build output in Visual Studio), but then I got a different error. Guess I will make a different thread for that, as this thread is concerned with attaching to the process.
I have tried running MyApplication.exe, and then tried to attach to it via EA, (as explained in the original post), and I have also tried debugging it in Visual Studio and then attaching to it (i.e. MyApplication.vshost.exe), but I'm not sure whether that is actually a legitimate way of doing things.
In the Execution Analyser window I have added a new script with Microsoft.Net as the Debugave ger and the Default Directory as the folder in which the exe lies.
I have managed to debug and record a totally different little project, but this application is the main focus.
I found this interesting, but it is a bit outdated:
http://www.sparxsystems.com/resources/demos/debuggingcs/debuggingcs.htm