Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Best Development Environment 1

Status
Not open for further replies.

KenWK

Programmer
May 25, 2001
76
US
I'm wondering if anyone can offer some suggestions regarding the best .NET development evironment.

We also need to start moving our VB 6 stuff (yeah, I know, its about time!) to .net in a hurry and I'm hoping some you experienced with this can suggest the best product.

One thing I REALLY love about VB 6 is the interactive object model that makes menus drop down as you're typing. I'm really hoping there are similar things in the .net development. Does Visual Studio do that?

Thanks very much,
Ken
 
My guess would be to re-do your VB 6 applications in VB.NET
As far as ‘menus drop down as you're typing’, if you are talking about Intellisense, yes – VB.NET has that, too. And so much more... :)


Have fun.

---- Andy
 
Safe to assume you're using Visual Studio?

Thanks a bunch,
Ken
 
Yes, Microsoft Visual Studio 2010 (for now...)

Have fun.

---- Andy
 
While I think VFP 9 is way superior to .net as a development environment I would suggest VB. The two languages are very similar. I can take a lot of my VFP code and just copy it to VB with minor changes.

For instance you have to change concatenation + to &. The way I build SQL quires I do a lot of that.

The biggest difference is that VB and other .net languages work on the snap shot of a table approach instead of keeping the table open and reading and writing to it. While in some ways that is nicer it means that record locking is a lot more of a problem with an SQL tables then with a DBFs.

Allow more time for coding in VB then you would in VFP. While VB is better at opening SQL tables and has a nice Fill command that VFP ADO doesn't a lot of the rest is line fox 2.6 in power rather then VFP. A lot of screen controls that exist in VFP are gone in .Net.

Website programming is lowest common denominator type stuff so use VB EXE's when the web isn't needed. Gives you a lot more power. Keep in mind that there are significant difference between VB for the web and VB for EXE.

As you might guess I think the biggest mistake MS ever made was dropping VFP.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top