|
|
I was getting ready to put out a preview for PainlessSVN Professional out for the people who have signed up for the Beta. Unfortunately, there is a problem with .NET Reactor protected MMC 3.0 assemblies not loading in the MMC console. Apparently, the new .NET libraries for MMC call reflection on startup, and some objects are not being recognized. This throws a System.Reflection.TargetInvocationException.
I got a response from Denis Mierzwiak, their CTO. They are looking at the problem. I'll make another entry, once I hear from from them. It seems that I always get stuck with obscure problems. This is something that I must have inherited from my dad. He has a knack of breaking "unbreakable" tools (wrenches and the like). He's even broken several heavy duty pickups. Heavy duty axles, brakes, and transmissions are no match for my dad!
On a positive note, the SVN Backup Widget is almost done. I've only been able to work on it for about an hour a night. I'm hoping to get it done this Saturday, so that I can start having scheduled backups of my repositories. I'll make an announcement when this utility is finally done. This will be a free download. Just wanted to give something back tot he community. 
Previous Page | Next Page
COMMENTS
What solution have u found for the System.Reflection.TargetInvocationException. I have the same problem but with only few pcs. Is it a windows update problem?
The issue is related to merging assemblies. Some namespaces in .NET do not play nice with merged assemblies. MMC related code is non-merge friendly. The solution is to not merge the assemblies. I obfuscate them, but not merge them anymore. That stopped my particular issue.
The System.Reflection.TargetInvocationException is thrown by a lot of stuff. It's one of those generic exceptions that gets thrown whenever there is a problem between Reflection and the assembly being read.
