mikemontana
03-13-2000, 02:03 AM
1) Ability to send TRACE messages to an OLE logging facility that will work
in both anonymous signons (ie an IIS DLL) as well as an authenticated signon
(ie standard VB desktop app)
2) Ability to natively edit RES files
3) TRY..CATCH..FINALY error trapping - the ON ERROR stuff is nasty
4) Ability to query interfaces at runtime - closer integration to the OLE
IQueryInterface stuff.
5) Ability to write multi-threaded apps (why not its a "Wish List" anyway!)
6) Better integration with MTS - so that VB components can be pooled
7) Runtime introspection - much like the Java Introspection. I want to be
able to determine at runtime what function I'm in, and programatically determine
what methods are available to me.
8) Clean up of the tri-states - NULL, EMPTY, NOTHING etc - while I understand
the meaning of the seperate states they frustrate me when testing for values
of variables. I would like the three to be programatically the same so that
a test for NULL is equiv as a test for EMPTY.
9) Better run-time dependency determining for distributions. The current
DeployWizard in VB6 is really really good. Needs a little polish.
10) Ability to write a VB service directly. (Its a wish list afterall)
11) Ability to pass values into a constructor/class_initialize event.
12) Continued support for the VB Editor extensibility - what a great job
they did with VB6's extensibility.
13) Better string handling algorithms. Right now every time I want to append
a string to a string a whole new string is allocated, teh prev copied + new
string, and the old one is freed. What a dog - especially when building lots
of HTML in a VB IIS DLL. MFC's string class has the ability to pre-allocate
a buffer size - and then auto-trim it when you're done with it. This is what
I'd like.
14) A better method of handling cross project compile dependencies. I go
looney when I have one DLL thats shared by 3 other apps and when i make a
daily build of code the CLSID gets changed and the dependent apps no longer
compile. Try making sense of the three Project Compatibility modes. I dont
have this problem with VC++.
15) A GUID as a native data-type. We all know that a GUID is sorta like a
string, and sorta not. Sorta.
16) Improved #IF...#END IF support. I use this alot and its still pretty
primitive vs. C++ - expansion of the preprocessor would be great. For example
I'd like to be able to declare a whole set of functions as a conditional
compile like:
#IF DEBUG_MODE THEN
Public Sub DEBUG_DoSomething()
...
End Sub
Public Sub DEBUG_DoSomethingElse()
...
End Sub
#END IF
17) Ability to programmatically determine if the app is in Debug/Environment
Mode or in Compile mode (part of introspection I guess).
18) PLEASE RETURN MSDN to a standard-windows format! ooooh i really dislike
the HTML versions... but, admittedly, they are getting better as HTML improves.
19) An improved Collection/Dictionary object. Gee, I'd really like to be
able to programmatically determine if a collection contains an item without
iterating thru the whole thing, or by using nasty ON..ERROR stuff.
20) A nice way to have IIS "shake loose" a VB DLL without having to START/STOP
the Web publishing service. RIght now if you execute a VB-DLL thru an ASP
page the DLL gets "stuck" in memory until IIS is shut down. That hurts.
in both anonymous signons (ie an IIS DLL) as well as an authenticated signon
(ie standard VB desktop app)
2) Ability to natively edit RES files
3) TRY..CATCH..FINALY error trapping - the ON ERROR stuff is nasty
4) Ability to query interfaces at runtime - closer integration to the OLE
IQueryInterface stuff.
5) Ability to write multi-threaded apps (why not its a "Wish List" anyway!)
6) Better integration with MTS - so that VB components can be pooled
7) Runtime introspection - much like the Java Introspection. I want to be
able to determine at runtime what function I'm in, and programatically determine
what methods are available to me.
8) Clean up of the tri-states - NULL, EMPTY, NOTHING etc - while I understand
the meaning of the seperate states they frustrate me when testing for values
of variables. I would like the three to be programatically the same so that
a test for NULL is equiv as a test for EMPTY.
9) Better run-time dependency determining for distributions. The current
DeployWizard in VB6 is really really good. Needs a little polish.
10) Ability to write a VB service directly. (Its a wish list afterall)
11) Ability to pass values into a constructor/class_initialize event.
12) Continued support for the VB Editor extensibility - what a great job
they did with VB6's extensibility.
13) Better string handling algorithms. Right now every time I want to append
a string to a string a whole new string is allocated, teh prev copied + new
string, and the old one is freed. What a dog - especially when building lots
of HTML in a VB IIS DLL. MFC's string class has the ability to pre-allocate
a buffer size - and then auto-trim it when you're done with it. This is what
I'd like.
14) A better method of handling cross project compile dependencies. I go
looney when I have one DLL thats shared by 3 other apps and when i make a
daily build of code the CLSID gets changed and the dependent apps no longer
compile. Try making sense of the three Project Compatibility modes. I dont
have this problem with VC++.
15) A GUID as a native data-type. We all know that a GUID is sorta like a
string, and sorta not. Sorta.
16) Improved #IF...#END IF support. I use this alot and its still pretty
primitive vs. C++ - expansion of the preprocessor would be great. For example
I'd like to be able to declare a whole set of functions as a conditional
compile like:
#IF DEBUG_MODE THEN
Public Sub DEBUG_DoSomething()
...
End Sub
Public Sub DEBUG_DoSomethingElse()
...
End Sub
#END IF
17) Ability to programmatically determine if the app is in Debug/Environment
Mode or in Compile mode (part of introspection I guess).
18) PLEASE RETURN MSDN to a standard-windows format! ooooh i really dislike
the HTML versions... but, admittedly, they are getting better as HTML improves.
19) An improved Collection/Dictionary object. Gee, I'd really like to be
able to programmatically determine if a collection contains an item without
iterating thru the whole thing, or by using nasty ON..ERROR stuff.
20) A nice way to have IIS "shake loose" a VB DLL without having to START/STOP
the Web publishing service. RIght now if you execute a VB-DLL thru an ASP
page the DLL gets "stuck" in memory until IIS is shut down. That hurts.