Thanks for the feedback, I'll look into it.

Cheers,

Nathan Rover

Alright guys,

I think I've got this taken care of, there was an issue with the loop that determines the min version that would have effected the .Net version number. Basically in the event that a module references an assembly like System.Data that has the same version number (2.0.0) in multiple frameworks (2.0, 3.0, 3.5), it would report the max version.

Mike, I also found an issue with a reference to System.WebExtensions which is reference by your project. That assembly isn't officially shipped in the GAC until .Net 3.5. However that assembly is included in DotNetNuke starting with version 04.05.00. Seeing as DNN 04.05.05 is the minimum required version of your module. Your module would not result in an assembly reference error running in .Net 2.0. I've added some logic to pick up on this special case. Once I made the above updates, your module is now reporting a minimum .Net version of 2.0

Eric, the main issue above is what resulted in your module being reported at a minimum version of 4.5. I also found that in my collection of assembly data that I use to determine the minimum .Net version I had listed System.Core as first appearing in .Net 4.5. After some research it seems that system.core was first introduced in 3.5 but also ships with 4.0. Once I made the above updates, your module is now reporting a minimum .Net version of 4.0

Again, thanks for the feedback.

Please let me know if you find any other issue, or have any questions about this update.

Cheers,

Nathan Rover