Books Authored for Apress Inc

April 30th, 2008 | Posted by Vidya Vrat in .NET | C# | Community - (0 Comments)
  1. Beginning C# 5.0 Databases
  2. Beginning C# 2008 Databases
  3. Beginning VB 2008 Databases
  4. Pro ASP.NET 3.5 in VB 2008: Includes Silverlight 2
  5. Pro VB 2010 and the .NET 4.0 Platform

Recently I got an opportunity to review the .NET Preparation Kits produced by uCertify – The fastest way to IT Certification

I was tasked to review the MCTS 70-536 C# exam preparation kit titled: Microsoft .NET Framework 2.0 Application Development Foundation. While reviewing the preparation kit for 70-536 I found the methodology used to teach the concepts are very good and the concepts are covered in such a way that a beginner or a professional will be equally benefited.
Various types of practice tests helps you to be tough and well prepared when you appear for the real test. Each test covers all the concepts as per the Microsoft requirements and helps to prepare gradually and also to see your progress. I believe that this exam is one of the most usable exams as it opens the entry for three other MCTS exams as well. I personally feel, that Investing in 70-536 preparation kit available at 70-536-CSHARP – C#.NET 2.0 Application Development Foundation practice test will be an asset for any MCTS aspitant.

If you want to purchase .NET Preparation kits from uCertify then you can avail 10% discount as being my blog reader. Provide the discount code “VVRAGA” during your online purchase order when asked and enjoy the .NET Preparation kits to help you achieve your desired Microsoft certification.

Lets also have look at the user friendly and easy to use dashboard of uCertify’s preparation kits.

Envisaging – C# 3.0

September 10th, 2005 | Posted by Vidya Vrat in C# - (0 Comments)

It was year 2000 when .NET 1.0 was released and till now, .NET has been on a long journey of advancements, and so C# 2.0 was released with Whidbey which will be getting public on November 7, 2005.

But future has unpredictable features to be available with another new version of C# and so named as C# 3.0(C# Orcas).Orcas is code name of VS .NET for future release of 64-bit OS Longhorn.

C# 3.0 (C# Orcas) has very interesting features which will make it much easier to write applications. Somehow I too believe that this much ease is not good.

It has been a practice for many years with almost all languages, that variable declaration requires a data type; for example: int i=10; or string s=”C Sharp”;

C# 3.0(C# Orcas) will be having an interesting behavior of Declaring Local Variables Implicitly and there is no need to mention data type while declaring a variable. I.e. a local variable can be specified using var as type without requiring any specific data type for that variable For example: var i=10; in C# 3.0 is as same as int i=10; and var s=”C Sharp”; is as same as string s=”C Sharp”; which was the procedure of declaring variables in earlier versions of C# and C# 2.0.

On the contrary declaring local variables implicitly has some restrictions: that the variable must be initialized and must be an expression and can not be null.

Another new feature is Query Expressions which provide a new language integrated syntax for queries like offered by SQL(relational) and XQuery (hierarchical)query languages.

Besides these features C#3.0(C# Orcas) has other great features too, which are extensions to the functionalities offered by C# 2.0.

Code Names

July 1st, 2005 | Posted by Vidya Vrat in .NET | C# | Visual Studio - (0 Comments)

Thunder – This was the code name for one of the Most facinating RAD tool Visual Basic(VB).
Lightning – This was the code name for .NET CLR(the most adorable one).
Everett – This was the code name for Microsoft Visual Studio .NET 2003. Everett is a city north of Seattle.
Whidbey – This is the code name for Microsoft Visual Studio .NET 2005. Whidbey is an island north of Seattle (you go through Everett to get the ferry to Whidbey Island).
Yukon – This is the code name of the next version of Microsoft SQL Server, with SQL Server 2005 “Yukon” developers will be able to leverage their existing skills in writing .NET-connected software using the Common Language Runtime (CLR) built into the database engine.Yukon is a place in Northern Canada!
Longhorn – This is the code name for the Next version of Microsoft’s 64-bit Windows operating system. Longhorn is a bar close to Whistler and Blackcomb ski resorts.
Orcas – Visual Studio .NET 200X code named “Orcas” will support the managed interfaces, enhanced user interface features and other new capabilities the Longhorn operating system will offer. Orcas is an island in the San Juan group of islands even further north of Seattle.

COM Interoperability

July 1st, 2005 | Posted by Vidya Vrat in .NET | C# - (0 Comments)

Using .NET Assembly from COM Client
This article explains about the .NET Interoperability with COM.

Step 1: Creating a .NET Assembly Project

1.1 Visual Studio .NET IDE -> File -> New Project ->
Visual Basic Projects -> Class Library

1.2 Name the Application, for instance NetServer, this will
be our .NET Assembly Project,which will be consisting of at
least one class called Class1.vb.

1.3 Rename the class to NetClass from properties window and manually
in code window.This class will hold all the functionality of .NET Component,
in the form of few functions.

Step 2: Adding Functionality

On the path of achieving COM Interoperability, Microsoft .NET
offers an attribute named ,which is
located inside the Micrsoft.VisualBasic namespace
and it makes the .NET Class available for use by a COM Client.

It’s also a wise choice to add System.Runtime.InteropService namespace to the class, which offers various features to be used.

The figure below shows the whole Code of .NET Assembly.

Step 3: Set Property for COM Interoperability

Select NETServer project from Solution Explorer, Right Click ->
Properties -> Configuration Properties -> Build -> Check on
Register for COM Interop after setting the property, do Build The Solution. It will create
a NetServer.dll (assembly) in your applications \bin folder.

Step 4: Deploying for COM access

A .NET assembly which has been created can’t be used by a COM Client,
because COM Client can access an object with help of a Type Library,
which tells to the Client about the Object.

In .NET world there is no such concept of Type LIbrary, but because of
COM Interop feature, .NET Framework SDK offers a tool called
RegAsm.Exe which offers to make a type library and
register it in Windows Registry, the very own style of COM.

4.1 Access Command Prompt (cmd)

4.2 Change the path to your application folder
for example : C:\>D: press enter
D:\> cd Net Applications\NetServer\Bin
D:\Net Applications\NetServer\Bin>

4.3 Type the following command to create a
Type Library,which is a COM world’s buzz word and equivalent
to Metadata of a .NET Assembly.

D:\Net Applications\NetServer\Bin> RegAsm /tlb: NetServer.tlb NetServer.dll

This command will create a Type Library named NetServer.tlb
in the \bin folder of .NET Assembly application. Which was
automatically registered in Windows Registry as well.

Now the .NET Assembly is ready to use by a COM Client.

Step 5: VB 6.0 Client to access .NET Assembly

5.1 Open Visual Studio 6.0 -> Visual Basic 6.0 ->
File -> New -> Standard.Exe

5.2 Drag one Label and two Command Buttons onto the form.

Step 6: Set Reference to the Type Library

Before consuming the class you build using .NET

Project -> References -> Find the NetServer and select that.

Step 7: Code to access the .NET Class

after adding the code, run your VB 6.0 and click on the command buttons, you will see that your application communicating with .NET Assembly.

 

Father of C#

January 26th, 2005 | Posted by Vidya Vrat in C# - (0 Comments)


Name: Anders Hejlsberg

Designation: Microsoft Distinguished Engineer and chief architect of C#.

History:
* He is one of the most successful developers in the IT cosmos in recent times.
* He stands among one of the Borland Corporation’s first employees.
* He was the original author of Turbo Pascal.
* He worked as the chief architect of the Delphi product line.

At Microsoft:
In 1996 he joined Microsoft, and played a pivotal role in the development
and design of Visual J++ and the Windows Foundation Classes.
Then he worked on COM+, followed by the VS.NET Framework team.

Over the past 5 years, as one of only 20 Distinguished Engineers at Microsoft, he has distinguished himself still further, as the brains behind the creation of C# the first component-oriented programming language in the C and C++ family to combine the power of those languages with the functional ease of modern, rapid application development tools. Anders, who is Danish, originally studied engineering at the Technical University of Denmark.