Preparing for the Next Product Cycle (Matt Gertz)

re: Preparing for the Next Product Cycle (Matt Gertz)

JamesNT — Thu, 31 Jan 2008 16:34:26 GMT

And to think I'm not even done mastering VB 2005 yet!!

JamesNT

re: Preparing for the Next Product Cycle (Matt Gertz)

VBTeam — Thu, 31 Jan 2008 21:55:16 GMT

:-) We're glad to help you gain mastery, of course! Along those lines, I'd like everyone to note that there's a *lot* of VB content on the aforementioned MSDN Code Gallery -- not just my apps, but a lot of other very cool VB-oriented pages as well.

--Matt--*

re: Preparing for the Next Product Cycle (Matt Gertz)

JamesNT — Fri, 01 Feb 2008 04:40:17 GMT

While the new stuff may very well be cool, don't forget us ancient VB 2005 guys! We'll be using it for a while - not everyone can upgrade at the snap of a finger. In fact, we are upgrading apps from VB6 to VB 2005 now.

JamesNT

re: Preparing for the Next Product Cycle (Matt Gertz)

VBTeam — Fri, 01 Feb 2008 23:51:30 GMT

Absolutely! One of the major goals that I set out to achieve when starting my blogging here was to focus on what you could *already* do with the tools at hand. It's of course fun to hear about what's going on for future releases, and I reserve the right to get really excited about it in my posts on occasion, but I'm still focused on writing good code with what's available. That will sometimes include exploring technologies introduced in 2008 (such as LINQ) since it is now available, but in those cases there's the option of trying it out for free using the Express editions if you get interested in what I'm writing about for "future considerations."

Since you brought it up, one thing I'd really like to get into but haven't yet are articles like "You did it that way in VB6 -- the equivalent is this way in VB.NET." I've been curtailed in this by the fact that I don't have VB6 installed at home to verify my code, and home is where I do most of my blogwork. (I have the VB6 disks somewhere but haven't reinstalled it since getting my new machine last year -- I need to find them.)

re: Preparing for the Next Product Cycle (Matt Gertz)

Sys64738 — Wed, 06 Feb 2008 22:19:07 GMT

Could you please elaborate about next VB?

I'm very curious... it seems that VB is already super-powerful and feature-rich as it is in VS2008! :)

What's next?

re: Preparing for the Next Product Cycle (Matt Gertz)

Herbert — Sun, 17 Feb 2008 01:27:59 GMT

Some requests from my job as a teacher for programming languages:

1) Please make it easier for novice programmers to ship applications:

- creating setups including databases, resourcefiles, ... with a single wizard.

- include License Providers for checking MAC adresses, hard disc serial numbers and a management service to handle customer's licenses

- force MS-PRESS to include Visual Basic in all books handling new themes (I am fed up with translating C# to VB)

- support application configuration files per assembly

- support special exception handling not only for windows apps, support also windows services and console apps.

- VS should name all thread it starts, It's annoying when debugging that threads are stopped/fail whose purpose cannot be seen.

2) include spell checker for XML comment and line comment

3) make it easier for multiple persons to work on the same solution without VSTS. Most often circular references need a redesign, can this be weakened?

次の製品サイクルへの準備 (Matt Gertz)

The Visual Basic Team — Fri, 06 Jun 2008 07:53:32 GMT

昔、高校のコンピュータサイエンスのクラスで A を取るために、短期間にジャグリングを習得しなければならないことがありました。これは作り話ではありません。全身を使って行うジャグリングは、プログラムを記述する作業に何となく似ています。とにかく、そのときにはそれが意味のある作業だったのです。