Panagiotis Kanavos:The tool is quite useful for creating estimates, but I feel that the data it uses is quite old now. In particular, the LOC estimates for VB.NET and C# feel wrong, with VB.NET requiring almost half the LOCs per feature point that C# does. My experience is that the two languages are equivalent in terms of LOCs/feature. In fact I've started using VB.NET instead of C# in my estimates in order to get realistic results.
You're right that it's been a few years since we released a new version of Construx Estimate, but we have no plans at this time to update it.
The variance in "lines of code per function point" has always been very high when you're using industry average data. Whether you're using the tool now or when it first came out 10 years ago, you can introduce a lot of error into your estimate with just that one conversion factor if your organization's lines of code per function point aren't the same as the industry average. Your estimates will be more accurate if you create your estimate in Construx Estimate in terms of LOC instead of function points.
If you're already entering your size information in terms of lines of code, then the programming language you choose doesn't numerically affect the estimate; it's just used for documentation (i.e., in the reports).
Panagiotis Kanavos: I also feel uncomfortable installing a VB6 application in my Vista 64 computer. It is the only application installed that uses VB6 and the old setup wizard.
VB 6 is supposed to run under Vista 64, isn't it?! If you find any specific issues on your Vista 64 computer, please let us know.