Re: Access Violation - 1.5.8.305 (General questions)
Hi. THanks. I'll check it out, but I'm not sure if this can be fixed since property bag changes can cause previous EXEs to crash in that case.
I would suggest, anyway, to switch to COM version. It's same sample but everything is done from the code.
So, this error is now gone?
Kreso
Complete thread:
- Access Violation - 1.5.8.305 - selisoft, 2011-04-27, 22:56
- Re: Access Violation - 1.5.8.305 - wodSupport, 2011-04-27, 22:58
- Re: Access Violation - 1.5.8.305 - selisoft, 2011-04-27, 23:19
- Re: Access Violation - 1.5.8.305 - wodSupport, 2011-04-27, 23:21
- Re: Access Violation - 1.5.8.305 - selisoft, 2011-04-27, 23:32
- Re: Access Violation - 1.5.8.305 - wodSupport, 2011-04-27, 23:21
- Re: Access Violation - 1.5.8.305 - selisoft, 2011-04-27, 23:19
- Re: Access Violation - 1.5.8.305 - wodSupport, 2011-04-27, 22:58