Before I go too far down this road, let me just make sure I'm not screwing up something stupid. I'm using VS2005, could that be an issue? I honestly didn't check the levels of support on it, but just wanted to bring that up.
It's definitely possible for the VB compiler to be getting screwy. I've actually had it flag a single line before as duplicate code. Sounds impossible, but I commented out the line and it didn't flag it, then un-commented it and it came back. Logically it made sense to move the line to another point in the method and that ended up fixing it. Doubt I'll be able to recreate that little bug, but it might be indicative of something weird with the VB compiler. I hacked together a small sample that is still generating the issue for me. I have the two versions (one compiled with optimizations and one without optimizations) so I'll get to uploading them in a little bit. This isn't like a deal breaker for me I was just wondering if other people saw what I was seeing. I actually see a good amount of strange behavior when it comes to using this utility with VB.NET, and so far I've just been ignoring it and skipping over it. Perhaps I should post a little more of those things over here. -- You received this message because you are subscribed to the Google Groups "Gendarme" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/gendarme?hl=en.
