From f75e72757e36afb051e586733a1d37802e01ef16 Mon Sep 17 00:00:00 2001 From: Simon Rozman Date: Tue, 4 Sep 2018 11:37:19 +0200 Subject: [PATCH] VS10Solution.sln => GEANTLink.sln --- VS10Solution.sln => GEANTLink.sln | 0 MSILocal.mak | Bin 15068 -> 15044 bytes Makefile | Bin 208594 -> 208546 bytes README.md | 4 ++-- 4 files changed, 2 insertions(+), 2 deletions(-) rename VS10Solution.sln => GEANTLink.sln (100%) diff --git a/VS10Solution.sln b/GEANTLink.sln similarity index 100% rename from VS10Solution.sln rename to GEANTLink.sln diff --git a/MSILocal.mak b/MSILocal.mak index d7a47fa7e23724d3039c34521ccc9e3b29b06188..1f9b684ee917201801c11247c84ac5cd2dac90fa 100644 GIT binary patch delta 117 zcmcapdZcuM8KcEU^Xo!_?hLLBjtqVbAq+kYnGAUh*^@a%WGAzT3QP_XUVv5hI95@R Po;6ryG&g?`eWL;ZpO_o* delta 133 zcmX?7dZ%=P8Kc=o^Xo$5VGO|xh71NkGM^!bp_HM7Arr{Tn=CJU7N^{LQO(I}BJ*&{ T%M0sHW)hu)OMdfuQBhR@!pAqr@))uwyL0PKp1@^*MdmtJBo)5o(X1*W*f~#xx~X5f*A}M41i=lLk>eJLkUABkd-%iKDX@TDlP{+@|x3E zu`vlup2ekrM-j*nfyqhSI=Iv{&*$DgpPSM94K4-K8`+p-w@dtBjNrqiWIIraDNb3i b0n>p72yFi%!lZ*!UAv(&({@8;=0a`&wIV~h diff --git a/README.md b/README.md index 6aed7de..f470ec2 100644 --- a/README.md +++ b/README.md @@ -93,7 +93,7 @@ GÉANTLink has some submodules. When cloning Git repository, make sure to use `- After clone is complete, grant _Users_ local group read and execute permissions to `output` subfolder (when working folder is private). This allows _EapHost_ service to load GÉANTLink's DLL, and Event Viewer to display GÉANTLink events. -GÉANTLink can be build and debugged opening _VS10Solution.sln_ in Visual C++ 2010 IDE. +GÉANTLink can be build and debugged opening _GEANTLink.sln_ in Visual C++ 2010 IDE. Before one can attempt to debug EAP DLLs, you should run `nmake register` from an elevated command prompt. See _Building in command line_ chapter below. @@ -102,7 +102,7 @@ Next, one must configure a network profile actually using GÉANTLink for the aut GÉANTLink EAP modules are divided into two DLLs: backend (i.e. _EAPTTLS.dll_) and GUI (i.e. _EAPTTLSUI.dll_). ##### Backend DLL -The backend DLL is loaded by _Eap3Host.exe_ process when connecting to the network. One approach to debug the module is to start Visual C++ elevated, open _VS10Solution.sln_, and attach to the running _Eap3Host.exe_ process. +The backend DLL is loaded by _Eap3Host.exe_ process when connecting to the network. One approach to debug the module is to start Visual C++ elevated, open _GEANTLink.sln_, and attach to the running _Eap3Host.exe_ process. On initial connection attempt _Eap3Host.exe_ will load the DLL and will not release it until _EapHost_ service is restarted. To release our DLL (i.e. for rebuild) you have to restart _EapHost_ service manually or run `nmake register` again.