vb.net - In-Design Mode error - "Resource has no property named 'myResource'" -

We actually get a strange scenario where we have resources in the project marked as embedded.

The studio environment in view, during the development process, is the error of return:

Type 'ourProject.My.Resources.Resources' in the name of 'tlSearch_Image' Property is not

but I promise that it exists! When we go into the properties of the project, we see it. And any other resources are not failing, so they are fine, it is more than one! Even Intelisence allows us to refer to it without any compilation errors.

Here are the attempts we have made:

• Clear solutions / reconstruction = FAILED
• Deleting Debug (in OBJ and Bin) We have everything in the folder of FAILED
• Restarting our computer (Microsoft, Yay !!) = FAILED
• Delete everything, and get everything back from our SVN trunk = FAILED
• Remove the image from the designer, and add it back = FAILED
• Rescue me from the project resources Trying to remove it, and add it back ... work for one time (like a few minutes) and then = FAILED
• dancing around the computer with a party cap = FAILED

And to add complexity, it only fails my computer ... not on any other computer in our team and yesterday worked very well. All this, even if there is no major change since then. But anyway, our team is on the same SVN version ... and I'm the only one who fails.

Anyone has already experienced it already because it is really unique because I can not see my form when I'm developing ... but I do not know if debugging ( F5 ) And it does not fail. Please note that this is not a self reference problem as we have seen in other posts from Google search results.

Our Environment: Windows 8.1, Visual Studio 2008.net Framework 3.5

Edit

Anything we tried was the removal of the resource, Save it from tlSearch_image instead of tlSearch ) and it worked for one day ... or so Again, it crashes my designer once more. And still only for me! Now we are thinking that this is no graphical issue or nothing! Please help!

Edit # 2

Okay, now, I'm not alone ... two other colleagues are facing the same error ...

Princescreen of what I have found here: