Microsoft has introduced a new Certification track for the lovers of .NET 2.0, Visual Studio 2005 and SQL Server 2005. These certifications will be available in 2006.
If you are the one; who can't live without thinking of .NET; then visit the below given link to get all your questions answered.
Microsoft's New Certifications for .NET 2.0, VS 2005 and SQL Server 2005
Tuesday, December 27, 2005
Saturday, September 10, 2005
Envisaging - C# 3.0
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.
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.
Friday, September 02, 2005
SQL Server 2005 release date - November 7 2005
Microsoft's Paul Flessner Senior Vice Peesident Server Applications, talks about Release date of SQL Server 2005 along wuth Visual Studio 2005 and Biz Talk Server 2006.
Sunday, August 14, 2005
Features of SQL Server 2005 (Code name - yukon)
Read my article on Features of SQL Server 2005 at Programmersheaven.Com
Monday, August 01, 2005
Saturday, July 30, 2005
Image of Whidbey (VS .NET 2005) Island
Whidbey is the code name for Visual Studio .NET 2005. Whidbey is an island north of Seattle and it looks like this:
Friday, July 01, 2005
COM Interoperability
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
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.
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
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.
Code Names
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.
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.
Sunday, May 29, 2005
Articles on Programmersheaven.com
Read My articles published on Programmersheaven.com
Features of SQL Server 2005
Features of .NET 2.0
Features of Yukon and Whidbey
Using My namespace with C# 2.0
Features of Visual Studio 2005
Understanding Various Versions of .NET Framework
Working with Partial Types
Features of Longhorn
Exploring SQL Server and the .NET CLR
SQL Server Management Studio - A Management and Development tool
Wednesday, February 09, 2005
Friday, February 04, 2005
My with C# 2.0
Introduction
This article/tutorial talks about My namespace which is
a new feature available with Microsoft .NET Framework 2.0,
and VB .NET 2005 only feature.
About My
With the latest release of Visual Studio .NET 2005
codenamed Whidbey, VB .NET 2005 has been shipped
with one extra class in .NET Framework 2.0 BCL.
The My namespace’s with VB .NET 2005 will help
to write difficult code with a lot of ease.
For example, accessing computer information,
reading computer clock, opening ports, accessing
network, files etc.
Since this most fascinating feature is VB .NET 2005
specific which aimed to help VB .NET developers, and C#
geeks still has to write code for above mentioned tasks,
as like before.
Accessing My with C#
Besides having the total control and writing the code on
your own as being the real C# developer, My namespace can
be accessed and used in C# programs.
The idea of accessing My lies in the core .NET Framework 2.0 BCL
Base Class Library), and My namespace has its implementation in
an assembly named Micrisoft.VisualBasic.dll and uses Microsoft.VisualBasic.MyServices namespace.
By having reference to this assembly, the functionality of My
namespace can be used with C# also.
Code Example
The example shows how to call My in C#
Step - 1 Run Visual Studio .NET 2005 (Whidbey)
File --> New --> Project -->Visual C# --> Console Application
Step - 2 Add Reference to Microsoft.VisualBasic.dll under References
Step - 3 Add the following line under using directive
using Microsoft.Visualbasic.MyServices;
and then add the code to call the functionality
Click to view the code
Step - 4 Run the application and see the output.
Conclusion
This article/tutorial briefly introduced the My namespace and how to access My with C#.
Another point is that why My is VB .NET 2005 only feature, the reason I can think is Visual Basic is the language which has been greatly recognized for its IDE and Intellisense features and this is all what satisfies the term RAD and this is why it is available with VB .NET 2005 (by default) and not with C#. VB .NET Code Editor Window recognizes My and it is a Language Enhancement with VB .NET 2005.
Since, My namespace is the part of .NET Framework 2.0 BCL (Base Class Library), implemented in Microsoft.VisualBasic.dll assembly, under the namespace Microsoft.VisualBasic.MyServices namespace, any C# developers can also take advantage of that by having a reference to the Microsoft.VisualBasic.dll and invoking the functionality from Microsoft.VisualBasic.MyServices namespace.
This article/tutorial talks about My namespace which is
a new feature available with Microsoft .NET Framework 2.0,
and VB .NET 2005 only feature.
About My
With the latest release of Visual Studio .NET 2005
codenamed Whidbey, VB .NET 2005 has been shipped
with one extra class in .NET Framework 2.0 BCL.
The My namespace’s with VB .NET 2005 will help
to write difficult code with a lot of ease.
For example, accessing computer information,
reading computer clock, opening ports, accessing
network, files etc.
Since this most fascinating feature is VB .NET 2005
specific which aimed to help VB .NET developers, and C#
geeks still has to write code for above mentioned tasks,
as like before.
Accessing My with C#
Besides having the total control and writing the code on
your own as being the real C# developer, My namespace can
be accessed and used in C# programs.
The idea of accessing My lies in the core .NET Framework 2.0 BCL
Base Class Library), and My namespace has its implementation in
an assembly named Micrisoft.VisualBasic.dll and uses Microsoft.VisualBasic.MyServices namespace.
By having reference to this assembly, the functionality of My
namespace can be used with C# also.
Code Example
The example shows how to call My in C#
Step - 1 Run Visual Studio .NET 2005 (Whidbey)
File --> New --> Project -->Visual C# --> Console Application
Step - 2 Add Reference to Microsoft.VisualBasic.dll under References
Step - 3 Add the following line under using directive
using Microsoft.Visualbasic.MyServices;
and then add the code to call the functionality
Click to view the code
Step - 4 Run the application and see the output.
Conclusion
This article/tutorial briefly introduced the My namespace and how to access My with C#.
Another point is that why My is VB .NET 2005 only feature, the reason I can think is Visual Basic is the language which has been greatly recognized for its IDE and Intellisense features and this is all what satisfies the term RAD and this is why it is available with VB .NET 2005 (by default) and not with C#. VB .NET Code Editor Window recognizes My and it is a Language Enhancement with VB .NET 2005.
Since, My namespace is the part of .NET Framework 2.0 BCL (Base Class Library), implemented in Microsoft.VisualBasic.dll assembly, under the namespace Microsoft.VisualBasic.MyServices namespace, any C# developers can also take advantage of that by having a reference to the Microsoft.VisualBasic.dll and invoking the functionality from Microsoft.VisualBasic.MyServices namespace.
Monday, January 31, 2005
Certification Process: MCAD .NET/MCSD .NET
To achieve MCSD .NET and MCAD.NET the participant has to understand the requirements which are mentioned below.
MCAD: Microsoft Certified Application Developer
MCSD: Microsoft Certified Solution Developer
MCAD for Microsoft .NET
Visual Basic .NET Language Path (Two required)
Exam 70-305: Developing and Implementing Web Applications with Microsoft Visual Basic .NET and Microsoft Visual Studio .NET
Or
Exam 70-306: Developing and Implementing Windows-based Applications with Microsoft Visual Basic .NET and Microsoft Visual Studio .NET
Exam 70-310: Developing XML Web Services and Server Components with Microsoft Visual Basic .NET and the Microsoft .NET Framework
Visual C# Language Path (Two required)
Exam 70-315: Developing and Implementing Web Applications with C# and Microsoft Visual Studio .NET
Or
Exam 70-316: Developing and Implementing Windows-based Applications with C# and Microsoft Visual Studio .NET
Exam 70-320: Developing XML Web Services and Server Components with Microsoft Visual C# and the Microsoft .NET Framework
Elective Exams (One Required)
Exam 70-229: Designing and Implementing Databases with Microsoft SQL Server 2000, Enterprise Edition
Note: This exam is widely by maximum of the developers.
Exam 70-230: Designing and Implementing Solutions with Microsoft BizTalk Server 2000, Enterprise Edition
Exam 70-234: Designing and Implementing Solutions with Microsoft Commerce Server 2000
MCSD for Microsoft .NET
Track: Visual Basic .NET (Four required)
Exam 70-305: Developing and Implementing Web Applications with Microsoft Visual Basic .NET and Microsoft Visual Studio .NET
Exam 70-306: Developing and Implementing Windows-based Applications with Microsoft Visual Basic .NET and Microsoft Visual Studio .NET
Exam 70-310: Developing XML Web Services and Server Components with Microsoft Visual Basic .NET and the Microsoft .NET Framework
Exam 70-300: Analyzing Requirements and Defining .NET Solution Architectures.
Note: This exam is required for all MCSDs, regardless of language choice.or
Track: Visual C# (Four required)
Exam 70-315: Developing and Implementing Web Applications with C# and Microsoft Visual Studio .NET
Exam 70-316: Developing and Implementing Windows-based Applications with C# and Microsoft Visual Studio .NET
Exam 70-320: Developing XML Web Services and Server Components with Microsoft Visual C# and the Microsoft .NET Framework
Exam 70-300: Analyzing Requirements and Defining .NET Solution Architectures. Note: This exam is required for all MCSDs, regardless of language choice.
Elective Exams (One Required)
Exam 70-229: Designing and Implementing Databases with Microsoft SQL Server 2000, Enterprise Edition
Exam 70-230: Designing and Implementing Solutions with Microsoft BizTalk Server 2000, Enterprise Edition
Exam 70-234: Designing and Implementing Solutions with Microsoft Commerce Server 2000
Other Info about Exam
Total Time: 175 Minutes (150 Minutes for the actual exam and 25 Minutes for survey and comments)
Fees: 2500 INR/Paper
Number of Actual Exam Questions may vary. (Around 58 questions)
Good way:
1. Read each question carefully.
2. Eliminate the wrong answers.
3. Select the correct ones (or at least the nearest guess)
4. Mark the questions which you don't know the answers (With this, you can estimate the possibility of passing the test before hand) to review them later
Useful Links:
www.microsoft.com/traincert
http://www.microsoft.com/learning/mcp/default.asp
Reference Books:
1.Microsoft Press/PHI MOC Books on Web/Windows etc
2.ADO.NET Step by Step by Rebecca
3.Advanced .NET Remoting - Ingo Rammer
4.Windows-Based Applications with Ms-C#.net and Ms-VB.NET.
5.Web-Based Applications with Ms-C#.net and Ms-VB.NET.
6.Professional C# Wrox.
7.Xml WebServices by Scott
8..Net Remoting -By Jason Bock, Pete Stromquist, Tom Fischer, Nathan Smith
9.Com + (o’riely )
MCAD: Microsoft Certified Application Developer
MCSD: Microsoft Certified Solution Developer
MCAD for Microsoft .NET
Visual Basic .NET Language Path (Two required)
Exam 70-305: Developing and Implementing Web Applications with Microsoft Visual Basic .NET and Microsoft Visual Studio .NET
Or
Exam 70-306: Developing and Implementing Windows-based Applications with Microsoft Visual Basic .NET and Microsoft Visual Studio .NET
Exam 70-310: Developing XML Web Services and Server Components with Microsoft Visual Basic .NET and the Microsoft .NET Framework
Visual C# Language Path (Two required)
Exam 70-315: Developing and Implementing Web Applications with C# and Microsoft Visual Studio .NET
Or
Exam 70-316: Developing and Implementing Windows-based Applications with C# and Microsoft Visual Studio .NET
Exam 70-320: Developing XML Web Services and Server Components with Microsoft Visual C# and the Microsoft .NET Framework
Elective Exams (One Required)
Exam 70-229: Designing and Implementing Databases with Microsoft SQL Server 2000, Enterprise Edition
Note: This exam is widely by maximum of the developers.
Exam 70-230: Designing and Implementing Solutions with Microsoft BizTalk Server 2000, Enterprise Edition
Exam 70-234: Designing and Implementing Solutions with Microsoft Commerce Server 2000
MCSD for Microsoft .NET
Track: Visual Basic .NET (Four required)
Exam 70-305: Developing and Implementing Web Applications with Microsoft Visual Basic .NET and Microsoft Visual Studio .NET
Exam 70-306: Developing and Implementing Windows-based Applications with Microsoft Visual Basic .NET and Microsoft Visual Studio .NET
Exam 70-310: Developing XML Web Services and Server Components with Microsoft Visual Basic .NET and the Microsoft .NET Framework
Exam 70-300: Analyzing Requirements and Defining .NET Solution Architectures.
Note: This exam is required for all MCSDs, regardless of language choice.or
Track: Visual C# (Four required)
Exam 70-315: Developing and Implementing Web Applications with C# and Microsoft Visual Studio .NET
Exam 70-316: Developing and Implementing Windows-based Applications with C# and Microsoft Visual Studio .NET
Exam 70-320: Developing XML Web Services and Server Components with Microsoft Visual C# and the Microsoft .NET Framework
Exam 70-300: Analyzing Requirements and Defining .NET Solution Architectures. Note: This exam is required for all MCSDs, regardless of language choice.
Elective Exams (One Required)
Exam 70-229: Designing and Implementing Databases with Microsoft SQL Server 2000, Enterprise Edition
Exam 70-230: Designing and Implementing Solutions with Microsoft BizTalk Server 2000, Enterprise Edition
Exam 70-234: Designing and Implementing Solutions with Microsoft Commerce Server 2000
Other Info about Exam
Total Time: 175 Minutes (150 Minutes for the actual exam and 25 Minutes for survey and comments)
Fees: 2500 INR/Paper
Number of Actual Exam Questions may vary. (Around 58 questions)
Good way:
1. Read each question carefully.
2. Eliminate the wrong answers.
3. Select the correct ones (or at least the nearest guess)
4. Mark the questions which you don't know the answers (With this, you can estimate the possibility of passing the test before hand) to review them later
Useful Links:
www.microsoft.com/traincert
http://www.microsoft.com/learning/mcp/default.asp
Reference Books:
1.Microsoft Press/PHI MOC Books on Web/Windows etc
2.ADO.NET Step by Step by Rebecca
3.Advanced .NET Remoting - Ingo Rammer
4.Windows-Based Applications with Ms-C#.net and Ms-VB.NET.
5.Web-Based Applications with Ms-C#.net and Ms-VB.NET.
6.Professional C# Wrox.
7.Xml WebServices by Scott
8..Net Remoting -By Jason Bock, Pete Stromquist, Tom Fischer, Nathan Smith
9.Com + (o’riely )
Wednesday, January 26, 2005
Father of C#
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.
Subscribe to:
Posts (Atom)
