ndepend

C#/.NET analysis tool to find race conditions/deadlocks

守給你的承諾、 提交于 2019-11-27 03:49:24
Is there a tool that analyses .NET code and finds race conditions? I have a bit of code that has a public static property that gets or creates a private static field. It also has a public static method that sets this field to null (...yes, I know!..) As there are no locks around either of these methods, it's a safe bet that things'll go horribly wrong in the future. I need a tool that'll recursively go through things that call either of these methods and see if anything was spawned on another thread. I'm looking for a tool or perhaps an nDepend SQL script (if this is possible). You're probably

Resolving MSB3247 - Found conflicts between different versions of the same dependent assembly

只谈情不闲聊 提交于 2019-11-26 16:51:11
A .NET 3.5 solution ended up with this warning when compiling with msbuild. Sometimes NDepend might help out but in this case it didn't give any further details. Like Bob I ended up having to resort to opening each assembly in ILDASM until I found the one that was referencing an older version of the dependant assembly. I did try using MSBUILD from VS 2010 Beta 2 (as the Connect article indicated this was fixed in the next version of the CLR) but that didn't provide any more detail either (maybe fixed post Beta 2) Is there a better (more automated) approach? AMissico Change the "MSBuild project

C#/.NET analysis tool to find race conditions/deadlocks

怎甘沉沦 提交于 2019-11-26 10:56:23
问题 Is there a tool that analyses .NET code and finds race conditions? I have a bit of code that has a public static property that gets or creates a private static field. It also has a public static method that sets this field to null (...yes, I know!..) As there are no locks around either of these methods, it\'s a safe bet that things\'ll go horribly wrong in the future. I need a tool that\'ll recursively go through things that call either of these methods and see if anything was spawned on