Source code for .Net Framework Libraries are available for download with the next release of VS 2008 and .Net 3.5 next year.
ScottGu explains more.

Have been said, it’s way too advance for me to dig through those source code as I’m still struggling to learn the efficient use of the libraries itself. But hey, it’s all good that you get the source too. Cool!

Hi, Sorry for long absent; blogger is currently attending Tech-Ed 2007 at Gold Coast Convention Center for a week from 6th to 10th Aug. She’ll be then visiting Sydney for 3 days and Adelaide for another 3 days. Blogger will be back on 18th Aug.

Couldn’t blog long. Just dropping a line during session break. I’ll write about my Tech-Ed experiences very soon. At the moment, I’m at “Ask the Expert” session, and quickly posting this. I got one exam to sit tomorrow and couldn’t finish studying yet. Gotta cram tonight.

Anyways gotta run. Will post about things properly later. Tar.

Guess what, there is a new feature on Google Reader. It’s going offline. You now have an option to read your feeds in offline or online mode.

We’ve used the newly released Google Gears, a browser plugin that enables offline web applications. Once you’ve installed Google Gears, you can download your latest 2,000 items so they’re available even when you don’t have an internet connection. To get started, simply click the “Offline” link in the top right of Google Reader.

You’ll need to download the Google Gears Setup file (188kb) which then download and install the plugin directly. This would take a while if your connection is slow.

Google Gears (Beta) is an open source browser extension that enables web applications to provide offline functionality using following JavaScript APIs:
# Store and server application resources locally
# Store data locally in a fully-searchable relational database
# Run asynchronous Javascript to improve application responsiveness

Once it’s done, you need to restart your browser and allow the plugin on the site. You then have the option to download your feeds and save them for offline reading.

Enabling the Google Gears plugin for the site


Downloading Feeds for offline reading

Online and Offline modes can be easily switched through by clicking on the tiny button at the top. The reader will synchronize the feeds accordingly.

Reader in Offline mode

More Info Links:
# Developer Site
# Developer Knowledge Base

Isn’t just sweet?

Over at WordPress.com, 3 new features have been added. Out of them, “Contact Form” features is very higly awaited feature and now it’s been out.

Here’s how: put

[contact-form]
in any post, and a simple contact form asking for the sender’s name, email address, website and comment will be inserted. When someone submits a message through the form, you receive that message in an email.

Other two include:
# Box.net Filesharing Widget
# More Slideshows

Personally, I don’t like slideshows so won’t be of much use for me but contact form is definitely a yes and the filesharing widget too. There are some more widget goodies under “Presentation Sidebar Widget” tab so check them out yarrh.

The core mission of a version control system is to enable collaborative editing and sharing of data. Different systems use different strategies to achieve this. There are two main versioning models namely “Lock-Modify-Unlock” and “Copy-Modify-Merge“.

Lock-modify-unlock

In this model, the repository allows only one person to change a file at a time. This exclusively policy is managed using locks. VSS and old style source controls use this approach where only one person at a time can modify a file. Lock the file, edit, then check in and release the lock. This model is only suitable for a small teams. For a bigger team with many developers, it would be inefficient to use this model as locking isolates a file to only one developer which delays the work among other team members who want to work on the file.

The lock-modify-unlock model (Ref #)

The problem with the lock-modify-unlock model is that it’s a bit restrictive, and often becomes a roadblock for users:

• Locking may cause administrative problems.
  if one developer forgot to unlock a file before he take a leave would cause others to delay working on the file unless an administrator to release the lock.
• Locking may cause unnecessary serialization
  if developers are to edit different part of the file, it’s is unnecessary to unlock and edit. It should be edited together then merge the file.
• Locking may create a false sense of security

(Ref: pp. 4)

Copy-modify-merge

In this model, each user’s client contacts the project repository and creates a personal working copy – a local reflection of the repository’s files and directories. Users then work simultaneously and independently, modifying their private copies. Subversion, CVS and a number of other version control systems uses this model as an alternative to locking. Early version of Subversion did not support locking at all, but this is no longer the case. You can now lock files, query files to see who has locked then, and even mark files as requiring locks before edits. This make sense for binary files where merging is impossible. (Ref: pp 5)

Copy-Modify-Merge model (Ref #)

NB: TortoiseSVN provides a good built-in diff tool; you can also install WinMerge (http://winmerge.org), which integrate itself into TortoiseSVN.

When Locking is Necessary

While the lock-modify-unlock model is considered generally harmful to collaboration, there are still times when locking is appropriate.

The copy-modify-merge model is based on assumption that files are contextually mergeable: ie. that the majority of the files in the repository are line-based text files(such as program source code). But for files with bonary formats, such as artwork or sound, it’s ofter impossible to merge conflicting changes. In these situations, it really is necessary to users to take strict turns when changing the file. Without serialized access, somebody ends up wasting time on changes that are ultimately discarded.

While Subversion is still primarily a copy-modify-merge system, it still recognizes the need to lock an occasional file and provide mechanisms for this. (Ref: pp 7)

Ref:
#Don’t Use Microsoft Visual SourceSafe!,
# subversion documentation | Online version

Crazy Egg is yet another web statistic tracking service. It displays in 3 formats:

• Overlay – % clicks, referal links
• List – view a full summary of raw clicks
• Heat Map – shows the most click areas on the page.

There are 3 paid plans and a free plan. A free account is ideal for a small personal site such as blog to track the visitor stats. Ofcos, there is a limit of 5,000 visit/month, 4 pages and 4 screenshots archive for the free plan. Very neat interfaces so you can consider using it for your blog stats tracking.

Here are some of the readings on Subversion and VSS that I came across. Whoever interested in Source Control and its available tools should go through these links first to get to know the technologies out there. I’m just concentrating on SVN and VSS, but there are a lot more to look at. Depending on your choice of technology, google would be your best reference.

Documentations:

• Subversion Software (Wiki): Subversion features and support wiki
• SVN Documentation: documentation on latest svn, available in pdf and html downloads
• TortoiseSVN Tutorials: step by step tutorial on using TortoiseSVN
• AnkhSVN Wiki Home: svn Visual Studio plugin – AnkhSVN support wiki.

Good Reference Articles

• Branching & Merging Primer: very good explanations on various form of branching and merging.
• Source Control HOWTO: Series of articles explaining how to do source control and the best practices.
• Subversion Resources at Open Directory: various resources and plugins for svn on multiple platforms.
• Subversion versus Perforce: Popular source code management tools go head to head: good comparison on svn vs perforce by the register
• My Experiences With Subversion: good article on personal experience with svn.
• Steps in starting up with Subversion – moving away from Sourcesafe

No to Visual SourceSafe? Bad Toad! Bad Toad!

• Don’t Use Microsoft Visual SourceSafe!
• Source Control: Anything But SourceSafe: strong emphasis on not to use VSS.
• Visual SourceSafe: Microsoft’s Source Destruction System: points out the disadvantages of VSS in terms of features as well as code safety.
• Visual SourceSafe Version Control: Unsafe at any Speed?

I’ll be adding more later and if you find some good readings/articles, do let me know too.