developersreference

noreply@blogger.com (balasundaram g) — Mon, 02 May 2011 22:09:07 PDT

This post confirms my ownership of the site and that this site adheres to Google AdSense program policies and Terms and Conditions: ca-pub-1189144978473927

Professional Application Lifecycle Management with Visual Studio 2010

noreply@blogger.com (balasundaram g) — Mon, 25 Oct 2010 21:55:00 PDT

Book Description

Get up to speed on Application Lifecycle Management (ALM) with Visual Studio 2010 through a combination of hands-on instruction and deep-dives.

Microsoft has packed a lot of brand new testing and modeling tools into Visual Studio 2010, tools that previously were available only to Microsoft internal development teams. Developers will appreciate the focus on practical implementation techniques and best practices.

A team of Microsoft insiders provides a nuts-and-bolts approach. This Wrox guide is designed as both a step-by-step guide and a reference for modeling, designing, and coordinating software development solutions at every level using Visual Studio 2010 and Visual Studio Team Foundation Server 2010.

Visual Studio 2010 offers a complete lifecycle management system that covers modeling, testing, code analysis, collaboration, build and deployment tools.

Book Details
Paperback: 696 pages
Publisher: Wrox (April, 2010)
Language: English
ISBN-10: 0470484268
ISBN-13: 978-0470484265
File Size: 247.3 MiB

Download files from Hotfile :
http://hotfile.com/dl/70640933/61c2428/Wrox.Professional.Application.Lifecycle.Management.with.Visual.Studio.2010.Apr.2010.part1.rar.html
http://hotfile.com/dl/70641060/d0676a1/Wrox.Professional.Application.Lifecycle.Management.with.Visual.Studio.2010.Apr.2010.part2.rar.html
Download files from Fileserve :
http://www.fileserve.com/file/nvCq5mq
http://www.fileserve.com/file/MnXTFfz

Professional WCF 4: Windows Communication Foundation with .NET 4

noreply@blogger.com (balasundaram g) — Thu, 23 Sep 2010 11:31:58 PDT

Book Description
A guide to architecting, designing, and building distributed applications with Windows Communication Foundation

Windows Communication Foundation is the .NET technology that is used to build service-oriented applications, exchange messages in various communication scenarios, and run workflows. This guide enables developers to create state-of-the-art applications using this technology.

Written by a team of Microsoft MVPs and WCF experts, this book explains how the pieces of WCF 4.0 build on each other to provide a comprehensive framework to support distributed enterprise applications. Experienced developers will learn both theory and practical application using the familiar Wrox approach.

.NET developers will learn to design services, create a hosting environment with Dublin, build cloud-based integrations, and much more.

Coverage Includes:
Design Principles and Patterns
Service Contracts and Data Contracts
Bindings
Clients
Instancing
Workflow Services
Understanding WCF Security
WCF Security in Action
Federated Authentication in WCF
Windows Azure Platform AppFabric
Creating a SOA Case
Creating the Communication and Integration Case
Creating the Business Process
Hosting
From the Back Cover
Design and build state-of-the-art applications using WCF 4

Written by a team of Microsoft MVPs, this book arms you with a clear understanding of how the components of WCF 4 build on each other to provide a comprehensive framework for distributed enterprise applications. The authors explain the technical features of the WCF 4 stack and present three case studies that show you how these features are applied step by step. You’ll also find out how to effectively use Visual Studio 2010 and Microsoft Azure Platform AppFabric to develop solutions that maximize WCF 4 capabilities.

Professional WCF 4:

Walks you through the design of services and use of communication patterns in a correct and solid architecture
Explores the benefits of the WCF 4 bindings and messaging enhancements
Uncovers different ways to secure access to service operations
Describes working with workflow services to organize business processes and create long-running orchestrations
Explains how to build cloud-based integrations with .NET Services as part of the Azure Services Platform
About the Author
About the Authors, Microsoft Connected System Developer MVPsPablo Cibraro is an enterprise architect and Regional CTO at Tellago as well as an MVP Connected System Developer.

Kurt Claeys is an architect and coach in developing .NET enterprise applications with a focus on integration implemented using WCF. He’s an MCT, MCSD and MVP Connected System Developer.

Fabio Cozzolino is a Software Architect, Analyst, and Developer at FimeSan, a CompuGroup Company, and is an MVP in the Connected System Developer category.

Johann Grabner is a freelance trainer for Microsoft Learning Partners and an MVP Connected System Developer.

Book Details

Paperback: 480 pages
Publisher: Wrox (June, 2010)
Language: English
ISBN-10: 0470563141
ISBN-13: 978-0470563144
File Size: 102.6 MiB
Download files from Hotfile :

http://hotfile.com/dl/70644936/4e387e5/Wrox.Professional.WCF.4.Windows.Communication.Foundation.with.NET.4.rar.html

Download files from Fileserve :

http://www.fileserve.com/file/2ZWA7UP

ASP.NET 2.0 Cookbook by O'Reilly Media

noreply@blogger.com (balasundaram g) — Tue, 23 Jun 2009 09:18:02 PDT

Requested by King - Orkut (Symbian OS)

noreply@blogger.com (balasundaram g) — Tue, 23 Jun 2009 07:56:41 PDT

SQL Server : Information Schema

noreply@blogger.com (balasundaram g) — Tue, 23 Jun 2009 02:56:07 PDT

In my previous post, explained how to get the relation ships between the tables. Here is some important hints about the SQL server.
In SQL server Information_Schema is very use full to get the details of the tables. The below list of Information_Schema's are used to retrieve the tables and fields details.
Information_Schema.Check_Constraints Information_Schema.Column_Domain_Usage Information_Schema.Column_Privileges Information_Schema.ColumnsInformation_Schema.Constraint_Column_Usage Information_Schema.Constraint_Table_Usage Information_Schema.Domain_Constraints Information_Schema.DomainsInformation_Schema.Key_Column_Usage Information_Schema.ParametersInformation_Schema.Referential_ConstraintsInformation_Schema.Routine_ColumnsInformation_Schema.RoutinesInformation_Schema.SchemataInformation_Schema.Table_ConstraintsInformation_Schema.Table_PrivilegesInformation_Schema.Tables Information_Schema.Views Information_Schema.View_Column_Usage Information_Schema.View_Table_Usage

For Example : if you want to see how many tables you are using in the database:
select * from Information_Schema.Tables where Table_Type = 'BASE TABLE'
if you want to see how many views you are using in the database:
select * from Information_Schema.Tables where Table_Type = 'VIEW'

Like this you can use Information_Schema to get the details of the database.

Retrive relationship between the tables

noreply@blogger.com (balasundaram g) — Mon, 22 Jun 2009 01:30:26 PDT

This query is used to retrieve the relationship for the tables in a dabase. This query is work only in sql server.

SELECT table1 = FK.TABLE_NAME, coloum1 = CU.COLUMN_NAME,table2 = PK.TABLE_NAME,
coloum2 = PT.COLUMN_NAME FROM INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS C
INNER JOIN INFORMATION_SCHEMA.TABLE_CONSTRAINTS FK
ON C.CONSTRAINT_NAME = FK.CONSTRAINT_NAME INNER JOIN INFORMATION_SCHEMA.TABLE_CONSTRAINTS PK
ON C.UNIQUE_CONSTRAINT_NAME = PK.CONSTRAINT_NAME INNER JOIN INFORMATION_SCHEMA.KEY_COLUMN_USAGE CU
ON C.CONSTRAINT_NAME = CU.CONSTRAINT_NAME INNER JOIN (SELECT i1.TABLE_NAME, i2.COLUMN_NAME
FROM INFORMATION_SCHEMA.TABLE_CONSTRAINTS i1 INNER JOIN INFORMATION_SCHEMA.KEY_COLUMN_USAGE i2
ON i1.CONSTRAINT_NAME = i2.CONSTRAINT_NAME WHERE i1.CONSTRAINT_TYPE = 'PRIMARY KEY') PT
ON PT.TABLE_NAME = PK.TABLE_NAME

How to find relation ship between two tables

noreply@blogger.com (balasundaram g) — Mon, 22 Jun 2009 01:29:00 PDT

Here is a query (SQL server) to find the relation ship between two tables. This will be very useful for the people who develop generic DAL

SELECT table1 = FK.TABLE_NAME, coloum1 = CU.COLUMN_NAME,table2 = PK.TABLE_NAME,
coloum2 = PT.COLUMN_NAME FROM INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS C
INNER JOIN INFORMATION_SCHEMA.TABLE_CONSTRAINTS FK
ON C.CONSTRAINT_NAME = FK.CONSTRAINT_NAME INNER JOIN INFORMATION_SCHEMA.TABLE_CONSTRAINTS PK
ON C.UNIQUE_CONSTRAINT_NAME = PK.CONSTRAINT_NAME INNER JOIN INFORMATION_SCHEMA.KEY_COLUMN_USAGE CU
ON C.CONSTRAINT_NAME = CU.CONSTRAINT_NAME INNER JOIN (SELECT i1.TABLE_NAME, i2.COLUMN_NAME
FROM INFORMATION_SCHEMA.TABLE_CONSTRAINTS i1 INNER JOIN INFORMATION_SCHEMA.KEY_COLUMN_USAGE i2
ON i1.CONSTRAINT_NAME = i2.CONSTRAINT_NAME WHERE i1.CONSTRAINT_TYPE = 'PRIMARY KEY') PT
ON PT.TABLE_NAME = PK.TABLE_NAME and PK.TABLE_NAME IN (@TableName)
and FK.TABLE_NAME IN (@TableName2)

Theory of Computation TEXTS IN COMPUTER SCIENCE

noreply@blogger.com (balasundaram g) — Fri, 19 Jun 2009 04:15:20 PDT

Most of the course is concerned with computational complexity, or the classification of computational problems in terms of their inherent complexity. This usually refers to time or space usage on a particular computational model, but may include other complexity measures as well, such as randomness, number of alternations, or circuit size or depth. We include a rigorous treatment of computational models, including deterministic, nondeterministic, and alternating Turing machines, circuits, probabilistic machines, interactive proof systems, automata on infinite objects, and various logical formalisms. Also included are various approximation and inapproximation results and some lower bounds.you can download Theory of Computation TEXTS IN COMPUTER SCIENCE Book for free from the download link.

Download:http://www.easy-share.com/1905743556/Theory%20of%20Computation.rar

C# Beginning Programming Tutorial

noreply@blogger.com (balasundaram g) — Sat, 13 Jun 2009 04:49:43 PDT

C# Programming tutorial::(1)Fundamentals

noreply@blogger.com (balasundaram g) — Sat, 13 Jun 2009 04:47:05 PDT

Java Video Tutorial : If Statements

noreply@blogger.com (balasundaram g) — Fri, 12 Jun 2009 01:51:48 PDT

Java Video Tutorial : Hello World!

noreply@blogger.com (balasundaram g) — Fri, 12 Jun 2009 01:48:35 PDT

Java Video Tutorial : Exceptions

noreply@blogger.com (balasundaram g) — Fri, 12 Jun 2009 01:44:44 PDT

Java Video Tutorial : Object Oriented Programming

noreply@blogger.com (balasundaram g) — Fri, 12 Jun 2009 01:41:41 PDT

Explaining the ADO.NET Entity Framework

noreply@blogger.com (balasundaram g) — Thu, 11 Jun 2009 03:37:23 PDT

Explaining the ADO.NET Entity Framework @ Yahoo! Video

This is the trailer for a 30-minute presentation by Mike Pizzo of Microsoft at the DataServices World conference. Mike is the Principal Architect, Data Programmability at Microsoft. He explains the ADO.NET Entity Framework and the Entity Framework data model. The complete presentation video is viewable by browsing to SQLSummit.com.

ASP.Net tutorial part 1

noreply@blogger.com (balasundaram g) — Thu, 11 Jun 2009 03:09:40 PDT

C# Programming tutorial (2of2)

noreply@blogger.com (balasundaram g) — Wed, 10 Jun 2009 22:53:19 PDT

C# Programming tutorial (1of2)

noreply@blogger.com (balasundaram g) — Wed, 10 Jun 2009 22:51:16 PDT

What is "maintainable code"? - Tony Davis

noreply@blogger.com (balasundaram g) — Mon, 08 Jun 2009 05:22:32 PDT

"Maintainable code" does not mean the same thing to a DBA as it does to a developer. Production Support staff will want something altogether different from either. These differing perspectives on maintainability have always been a cause of immense grief to IT projects.
To a developer, maintainable code simply means "code that is easy to modify or extend". At the heart of maintainability is carefully constructed code that is easy to read; code that is easy to dissect in order to locate the particular component relating to a given change request; code that is then easy to modify without the risk of starting a chain reaction of breakages in dependant modules.
Aside from "common sense" principles such as keeping code as simple and terse as possible, creating effective documentation, using source control, and so on, developers aim to ensure a clean separation of functionality in their code, with high cohesion and low coupling. They will generally employ a range of tools and techniques, such as MVC patterns, object-relational mapping tools, and test-driven development, which offer the promise of more maintainable code.
Unfortunately, such tools mean little to the DBA. They will find little solace in the idea that the code is elegant and object-oriented; it matters little to them if there are few inter-class dependencies. They are not enamoured by object-relational mapping. Maintainable code to a DBA means code that is written to a defined interface, based on routines, so that access rights can be restricted for security, and the SQL can be optimised independently of the application code. It is code that is instrumented and easy to troubleshoot, where any anomalous conditions within the application are logged, even if they don't cause errors.
Support staff will be largely unimpressed by either definition of maintainability. For them, a maintainable application provides an easily-accessible list of all possible 'exceptions', along with a description of what to do to fix the problem. They want an application that alerts them when there is anything that needs to be corrected, and gives them a step-by-step procedure to do so, or indicates who they should contact. They just want something they can keep upright, no matter what elegant innards lie behind and beyond the 'application unavailable: please contact your administrator' message.
What is the way out of this conundrum? Is it possible to reach a "consensus" definition of maintainability, or do we simply need to main distinct definitions and make it clearer which "type" of maintainability we're referring to?
As always, we'd all love to hear what you think. The best contribution to the debate, added as a comment to the editorial blog, will receive a $50 Amazon voucher.
Cheers,
Tony.
Original post can be found here

Making a jQuery Plugin Truly Customizable

noreply@blogger.com (balasundaram g) — Mon, 08 Jun 2009 05:21:13 PDT

Most if not all of the jQuery plugins out there have some level of customization. But very few of the plugin authors have mastered the very particular art involved.
Achieving the "optimum level" of customization is a bit of a balancing act… go too far either way and you've got an unusable plugin! read more...

You should NOT use ASP.NET MVC if. . .

noreply@blogger.com (balasundaram g) — Mon, 08 Jun 2009 05:19:37 PDT

You are not very comfortable with polymorphism
You aren’t willing to build on top of the framework
You rely on 3rd party vendor controls for lots of the UI
You are adverse to using open-source libraries

The above are four quick reasons why WebForms may be a better for for some time to come if you are an ASP.NET developer wondering whether you should upgrade to ASP.NET MVC. Please understand that I have switched all of my employees to this latest version of ASP.NET for all client projects. I’m also writing a book, ASP.NET MVC in Action for Manning with two great co-authors, Ben Scheirman and Jimmy Bogard, both of which write about the framework on their respective blogs. more...

What about GIT?

noreply@blogger.com (balasundaram g) — Mon, 08 Jun 2009 05:16:32 PDT

Git is distributed version control system focused on speed, effectivity and real-world usability on large projects. Its highlights include:
Distributed development. Like most other modern version control systems, Git gives each developer a local copy of the entire development history, and changes are copied from one such repository to another. These changes are imported as additional development branches, and can be merged in the same way as a locally developed branch. Repositories can be easily accessed via the efficient Git protocol (optionally wrapped in ssh for authentication and security) or simply using HTTP - you can publish your repository anywhere without any special webserver configuration required.
Strong support for non-linear development. Git supports rapid and convenient branching and merging, and includes powerful tools for visualizing and navigating a non-linear development history.
Efficient handling of large projects. Git is very fast and scales well even when working with large projects and long histories. It is commonly an order of magnitude faster than most other version control systems, and several orders of magnitude faster on some operations. It also uses an extremely efficient packed format for long-term revision storage that currently tops any other open source version control system.
Cryptographic authentication of history. The Git history is stored in such a way that the name of a particular revision (a "commit" in Git terms) depends upon the complete development history leading up to that commit. Once it is published, it is not possible to change the old versions without it being noticed. Also, tags can be cryptographically signed.
Toolkit design. Following the Unix tradition, Git is a collection of many small tools written in C, and a number of scripts that provide convenient wrappers. Git provides tools for both convenient human usage and easy scripting to perform new clever operations.
Besides providing a version control system, the Git project provides a generic low-level toolkit for tree history storage and directory content management. Traditionally, the toolkit is called the plumbing. Aside the user interface coming with Git itself, several other projects (so-called porcelains) offer compatible version control interfaces - see the related tools list.

JavaScript is already well over a decade old

noreply@blogger.com (balasundaram g) — Mon, 08 Jun 2009 05:15:38 PDT

It’s hard to believe that JavaScript is already well over a decade old. Often relegated to marginal tasks in its early years, JavaScript has grown to become a pillar of modern web development. With the current popularity of DHTML and AJAX, it can be difficult to find a site that doesn’t use JavaScript anymore. One of the driving forces behind JavaScript’s newfound popularity is a proliferation of JavaScript frameworks, such as jQuery.
Why?
Click here to continue reading this article on the MIX Online site »

JavaScript is already well over a decade old

noreply@blogger.com (balasundaram g) — Mon, 08 Jun 2009 05:15:35 PDT