MySQL Bugs: #65320: Workbench 5.2 Common Language Runtime detected an invalid File

Bug #65320	Workbench 5.2 Common Language Runtime detected an invalid File
Submitted:	15 May 2012 17:57	Modified:	26 May 2012 16:09
Reporter:	Martin Pirringer	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.x	OS:	Windows (7.0)
Assigned to:		CPU Architecture:	Any
Tags:	not starting

Description:
I had Workbench 5.2.37 working fine Saturday. Today when starting it it comes up with a window stating

MYSQL Workbench Unexpected Error

MYSQL Workbench has encountered a problem

Common Language Runtime detected an invalide File

Nothing has changed on my computer except maybe an automatic update from Windows

Uninstalled WB and reinstalled the latest (5.2.40) same result.

any ideas?

How to repeat:
Don't know if its specific to here. Otherwise just click on the icon

Hello martin,
Thanks for your report, Can you please confirm if you have installed: "Microsoft Visual C++ 2010 Redistributable Package (x86)" in your system?

If not, can you please install it (http://www.microsoft.com/en-us/download/details.aspx?id=5555) and give a second try?
Thanks in advance!

I have Visual C++ 2010 Redistributable 10.0.30319 Installed. To make sure I removed it and reinstalled it from the link provided - same result I also got 2010 x64 and x86 Runtime 10.0.40219 Install, Visual C++ 2010 expres and MS VS 2010 express with service Pack 1 and a whole slew of C++ 2008  and 2005 Runtimes and Redist.

Remember it has been working for years. I have been using WB since 5.1 now and been upgrading. Something must have changed

HTH

Got it resolved. Between the last time of it working and the time it started to give the error Microsoft updated both the C++ and the .NET 4.0 programs. I removed WB, removed anything C++ related (including VS10) an all .NET 4.0 components. Then I reinstalled .NET 4.0 and the C++ runtime an WB 5.2 an it works. Will now start to reinstall the other dependancies for C++ runtime and the .NET Client. So far so good. It might be helpful if WB could give a more specific message when it does not load as to which file and/or process caused the failure