Team Build Compatibility between 2005 and 2008 VS

We are getting ready for a release at TWM this week. Next couple of days i will be cursing VSTS Team Build again!....
I was reading Buck Hodge's blog entry related to Team Build Compatibility between 2005 and 2008 VS. Let me share you the link wth you all.
http://blogs.msdn.com/buckh/archive/2007/07/27/team-build-compatibility-between-2005-and-2008.aspx

LateNight Thoughts!.....

One more weekend passed by!...It was silent. Nothing much happened from my side. But..Let me give you a clue. I am going to jump into a new area. Yes, will be sharing the news with you soon.

VSTS Useful links

I am spending lot of time with VSTS nowadays....

Again, sharing some useful links on VSTS.
1. FAQ's on TFS from Jim Lamp
http://blogs.msdn.com/jimlamb/articles/tfsfaq.aspx
2. TFS version control Command line summary:
http://blogs.msdn.com/buckh/articles/CommandLineSummary.aspx
3. Microsoft Visual Studio Team System Licensing White Paper
http://www.microsoft.com/downloads/details.aspx?familyid=1FA86E00-F0A3-4290-9DA9-6E0378A3A3C5&displaylang=en
4.Team Foundation Server - Build Automation Fourm
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=481&SiteID=1
5.Team Foundation Server - Version Control Forum
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=478&SiteID=1
6.VSTS Home
http://msdn2.microsoft.com/en-us/teamsystem/default.aspx

Some links : Basics of Dependancy Injection

Just thought of sharing some basic links to my readers who are new to Inverison of control principle and to Dependency Injection Pattern. This is n times better than my words about the same.!...
Enjoy reading.
From MSDN
http://msdn.microsoft.com/msdnmag/issues/05/09/DesignPatterns/default.aspx
An old blog post from Jeremy Miller
http://codebetter.com/blogs/jeremy.miller/archive/2005/10/06/132825.aspx
last , but not the least, A grt Article from Martin Folwer,
http://martinfowler.com/articles/injection.html

Thoughts of the day

I have to change the look and feel of this site. As a developer who learn agile methodologies, i am not suppose to stick to this Microsoft template site anymore. Nowadays I am running out of time and failed to reserve some minutes to make this site a standard one!.. (shame on me.. it is having different fonts, spelling mistakes, incomplate profiles, links, .. too bad....) I am sure, i am going to do it in couple of days now.

The truth is that... I am in love and love is blind!... Guess now, where I am spending my time .!.....Intelligent Investment for the future.!...

Back in action soon....

ALT.NET ........

ALT.NET ... was superb!....
Enjoyed the company of some fo the grt. people in the Microsoft Tech. world.I need to write more on each of the things on the same.
Two days full of dicussions, sessions, enjoyment, fun.....
Before i satrt bloggin about the same, lot many of my friends already started the same...
Here's couple of good links you can get go through ..
Jeffrey Palermo really spent some time to consolidate these links for the rest fo us. Thanks a TON!...
http://codebetter.com/blogs/jeffrey.palermo/default.aspx
I think this is enough to get all the realted links... enjoy reading...
I will blog more details about each moment soon...(I am running out of words now!..)

Microsoft to Release Source Code for .NET Framework 3.5

Interesting news...
Scott Guthrie has announced that Microsoft will be releasing the source code and debug symbols (aka PDB files) for the .NET Framework assemblies when they release .NET Framework 3.5 later this year.

From Scott Guthrie's Blog,........

"Today I'm excited to announce that we'll be providing this with the .NET 3.5 and VS 2008 release later this year.
We'll begin by offering the source code (with source file comments included) for the .NET Base Class Libraries (System, System.IO, System.Collections, System.Configuration, System.Threading, System.Net, System.Security, System.Runtime, System.Text, etc), ASP.NET (System.Web), Windows Forms (System.Windows.Forms), ADO.NET (System.Data), XML (System.Xml), and WPF (System.Windows). We'll then be adding more libraries in the months ahead (including WCF, Workflow, and LINQ). The source code will be released under the Microsoft Reference License (MS-RL).
You'll be able to download the .NET Framework source libraries via a standalone install (allowing you to use any text editor to browse it locally). We will also provide integrated debugging support of it within VS 2008."

Grt Starting...

Let me recall one of the famous advertisement words from IBM (One of my Prev. Employer!..) .... "When changes are part of the plan, that is on demand business!.."

ALT.NET Thoughts

Hi Friends,
I am ready for the ride.... Want to enjoy the drive from Dallas to Austin on Friday afternoon!... and then want to interact with the ALT.NET community.
I perfectly agree with Chip Lemmon's views and want to represent the "Marginal Developer "community around the world and my goal in ALT.NET is to listen to all the good/bad things and blog/share the same information to others.
Also i hate to talk ill about others , especially against Microsoft!....... Let's imporve ourself first.. than help others.
Hope to see you all there.

Multi Dimensional Seperation of Concerns

I was goign through an interesting research paper from IBM on Multi Dimensional Seperation of Concerns. Looks interesting to me.
Some tips from the same below...
Separation of concerns is at the core of software engineering in general, and of object-oriented software development in particular. Done well, it can provide a host of crucial benefits: additive, rather than invasive, change; improved comprehension and reduction of complexity; adaptability, customizability, and reuse, particularly of off-the-shelf components; simplified component integration; and the ultimate goal of "faster, safer, cheaper, better" software.
To benefit fully from separation of concerns, one must have the right modularization at the right time: the concerns that are separated must match the concerns one needs to deal with. Unfortunately, different development activities often involve concerns of dramatically different kinds. For example, changing a data representation in an object-oriented system might involve a single class, or a few closely-related classes, and might be done additively using subclassing or suitable design patterns. Here the hallmark of object orientation--modularization by class (or object)--is a major asset. On the other hand, adding a new feature to a system typically involves invasive changes to many classes: the feature code is scattered across multiple classes, and tangled with other code within those classes. This reduces comprehensibilty and increases impact of change and the likelihood of error. In short, one needs different modularizations for different purposes: sometimes by class, sometimes by feature, sometimes by aspect (e.g., distribution or persistence), role, variant or other criterion.
We use the term multi-dimensional separation of concerns to denote separation of concerns involving:
Multiple, arbitrary kinds (dimensions) of concerns.
Separation according to these concerns simultaneously; i.e., a developer is not forced to choose a small number (usually one) of "dominant" dimensions of concern according to which to decompose a system at the expense of others. This separation must be more than just identification of concerns and of the code that pertains to each. It must include segregation (encapsulation) that is sufficient to limit significantly the impact of change. This does not mean that every change within a concern can affect only that concern; this is never possible. It means that, just as modules in a dominant decomposition localize the impact of many kinds of change and limit the impact (propagation) of others, so must this be true of any of the concerns. More precise definition of this requirement is an interesting topic for discussion and for further research.
Overlapping or interacting concerns. It is appealing to think of many concerns as being independent or "orthogonal," but this is rarely the case in practice. It is essential to be able to support interacting concerns, while still achieving useful separation.
Recent approaches such as adaptive programming, aspect-oriented programming, composition filters, role-modeling and subject-oriented programming have enhanced object-oriented programming by providing separation of concerns along additional dimensions, beyond "class." Multi-dimensional separation of concerns is more general, and its goals are more ambitious, than these approaches; considerable research is still required before any existing approach fully achieves the goals listed above.
For more detailed reading ..http://www.research.ibm.com/hyperspace/MDSOC.htm

Separation of Concerns Principle

This principle states that a given problem involves different kinds of concerns, which should be identified and separated to cope with complexity, and to achieve the required engineering quality factors such as robustness, adaptability, maintainability, and reusability. The principle can be applied in various ways and it is no exaggeration to state that the separation of concerns principle is an ubiquitous software engineering principle.
From the Aspect Oriented Software Architecture Design Portal . They define the term Concern as ,
Concern:A canonical solution abstraction that is relevant for a given problem.

More : http://trese.cs.utwente.nl/taosad/separation_of_concerns.htm

"Don't call us, we'll call you".

I am in a very good mood to tell some theories today...
I went for a long drive, had nice dinner and now back in home....
Computer is not calling me today....Time for action (sleep)!...) Let it control me today, I used to control it most of the time.... (Is that called as IoC ? )
IoC is about inverting the control between objects. Thus, for example, rather than object A controlling object B, object B might be passed to A, such that it appears that the control is the other way up - i.e. inverted.
Miles to go before I sleep....

My The Scrum Master is My Business Analyst!

I recall i worked for a company they used to say "Customer First"... (Everyone does right?).

What if My Busniess Analyst/ My Business Manager became my Scrum Master and you are just one of the pigs!.... Good enough.. right??
What if you are just a chicken in the whole process? I can see three possible answers,
1. Are you just the part of the process (not the heart?? Are you Contracting for a Non -IT firm??)
2. Are you just do Agile?? ( This create a big impact!....)
3. What about other pigs .
Atleast one of my readers must ask... Are you in a wrong team/wrong environment?? Get the hell out of there!....