Skip to main content

Difference between VB and C#

Each one language has it's  excellency and assets.
VB:
VB.Net supporting Event Driven Language.
VB.Net has WITH Construct, Which is not in C#.
Vb.Net support for Optional Parameters.
C#:
C Sharp supporting Object Orientation.
C Sharp is fully typed language than VB.Net.
XML Documentation is generated from source code
C Sharp supporting  Operator Overloading.
C Sharp supporting this operator.
C Sharp supporting Pointer via Unsafe Block.

In Dot Net We can share the libraries of languages collaborately in our programming. Dot Net supporting CLR, which helping to use the libraries of all the languages supported by .Net. .Net supporting more than 50 languages. .Net is an Language Independent Development Environment. So that it helping to the developers, coders very effiently. Even the J# developers can use the .Net environment for their development purposes.

Comments

Popular posts from this blog

Microservices vs. APIs

It still surprises me just how many times I come across misconceptions around Micro Services and APIs. Often hearing phrases like micro services are fine grained web services or API is themselves are equivalent to micro services. These all sort of show fundamental misconceptions under the covers. So, I've written this just to really break that out and explain about what the key differences are in those two concepts. What is an API? An API, fundamentally Application Programming Interface, that is an interface. It's a way of making requests into a component. So it's the route that you go in to make those requests. In modern use that typically means a REST API, that's a call made using HTTP protocol using JSON data as the payload. What are Micro Services? So let's ensure we also have a clear crisp definition on what a micro service architecture really is. Micro-Services architecture is about breaking down large silo applications into smalle...

What's Virtual DOM?

There’s no big difference between the regular DOM and the virtual DOM. It’s better to think of the virtual DOM as React’s local and simplified copy of the HTML DOM. It allows React to do its computations within this abstract world and skip the real DOM operations, often slow and browser-specific. Real DOM operations are really really expensive. The Virtual DOM is an abstraction of the HTML DOM. It is lightweight and detached from the browser-specific implementation details.  One thing you should remember that the DOM itself was already an abstraction. So, Virtual DOM is an abstraction of an abstraction. :)