Where is VB.Net taking us? 2

[johnk]

As a developer/maintainer of lots of VB6 code I've been looking into what it will take to convert to VB.Net. It's not a pretty picture.

Obviously this Microsoft move has major implications to developers like myself who have chosen Microsoft VB some time ago in the expectation that future versions of the language tools would be evolutionary in nature and not revolutionary.

So, do we:
1. Commit the time and effort to convert to VB.Net, or
2. Live with VB6 forever, or
3. Wait for a good VB7 set of tools from somewhere, or
4. Switch to Java, C# or something else?

The professional VB development community should have some things to say about this issue, and I think Tek-Tips is an ideal place to say it. I am alarmed about this issue. Anyone else?

John Kisner

 

[chiph]

I just installed the .NET beta 1 last night, and only got a brief chance to look at the IDE.

Wow, what a lot of changes!

I think the learning curve will be at least as steep as when objects got added in VB4, if not steeper.

My opinion is that porting VB6 programs over will be too time-consuming. VB.NET is likely to only be used for new development.

So far as taking the time to learn .NET, I recall the people who put off learning objects. They were left behind (skill-wise). So I'm going to make the effort to learn it, even if I don't have a particular project to use my skills on just yet.

Did you see that MS has backed off on some of the changes in VB7? They've decided to keep the array index starting at 1 by default (it will also continue to allocate a 0-element, too). So if you want an array of 5 elements, it will allocate 6 elements, 0 to 5.

Chip H.

 

[Ferlin]

Hi,

I haven't researched VB.NET real heavy yet, although I need to. But it is my understanding that if our existing code is written to take advantage of objects and heavly driven by classes. The conversion will be less work, then those applications that are not so object based, but rather written using the old structured programming method. I have an article some where that tells what you can be doing now to your VB6 code to make the conversion to VB.NET much smoother and less time consuming. At any rate programs now should be written Object Oriented instead of Structured Programming Methods. I guess I need to get busy with my RESEARCH.

Ferlin.

 

[browneye]

Hi Guys
I have tried to install VS.Net Beta 1 on windows 98. it gives me error some ATL error when I open new webapplication.
Then I swithched to Windows 2000 and Installed successfully VS.Net. But it screwed up my Microsoft Office Premoium (2000).
Now If I start word,excel,access whatever ,word comes up if i click any where it kickes me out without any error.
I tried drwatson it says no errors detected.

Any idea?

thank you in advance

 

[Ferlin]

tp0724,

What error does it kick you out with? I was getting an error on my access about no license on this machine. I checked the FAQ's I believe it was in Microsoft Access General Discussion Forum and found the solution. Worked great for me.

Ferlin.

 

[browneye]

Ferlin,
thank you for quick response. It doesnt give me any error. Just kicks me out.
Any idea about installing it on Windows'98

thank you

 

[Ferlin]

tp0724,

Hmmmm, I see what your saying now. Are you running both Windows 98 and Windows 2000 with a boot choice? I assume you have Uninstalled and Re-Installed the Microsoft Office. Due to the differences in the Register formats between Windows 98 and Windows 2000, usually when you install 2000, you have to reinstall any register driven software.

Just a thought.

Ferlin.

 

[johnk]

Ferlin & tp0724,

I appreciate the need to deal with the nuts & bolts of making the new IDE load & work, but in this thread I am looking for a discussion of what this new technology means to us. Maybe another thread or forum would be work better for your issues above.

Thanks,

John Kisner

 

[Ferlin]

johnk,

Sorry about that I guess it was kind of off topic for this thread.

Ferlin.

 

[chiph]

John -

What are your employer's (if any) plans to migrate to VB7?

Chip H.

 

[johnk]

Chip, We are a small group of developers who have created application packages for distributors, manufacturers and some misc. others. Since we aim to have multiple buyers of our packages, it is a serious thing for us to change our software technology.

We've been at this since 1974. First with IBM midrange, then with UNIX (using Informix and Oracle), and now, since 1996, Microsoft & VB. We hadn't gone very far with VB3 when VB4 came out with classes. From VB4 through VB6 the new versions were mostly incremental and we were able to upgrade our packages without much time & expense.

But now I'm concerned that we will have to do much rewrite to bring our packages up to VB.Net level.

At this point I have no plans to move my business to VB.Net. Ultimately we will have to advance to something, but I'll have to find justification for such a big change.



John Kisner

 

[Ferlin]

johnk,

Have you seen the thread in VB General Discussion Forum, started by Sentil about VB.NET, it goes right along with this thread.

Ferlin.

 

[neilkonitzer]

If you're a VB web developer, then .NET is definitely the way to go, and yes, there will be growing pains. Due to the upcoming MSIL (Microsoft Intermediate Language), if you're only developing desktop apps, then it is highly recommended that you stick with VB 6.0. Visual Basic Programmers Journal did an article on this very thing a few months ago. It was almost scary.

 

[johnk]

Thanks, Neil.

One thing that has come through loud & clear is that we developers are a very mixed lot. My concern about keeping my commercial packages up to date through new releases is different from those who develop custom apps. My needs with multi-tier "fat" client apps are different from those who develop web enabled apps. And then there is the issue of how best to web enable my fat client apps.

Looks right now that we will pass on VB.Net for now & look at it again when it's time to add a web front end.

John Kisner