Wednesday, July 27, 2005

UIPAB (Part 2)

I had written the second article on UIPAB. You can find the same on http://www.codeproject.com/useritems/UIPAB.asp. This article explains you about how to work on UIPAB. First article that was published on http://www.codeproject.com/dotnet/UIPAB.asp explains about why and when to use UIPAB.

Longhorn Alias Windows Vista

Next version of Windows finally has an official name: Windows Vista.Earlier its name was Longhorn. Microsoft is expected to ship it in later months of 2007

 

Monday, July 25, 2005

Article on UIPAB

Microsoft application block is put up by pattern and practices group of Microsoft. UIPAB is one of those infrastructural areas which are been addressed as higher level issue and needs to be resolved. Though .NET Framework provides sets of core services but still to make our application more scalable, maintainable and also reusable, we need application blocks. I will be trying to summarize the UIPAB in two articles series. This is the first article of the series, which contains an information about the brief description of UIPAB and some of the keywords used in UIPAB. My second article will go in depth of the UIPAB with the demonstration. My first article is published in http://www.codeproject.com/useritems/UIPAB.asp.

 

Monday, July 18, 2005

Encryptions at your hands

Hi,

I had got a lot of feedback about connectionstrings encryption so i had written a article for the same.

http://www.codeproject.com/dotnet/Encryptions.asp

regards

Nishith

Thursday, June 30, 2005

Connection String enhancements in VS 2005

Today I had written an article on ConnectionStringBuilder and the enhancements for the use of connection string.This article is published on following URL

http://www.codeproject.com/useritems/Connection_Strings.asp

 

 

Thursday, May 19, 2005

FAQ on Longhorn

Today as i was browising the sites, i got some FAQ on Longhorn

 

What is Longhorn?
Longhorn is the code name for the next version of Windows. A server version of Longhorn is also planned.

Why the name longhorn?
It's a type of steer. It's also the name of a bar at the base of British Columbia's Whistler mountain, on the way to Blackcomb. Whistler was the code name for Windows XP, while Blackcomb was the moniker for a version of Windows that was originally scheduled to follow Whistler.

When will Longhorn arrive?
Microsoft has promised that Longhorn will be widely available on computers for the 2006 holiday buying season. A beta or test, version is planned for "early summer," probably June or July. The server version is slated for 2007.

So what's in this Longhorn thing?
Longhorn has evolved quite a bit since Microsoft first demonstrated an early version in 2003. The company has dropped plans to include its all-new WinFS file system and has also changed the way it's implementing a new Web services architecture, known as Indigo, and a new graphics engine, dubbed Avalon.

Among the key features of Longhorn as it currently stands are: security enhancements, a new searching mechanism, lots of new laptop features parental controls and better home networking. There will also be visual changes, thanks to Avalon, ranging from shiny translucent windows to icons that are tiny representations of a document itself. On the business side, Microsoft said Longhorn will be easier for businesses to deploy on multiple PCs and will also save costs by reducing the number of times computers will have to be rebooted.

Is that all?
No. Among the other features Microsoft has publicly confirmed are: broad IPv6 support, improved client-side caching of data stored on a server, whole-volume encryption, a revamped synchronization engine, the ability to support laptops with an auxiliary display, automatic hard drive optimization and a secure boot-up process that helps prevent someone from gaining access to your data if your PC is lost or stolen. There's also probably a ton of stuff we haven't heard about yet.

Is everything final?
No. Allchin has said that getting Longhorn out on time is more of a priority than including every last feature. So if the team hits a stumbling block, some features could be on the chopping block.

Will Longhorn be called Longhorn?
No, Microsoft will give it some official name, probably around the time it goes into beta, according to Allchin.

 Will my PC run Longhorn?
That depends on how recently you bought it. Allchin said in an April interview that he expects Longhorn will need about 512MB of memory and "today's level" of processor. The ability to display all the fancy new graphics will depend on what type of graphics card one has. On some older machines, the graphics may look similar to today's Windows.

Will it come in the same editions as in the past--Home, Professional, Tablet and Media Center?
Allchin said Microsoft is close to a decision there, but not ready to talk about it. "We are moving features around," he said.

How much will it cost?
Pricing, too, is yet to be decided

I got to know that Microsoft is expecting seven editions of Longhorn targeting each users.

Tuesday, May 10, 2005

WBMTest.exe - WMI Tester

As i was browsing through the internet, I got to know about a hidden tool that works like a WMI Tester. Name of the utility is wbmtest.exe which can be run by start- run and executing wbmtest.exe. For more info about it, you can visit a link below

http://www.computerperformance.co.uk/Logon/WBMTEST.htm

Thursday, May 05, 2005

Introduction to Visual Studio 2005

                             Introduction to Visual Studio 2005

 

Microsoft Visual Studio 2005 Beta 1 is a major new release of the comprehensive development environment for building Microsoft .NET.connected applications for Microsoft Windows® and the Web. This new version offers the following primary advantages: 

 

·         Radically improved developer productivity. Visual Studio 2005 contains integrated development environments (IDEs) for Microsoft Visual Basic®, Microsoft Visual C#®, and other programming languages, which include many features that make it faster and easier to develop software. These include edit marks, automatic saving of edits, improved rapid application development (RAD) features, and others. Visual Studio 2005 also contains improved graphical tools for specific application scenarios, such as Web page development and data access.

·         Development of Applications in .NET Framework 2.0

·         Development of applications that integrate with Microsoft SQL Server. 2005 Beta 2 or earlier  versions of SQL Server, and development of managed code that runs inside of SQL Server 2005.

 

 

Microsoft .NET Framework 2.0 is the new version of the object-oriented programming environment used to develop applications ranging from traditional command-line or graphical user interface (GUI) applications to Web applications and XML Web services. The .NET Framework 2.0 base class library (BCL) supports backward compatibility with earlier versions and also offers some enhancements to classes to perform common programming tasks such as string management, data collection, database connectivity, and file access. In addition to these common tasks, the BCL includes many enhancements to namespaces that support a variety of specialized development  scenarios, including:

 

1.   ADO.NET 2.0, which consists of classes for efficient data access.

2.   System.Xml 2.0, which consists of classes that enable you to read, write, manipulate, and

transform XML.

3. Windows Forms 2.0, which consists of classes to develop rich-client Windows GUI applications.

 4.  Microsoft ASP.NET 2.0, which consists of classes to build Web applications and XML Web

services.

 

Software developers with experience with earlier versions of Visual Studio .NET will find many productivity enhancements in Visual Studio 2005.

 

Some of the most useful of these enhancements include:

 Edit marks

Visual Studio 2005 provides you with a visual indication of what has changed during the editing session. It distinguishes between the changes you have made that have not yet been saved and changes you have made during the current session that have been saved to disk.

Code snippets and code expansions

Visual Studio 2005 comes with a library of code snippets for common programming tasks. Code snippet is the name used in Visual Basic, but in Visual C# and other languages, it is known as code expansion. You can insert a code snippet into your code to achieve a programming task, instead of searching the documentation or code samples for examples. You can also create your own code

snippets.

Visual C# IDE refactoring tools

The C# IDE includes a suite of tools that automate many common code refactoring tasks.

Developers can easily rename classes, fields, properties, and methods, extract code into its own method, reorder or delete parameters to a method, promote a local variable to be a parameter, encapsulate fields, and perform many other refactoring tasks. The tools ensure that when any change is made, all dependant modules are also updated.

 

Visual Basic productivity enhancements

Visual Studio 2005 delivers a long-requested feature, which is the ability to correct programming errors during debugging and continue to run without restarting the program. There are many other productivity enhancements, including the MyServices abstraction. MyServices are a series of coded shortcuts that make it easier to find system and application resources. For example, code such as My.Computer and My.WebServices are programmatic shortcuts to system resources and Web service references respectively.

 

 

Thursday, February 03, 2005

IIS first look

IIS 7.0 might be released late with Longhorn but it is always good to check some of the features of the articles ..

check more information on this article

http://www.ftponline.com/reports/vslivesf/2005/ruest/

 

 

Monday, January 31, 2005

how baseball player and .NET developer are similar

 
Similarity – Baseball is at a stage where players have now been around for 20 some years, just like some of the heavy hitters (pun intended) in .NET have been around Windows for some time now.

Difference – Baseball players like to play catch.  Developers tend to always be playing catch up, even when a project manager thinks there is plenty of times. 

Similarity – The great baseball players try to get together to form better teams or work out groups.  We have seen many times in .NET that there are banks of great developers that band together to create an environment that is right for them.

Difference – Baseball players hit things for a living.  If a .NET developer hit things for a living, they would probably be sued.

Similarity – Baseball players tend to strike out quite a bit.  So do .NET developers, or any computer person for that matter.

Difference – People pay good money to see baseball players at work.  I will guarantee that no person in their right mind will come to watch me at work. Ever!

Similarity – Once baseball players get to a certain age they let the younger guys fill in for them and they start to step out of the lime light.  Once a .NET developer gets to a certain age, they usually start to move to a manager role (see any similarity yet?), or they start to step out of the lead role and let some younger person take over.

Difference – Baseball players usually only last a couple of years.  Most developers last much longer than that.

Monday, January 24, 2005

Imagine cup Back again

Imagine cup is back again now. Registration closes March 1, 2005. Get started now and register at http://imagine.thespoke.net.

 

 



Friday, January 21, 2005

web messenger from MSN

 
Microsoft now has a web-based version of their popular IM utility.
http://webmessenger.msn.com/

This is 100% Port-80 HTTP traffic, so you will have no problems with the corporate Firewall preventing you from doing IM!!!

 

Persistence Framework : An Introduction

Most enterprise applications need access to a relational database. The Microsoft standard for accessing relational databases is the OleDb or using native Managed .NET Provider that utilize SQL as a data manipulation language. This approach of directly accessing a relational database from an object-oriented .NET application was shown to be inefficient and introduces a problem called "object-relational impedance mismatch," or simply "impedance mismatch" for short. Impedance mismatch refers to the differences between object-oriented technology and relational technology. Object technology relies on objects that have data and behavior. Relational technology supports the storing of data in tables and handling these data via a Data Manipulation Language (DML) such as SQL. Furthermore, objects have identity and are traversed using direct access, whereas RDBS tables have a primary key and are related via values in foreign and primary keys. Finally, RDBMS has no equivalent to object inheritance for data and behavior. An approach for solving the impedance mismatch problem is to introduce an abstract layer, called a persistence layer, between the relational database and the object model of the application. This layer fully encapsulates the database access from your business objects. Thus, instead of writing code to handle your database, you are required only to define meta-data that represents how your relational database will be mapped into objects and deal directly with these objects.