How long can you milk VB6/ASP/SQL for....?

[DimPrawn]

Have you managed to screw up your tiers yet and merge dlinq quries into your ui and bo's))

The future's messy, the future is linq

Sadly, C# 4.0 doesn't exist yet, but if Threaded will let me borrow his timemachine.......

[TheMonkey]

Does that include VB that's in Office too? I haven't yet looked at the new flavours of Office coming out so I'm well aware that this is probably a very stupid question.

VBA isn't changing with Office 2007 - it's still the same old tulipe.

[HankWangford]

Linq

I feel sorry for the guys using C# 2.0 when I'm using C# 4.0 already.

Have you managed to screw up your tiers yet and merge dlinq quries into your ui and bo's))

The future's messy, the future is linq

[TheMonkey]

Ironically the last two jobs I've worked on have been advertised as C# but I end up with some ASP/VB6/COM nightmare to test my patience for the first month...

It's out there and still being used but don't count on it for much longer.

[ladymuck]

Are you blond?

Nope, brunette.

[DimPrawn]

I feel sorry for the guys using C# 2.0 when I'm using C# 4.0 already.

[funkyd]

VB6 on a CV today just looks crap imo. It shows that you haven't kept up with things and are years behind everyone else.

When you have learnt .NET skills, you will have limited experience and a cv full of VB6. Why don't you look at migrating some of your VB6 projects to .NET - sell it to the client and learn off the back of it....

[Gold Dalek]

Does that include VB that's in Office too? I haven't yet looked at the new flavours of Office coming out so I'm well aware that this is probably a very stupid question.

Are you blond?

[ladymuck]

Does that include VB that's in Office too? I haven't yet looked at the new flavours of Office coming out so I'm well aware that this is probably a very stupid question.

[DimPrawn]

According to MS, Visual Basic 6.0 will no longer be supported starting March 2008.

So there will be no service packs, security/hot fixes beyond that point, or any plan to ensure old VB6 apps run okay on future Windows platforms.

Therefore, you've probably got another 3 or 4 years before the market for those skills is truly gone.

Enough time to learn .NET I would think, but I'd start now with VS.NET 2005 and if you have any C/C++/Java experience try and move to C# rather than VB.NET, as it is a more marketable skills.

[Shimano105]

Keep meaning to pursue my numerous .NET projects (that's the future after all - M. Benes).

Trouble is, I keep getting VB6 contracts offered, and a bird in the hand etc.

So, how long before we're on .NET 3000 and I'm an unemployable wretch living in a shop doorway (smelling like Xoggoth)?