>Again, you miss the point or just choose to ignore it. We cannot de-empahisize in our RFI's. They want to know where each dll came from, its language, its connections to other dll's, etc.
>
>I take your point, but once you're a NET dll you don't have a "language" any more. Isn't that the whole point of assemblies, IL and the CLR? In this case, if the compiler produces assembly then it's "written" in assembly. Certainly it isn't written in VFP and bears absolutely no connection to VFP any more.


Let me type this really slow... O U R C U S T O M E R S W A N T T O K N O W W H A T L A N G U A G E W A S U S E D for each and every dll, com object, web service, etc. It happens to be the first quesiton on the RFI. Regardless if it is compiled to IL, they still want to know what was used, all programs, etc. So we have to list Visual STudio, c#, blacklight controls, silverlight controls, any open source, etc. You can argue till your blue in the face that it doesn't matter, but it does and mainstream customer want to know what it is when they are paying 7-8 figures for a program and license fees. For instance, we can't use EF yet, because of a security hole that will be repaired in v2.