Hey there tom, big fan of your work.
I am running ResXManager hosted in Visual Studio Community 2013 and implementing WebSite projects with ASP.Net WebPages.
Since update 1.0.0.57, I've been having an annoying error popup each and every single time I edit a resource field saying "Value cannot be null. Parameter: source". It has an OK button that I can click on and (seemingly) the popup disappears and nothing gets changed or affected, except that I have to hit Return about a thousand times every hour.
At this point, I am not 100% sure if ResXManager is entirely responsible for this, but it is driving me crazy.
Just to be clear, it is not a one-off or per-project problem. It is systematic every single time that a row goes out of focus (when I finish inserting all the items for 1 row or when I create a new row for example).
Would appreciate any help/update on this.
Regards,
Alex
Comments: ** Comment from web user: alexandrepigeot **
I am running ResXManager hosted in Visual Studio Community 2013 and implementing WebSite projects with ASP.Net WebPages.
Since update 1.0.0.57, I've been having an annoying error popup each and every single time I edit a resource field saying "Value cannot be null. Parameter: source". It has an OK button that I can click on and (seemingly) the popup disappears and nothing gets changed or affected, except that I have to hit Return about a thousand times every hour.
At this point, I am not 100% sure if ResXManager is entirely responsible for this, but it is driving me crazy.
Just to be clear, it is not a one-off or per-project problem. It is systematic every single time that a row goes out of focus (when I finish inserting all the items for 1 row or when I create a new row for example).
Would appreciate any help/update on this.
Regards,
Alex
Comments: ** Comment from web user: alexandrepigeot **
Hey there, me again.
I have upgraded to Win10 in the last few days and it seemed to have stopped completely. Unfortunately, I didn't think of getting an output log for reference.
And seeing as nobody else had the problem save for me, it might have been a misconfigured environment on my end. I am sorry for the trouble. If it ever happens again, I'll try and get a log along with my request.
For reference my system was running Windows 7 Ultimate SP1 x64 at the time, and I was using BOTH Visual Studio Community 2013 and 2015 (I'm thinking maybe a conflict between the plug-ins).
Thanks a lot for your reply.