C# v.s. VB on the web ...

I'm VERY curious about your take on .NET.

Do you guys think that C++/VC++ is on the way out with .NET here? Will C# come to be 'THE' MS Windows language, both on the desktop and the web?

Also, why would someone learn C# if VB.NET will do everything they need on the web already (it seems as if it will ... even controls and web services)? Is there any part of ASP.NET that C# really does better than VB.NET?

If you were just starting out and wanted to program for Windows/Web, would you learn VB.NET or C#?

I'm learning C++ for Windows game programming (who isn't :o) and maybe dabbling in Linux so I don't have a preference in MS products.

Thanks,

Minh

>Do you guys think that C++/VC++ is on the way out with .NET here?

As a programming language for native compiled programs that favor speed over development time ( i.e. Games, Batch-Servers ) C/C++ is and will remain the only alternative to something chunky as ASM.

.NET is made for RAD purposes and programs that don't need that tad of speed that would give it the edge.

So it's pretty clear where you take which language/framework.

>Also, why would someone learn C# if VB.NET will do everything they need on the web already

Because both are completely new ( VB.NET is nothing like the old VB, you need to learn it completely new ) and as such you would pick the one that integrates best with the framework and has the better syntax. Which is C#.

>If you were just starting out and wanted to program for Windows/Web

Learn C#.

I think that Microsoft is delegating Xbox as their game environment, and .net focused heavily on business programming needs. The .net framework was necessary because Java was taking over the business market. That is, businesses were using Java to carry out commerce and advertising.

Microsoft is developing games that run on the .net framework, but the framework need to evolve to encompass graphics libraries such as DirectX or OpenGL. I think that a lot of things will be learned from Web Forms. How many of you have created this type of application? The capabilites for distributed computing are a very interesting aspect of .net.

Directx 9 will have full .net support, and you can use Directx 8 with it. Cheak out sunlights site for information how.

www.sunlightd.com

Troll_King is a transvestite.

/* name edited by nv, mod */

Framework, framework, all I freaking hear about nowadays is framework. What exactly did they do with .NET to create this 'framework'. Did they just like bunch a whole bunch of .dlls together or something. Why is it so much faster. I have visual studio ... my friend just got .NET, and so of course I am thinking of getting it but I have no clue why it is so great.

It's good because it is an improvement upon their previous technologies (ASP, COM, Win32, Win DNA, etc). It solves a lot of problems that exist with programming using the system API directly and brings the developer closer to being able to make high order logical decisions and concentrating on program presentation. In a way it sets a Microsoft developer on the right track. It puts them in their place and provides them with tools that are focused on delivering specialized functionality. These are things that you should be focusing on when developing solutions for this platform. In addition it forces the developer to use OOP and as a result will encourage better planned and designed code, and education.

I'm not entirely sure of the potential, but it is positive, especially for small and medium sized business. There are some downsides, but not in terms relating to any trade off of having to leverage a framework. It's good that the Microsoft developer will now be more focused on using tools provided by Microsoft and affiliates rather than deluding themselves into thinking that they can build their own. That kind of work goes on in open source platforms.

Well said. The way you said it makes sense. I guess I will try out .NET for myself. Seeing as how I am only a hobbyist I don't know if I will see a big difference between .NET and Visual Studio 6.0. Worth a try regardlessssssssssssssssssssssssssssssssssssssssss ssssssssssssssssssssssssssssssssssssssssssssssssss ssssssssssssssssssssssssssssssssssssssssssssssssss sssssssssssssssssssss.???

You will notice a difference.

You will not see any difference with native C++. There's a big leap with managed C++, but it might strike you as more complex and not worth it if you don't know the other parts of the framework. If you look into C# you will see how easy to use the framework actually is and how much time it saves.

Since Microsoft wants you, the developer, to use their systems to support the application plumbing, you might find that your solutions are not much different structurally than the next Microsoft developer. On the other hand it appears that there are tools that allow you to focus on your applications domain and make high level logic decisions. This detail was hard to manufacture in the past. The framework is feature rich enough so that it provides you with several contexts to choose to work from. You can work ontop of systems that concentrate on Windows Forms or else systems that provide Web Forms facilities which are a hybrid applicaton. At any rate, you can start building your applications at a higher level, rather than having to piece different systems together, that is being done for you already. This results in more dependance on the Microsoft engineers and it might mean that if there is an error that you can not fix it yourself, however you certainly will be able to construct feature rich applications and one interesting thing is the potiential that is being revealed by using a framework in inventing new systems that lie underneath it all. It might be pushing invention forward.

Note: Even with Win32 API you couldn't fix things by yourself if the problem originated in the implementation.

Quote:

---

Originally posted by Shadow12345
Framework, framework, all I freaking hear about nowadays is framework. What exactly did they do with .NET to create this 'framework'. Did they just like bunch a whole bunch of .dlls together or something. Why is it so much faster. I have visual studio ... my friend just got .NET, and so of course I am thinking of getting it but I have no clue why it is so great.

---

I like to think about the .NET framework as API or the mfc. It is a set of calls you can do to have the OS do things for you.

That last post was me..

Quote:

---

Originally posted by Unregistered


I like to think about the .NET framework as API or the mfc. It is a set of calls you can do to have the OS do things for you.

---

That's way too simplistic of an interpretation, don't you think! It's a hell of a lot more than that.

I ****ing reveal knowledge and it just gets trampled over for Christs sake!