| ActiveMac | Anonymous | Create a User | Reviews | News | Forums | Advertise |
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
ActiveMac |
|
Articles |
|
Forums |
|
Links |
|
News |
|
News Search |
|
Reviews |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
DVD |
|
ActiveHardware |
|
Xbox |
|
MaINTosh |
|
News Search |
|
|
|
|
|
|
|
ANet Chats |
|
The Lobby |
|
Special Events Room |
|
Developer's Lounge |
|
XBox Chat |
|
|
|
|
|
|
|
FAQ's |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows "Whistler" XP |
|
Windows CE |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
TopTechTips |
|
Registry Tips |
|
Windows 95/98 |
|
Windows 2000 |
|
Internet Explorer 4 |
|
Internet Explorer 5 |
|
Windows NT Tips |
|
Program Tips |
|
Easter Eggs |
|
Hardware |
|
DVD |
|
|
|
|
|
|
|
Latest Reviews |
|
Applications |
|
Microsoft Windows XP Professional |
|
Norton SystemWorks 2002 |
|
|
|
Hardware |
|
Intel Personal Audio Player 3000 |
|
Microsoft Wireless IntelliMouse Explorer |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Affiliates |
|
ANet Forums |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
|
Links |
|
Member Pages |
|
Site Search |
|
Awards |
|
|
|
|
|
|
|
Credits |
 |
Moving from Visual Basic to ASP.NET | |
|
||
| Time: 00:00 EST/05:00 GMT | News Source: ActiveWin.com | Posted By: Robert Stein | ||
|
Learn the similarities and differences between Web application development using ASP.NET and classic desktop application development. This article is aimed toward Visual Basic 6.0 developers who are interested in getting started with creating ASP.NET Web applications, and examines the differences between creating desktop applications with Visual Basic 6.0 and creating ASP.NET Web applications with Visual Basic .NET. | ||
|
Write Comment
Return to News |
Displaying 1 through 25 of 156 Last | Next |
The time now is
1:43:41 PM
ET.
Any comment problems? E-mail us |
| #1 By 20 (67.9.179.51) at 9/7/2003 10:15:04 PM |
|
Step 1: Learn C#.
Do yourself a favor and don't use a crutch that is VB.NET. While you can use VB.NET to create elegant, fully OO projects, the temptation to use the crutches for the VB6 programmers is too high. |
| #2 By 20 (67.9.179.51) at 9/8/2003 2:32:58 PM |
|
First off, the underlying language for Office is not VB. Office is written in C++ and what parts are Managed code are most certainly C# (MS uses C# as their standard language for all .NET Projects).
Perhaps you're referring to VBA? That's old technology. Office 2003 supports .NET automation using any .NET language (including C# and VB.NET). So I don't know what the heck you're talking about and I don't think you do either. All managed parts of the .NET Framework are C#. Visual Studio.NET is about half managed, half unmanaged, and the managed parts are all C#. |
| #3 By 20 (67.9.179.51) at 9/8/2003 2:36:25 PM |
|
Also, all I'm saying about the VB.NET thing is, if you're at a crossroads and have the choice between learning VB.NET and C#, choose C#.
As a long time developer, I can tell you that sticking with one language for a long time is very bad for your career and your knowledge. You should be striving to learn lots of new things, you will be a better programmer in the languages you already know because of it. I don't code in C++, but I've been playing around with it and learning it and it has helped me understand some of the concepts and design choices made in .NET better and has helped me code better because of it. |
| #4 By 135 (209.180.28.6) at 9/8/2003 7:47:56 PM |
| I'm more comfortable with C# myself, but I see no compelling reason to engage in an argument of VB.NET versus C# since they are virtually identical. |
| #5 By 20 (67.9.179.51) at 9/8/2003 9:08:33 PM |
|
#9:
You are out of your mind if you think my organization will upgrade from Office 2000 to Office 2003 (which really isn't even out yet) just so I can write macros in C#. I don't recall saying that. You were arguing that Office is written in Visual Basic, which is most certainly not true. I thought you were referring to VBA and I was merely pointing out that a.) VBA is not VB.NET, and b.) If you wish to write .NET macros, you can use C# as well as VB.NET, among many other languages. I do know the difference between VBA and VB.Net. ... So I'll dabble in ASP.NET and VBA.NET. Buzz... wrong. you don't know the different between VBA and VB.NET. There is no such thing as VBA.NET. and VBA is not .NET and Office is not written by Visual Basic. Do you know anything about .NET? |
| #6 By 20 (67.9.179.51) at 9/8/2003 9:10:44 PM |
|
#11: There are many usability and maintainability issues with VB.NET. While VB.NET has most of the features of C#, C# is obviously the chosen and most favored language among MS and has the majority of tools and examples being written for it. Not to mention lots of new features and new development.
While the VB.NET team is focusing on more RAD type features like edit and continue, the C# team is focusing on language features like Generics, Partial Types, anonymous methods, etc. It's clear that VB.NET is for rapid prototyping and maybe simple app design, but for serious programming projects, the advanced language features of C# make it superior. |
|
Write Comment
Return to News |
Displaying 1 through 25 of 156 Last | Next |
The time now is
1:43:41 PM
ET.
Any comment problems? E-mail us |
