12-06-2018 05:27 PM
Thank you for your reply. Yes, that assembly exists in the C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Act.Framework folder. Should I delete it?
12-06-2018 05:35 PM
No, the folder is NOT empty. There is an Act.framework.dll there. Even if I rename this file, the error occurs.
Not sure what else to do.
Do any of you see an empty assembly folder named v4.0_18.104.22.168__ebf6b2ff4d0a08aa when looking at your .net assemblies at C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Act.Framework ?
12-11-2018 10:15 AM
I have written the tester as you stated and it worked fine on my act v21 update 4 system. Send me your tester app and I can see what the problem is...
I tested in debug and release as well and no issues.
I am very aware of inability to debug for plugins via studio etc, but writing against framework is working in my and our tests. Also, it should be noted that custom tables is a plugin for Premium Plus and that is working fine as well.
12-11-2018 12:03 PM
Thank you for your response. Did you talk to Billy Clark ? He managed to duplicate the issue at your site.
I've attached a very simple project that crashes every time. It instantiates Act.Framework.actframework and opens the database. VERY simple. Crashes every time.
I'm running Windows 10 Pro with ACT 21 with update 4.
Also, I've made a video of the problem.
Note, I was running Act! 20.1 and everything worked fine. I installed Act 21 and then started running our tests. I have not entered the license to activate the product.
12-11-2018 12:06 PM
Here is the direct link to the video.
The link on the posting does not seem to work.
12-11-2018 12:10 PM
12-11-2018 02:42 PM
Using your code it still works just fine for me, add an exception try catch and put messagebox with error, I think something must be wrong with image or dll is failing to load for some reason.
IS anyone else having this issue who is not trying to debug?
12-11-2018 02:51 PM
Actually no, that is not what they are saying. They are saying they are unable to DEBUG or attach a debugger, that is completely different from what you are saying and that's why I looked into it. You are saying you cannot connect and login to the act! framework with the code above - even if you are not running via the debugger - Correct?