(I'm sorry, I can read most of VB.net but I can't write it. But I figure you will get my point after all.)
I have the same problem with C#.
Since posting this I have run into a number of brick walls - the main problem being the way Fileup treats asp and asp.NET in two different ways, so just porting an existing asp app. is not going to work - it was back to basics and then more hassles with Database connections (a ported asp app. will allow OLEDB connections via MS Provider for ODBC connections but pure asp.NET will not) and a host of other. The same old Micro(spit)soft hassle - if you don't use their SQL Server (how did they get away with naming a commercial Database product after a language anyway? - 'nuther soapbox!) then compatability is a joke! We were totally unable to use .NET with a Sybase back end with Framework 1.0 but the later version has improved things - a bit!