Tuesday, December 26, 2006

TOC of Book

In respect to lot of mails that i received about Table Of Contents(TOC) of our book , so here is the attached TOC for my book, Pro WCF: Practical Microsoft SOA Implementation for APress Publication. The book is divided into three parts, with first being the introduction to WCF , second about programming and third on Advanced topics of WCF.


PART 1
Introducing Windows

Communication Foundation

nCHAPTER 1 Introducing Service-Oriented Architecture . . . . . . 3

nCHAPTER 2 Introducing WCF Basics . . . . . . 25

nCHAPTER 3 Exploring the WCF Programming Model . . . . . . . 51

PART 2 Programming with WCF

nCHAPTER 4 Installing and Creating WCF Services . . . . . . . . . . . . . 99

nCHAPTER 5 Hosting and Consuming WCF Services . . . . . . . . .145

nCHAPTER 6 Managing WCF Services . . . . . . . . . . . . . . . . . . 179

PART 3 Advanced Topics in WCF

nCHAPTER 7 Implementing WCF Security . . . . . . . . . . . . . . . .. . . . .213

nCHAPTER 8 Implementing Reliable Messaging and Queue-Based

Communications . . . . . . . . . . . . . . . . . . . . . . . . . 249

nCHAPTER 9 Using Transactions in WCF . . . . . . . . . . . . . . 277

nCHAPTER 10 Integrating with COM+ . . . . . . . . . . . . . . . . . . .301

nCHAPTER 11 Working with Data . . . . . . . . . . . . . . . . . . . . . . . .335

nCHAPTER 12 Developing Peer-to-Peer Applications with WCF . . . . . . . . . . 371

nCHAPTER 13 Implementing SOA Interoperability . . . . . . . . . . . . . . . . . . . . 401

PART 4 Appendixes

nAPPENDIX A QuickReturns Ltd. . . . . . . . . . . . . . . . . . . . . . . . . . . 425

nAPPENDIX B History of Microsoft Web Service Implementations . . . . . . . . .431

nAPPENDIX C WCF and .NET Framework Installation Steps . . . . . . . . . . . . . 441


Friday, December 22, 2006

Book scheduled Date on January 15

Hi all
As you all knew that, i along with my colleague is involved in writing a book on WCF for APress Publication. Some good news that i would like to share with you is Book is on the print and if every thing goes fine, is scheduled to hit the market on January 15. The book has been foreword by none other than Thom Robbins.He is presently working as a Director for .NET Platform Marketing and is associated with Microsoft for almost six years. And as many of you has asked, I will furnish the TOC by today or in this weekend.

Saturday, September 02, 2006

WCF RC 1 go live

Much awaited news... The Windows Communication Foundation's Release Candidate are now live.

you can download the .NET Framework 3.0 with the WCF bits from
http://www.microsoft.com/downloads/details.aspx?FamilyId=19E21845-F5E3-4387-95FF-66788825C1AF&displaylang=en

for more info, visit clemens blog


Wednesday, August 02, 2006

MSDN for Free download

Now, MSDN Library is free for download without any MSDN Subscription. you need to be connected to avail the benefit. It can be free download to everyone: http://www.microsoft.com/downloads/details.aspx?FamilyID=373930cb-a3d7-4ea5-b421-dd6818dc7c41&DisplayLang=en

 

Friday, July 21, 2006

.NET Framework 3.0 July CTP is out


Win Fx aka .NET Framework 3.0 's July CTP is out and can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyId=62057A6F-185F-41DB-ABE5-678F6FC388F0&displaylang=en.
Downloaded it yesterday and found that there is still some documentation missing and there are no VS Extensions with
this version. Not much major changes from June CTP as far WCF
is concerned..




Wednesday, June 21, 2006

My first book





Thought to share with you now for the work that i and few of my colleagues were working on since many months. I am a coauthor of this book and the book is on Windows Communication Foundation alias Indigo. The book is more on developer's perspective of analyzing WCF and using Service Orientation. More info is available on
http://www.apress.com/book/bookDisplay.html?bID=10185

I will also be posting few articles on WCF on my blog.. So keep tracking ..

Friday, April 07, 2006

new command interpreter : MONAD

Shells are used as the command interpreter in unix/linux. In Microsoft
windows, it is been done by cmd.exe. Microsoft is coming up with the
new command interpreter for Windows Vista and is termed as Monad
(Monad Shell) or MSH. This Monad interpreter runs in any OS where
.NET 2.0 can be installed such as Windows XP SP2 or Windows Server
2003 SP1. Learn more about Monad with
http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

Tuesday, February 28, 2006

Feb CTP : No Pain No Gain

Feb CTP is out on http://www.microsoft.com/downloads/
details.aspx?FamilyId=F51C4D96-9AEA-474F-86D3-1
72BFA3B828B&displaylang=en
. There are lots of changes
between Jan and Feb CTP.If talked about WCF, November,
December and jan CTP are on the same track while on feb
CTP, they had added few DCRs that Microsoft was working
in silos earlier. Anyhow, its really a pain to see keywords and
namespace changing with every CTP but i do believe the
Feb CTP is now very stablized and close to what the final
RTM will look like.

 

 

Thursday, January 19, 2006

WCF and WWF Go live

Microsoft announced Go Live licenses this morning for Windows
Communication Foundation (WCF, previously - Indigo)
and
Windows Workflow Foundation (WWF) , which lets customers
use the January Go Live releases of WCF and WWF in their
deployment environments. WPF is not included in it. More
information about the Go Live program is at
http://msdn.microsoft.com/winfx/getthebeta/
golive/default.aspx
.

Monday, January 16, 2006

Windows Vista Release date , Nov 2, 2006

Microsoft are likely to hit final Vista product with a deadline of Nov, 2 , 2006. So now we are preety sure that we can get the hands on experience on RTM of Windows Vista in this year. Earlier the release date was scheduled on June,2006 but testing staff for Vista has proposed a new date for it

Friday, January 13, 2006

SetFocusOnError property in ASP.NET 2.0

In ASP.NET 1.x, if we want to put the focus on a control if a validation fails based on the validation control, we need to tweak around webUiValidation.Js and modify it to work for us. Now in ASP.NET 2.0, we got a couple of options to do it. We got a SetFocus method as a part of Page in which we can pass the id of the control to get focus,

 Page.SetFocus(txtName);

we got a new property called SetFocusOnError which is set on validator controls to cause the first invalid control to receive focus.

<asp:TextBox ID="txtRollId" runat="server"></asp:TextBox>
 <asp:RequiredFieldValidator SetFocusOnError="true"
ErrorMessage="RollId is empty" ID="RequiredFieldValidator2"
ControlToValidate=" txtRollId" Display="Dynamic"
runat="server">*
</asp:RequiredFieldValidator>
Check out the SetFocusOnError = true set in requiredFieldvalidator
 

Friday, January 06, 2006

MSBuild - Part 2

Implementing MSBuild in Whidbey

You can implement MSBuild in Whidbey by creating an MSBuild project file that you can use to compile a .NET project. The MSBuild project file is an XML file with the .proj extension. The MSBuild project file describes the build process of a .NET project. A console application of the MSBuild tool, called msbuild.exe, performs the build process. This application receives project files as input and processes them synchronously. You can create an MSBuild project file using the Visual Studio .NET IDE. To create an MSBuild project file:

1.         Create a folder, MSBuild, at the C:\WINNT\System32\ location to save the project file.

2.         Copy the msbuild.exe file from the C:\WINNT\Microsoft.NET\Framework\v2.0.40607 location and save it at the C:\WINNT\System32\MSBuild location.

3.         Select Start -> Programs -> Microsoft Visual Studio Whidbey -> Microsoft Visual Studio codename Whidbey to open the Microsoft Visual Studio Whidbey IDE.

4.         Select File -> New -> File to open the New File window

5.      Select XML File and click Open to open the Code Editor window
Enter the code in the Code Editor window to create an MSBuild project file.

6.      Select File -> XMLFile1.xml to open the Save File As dialog box.

7.      Select the MSBuild directory from the Save in drop-down list box to specify the location where you want to save the project file.

8.      Select the All Files (*.*) option from the Save as type drop-down list box and enter the MSBuildProj file name with the .proj extension in the File name text box to create an MSBuild project file.

9.      Enter the following command at the command prompt to build the MSBuild project file that you create:

       WINNT\System32\MSBuild MSBuild MSBuildProj.proj