Wednesday, May 20, 2009

Visual Studio 2010 and .NET Framework 4.0 Beta 1 Released Today! (Lisa Feigenbaum)

Published 20 May 09 01:56 PM

The public availability of Visual Studio 2010 and .NET Framework 4.0 Beta1 was announced today on Jason Zander's blog:

Below are some resources to use as you download and start using the Beta.


Lisa Feigenbaum | Program Manager | VS Languages

VB, C#, and F# 2010 on MSDN

These are the best one-stop shops for information on what’s new in VB, C#, and F# in VS2010:




Additional VS2010 resources

· VS2010 Download page

· VS2010 Walkthroughs

· MSDN Library: What’s New in Visual Studio 2010

· VS2010 Connect

· Forums: VS, VB, C#, F#

· Samples: VS, VB, C#, F#

· Language specs: VB, C#, F#

· IronPython 2.6 CTP for .NET 4.0 Beta1

by VBTeam

Filed under: Lisa Feigenbaum, VB2010

Monday, May 18, 2009

What about GIT?

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.

Friday, May 15, 2009

JavaScript is already well over a decade old

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.


Click here to continue reading this article on the MIX Online site »

Accessibility Levels (C# Reference)

Use the access modifiers, public, protected, internal, or private to specify one of the following declared accessibilities for members.

Declared accessibility


Access is not restricted.


Access is limited to the containing class or types derived from the containing class.


Access is limited to the current assembly.

protected internal

Access is limited to the current assembly or types derived from the containing class.


Access is limited to the containing type.

Only one access modifier is allowed for a member or type, except when using the protected internal combination.

Access modifiers are not allowed on namespaces. Namespaces have no access restrictions.

Depending on the context in which a member declaration takes place, only certain declared accessibilities are permitted. If no access modifier is specified in a member declaration, a default accessibility is used.

Top-level types, which are not nested into other types, can only have internal or public accessibility. The default accessibility for these types is internal.

Nested types, which are members of other types, can have declared accessibilities as indicated in the following table.

Members of
Default member accessibility
Allowed declared accessibility of the member










protected internal









The accessibility of a nested type depends on its accessibility domain, which is determined by both the declared accessibility of the member and the accessibility domain of the immediately containing type. However, the accessibility domain of a nested type cannot exceed that of the containing type.

C# Language Specification

For more information, see the following sections in the C# Language Specification:

  • 3.5.1 Declared Accessibility

  • 3.5.3 Protected access for instance members

  • 3.5.4 Accessibility constraints

  • 10.2.3 Access Modifiers

  • Declared Accessibility

See Also

C# Keywords
Access Modifiers (C# Reference)
Accessibility Domain (C# Reference)
Restrictions on Using Accessibility Levels (C# Reference)
Access Modifiers (C# Programming Guide)
public (C# Reference)
private (C# Reference)
protected (C# Reference)
internal (C# Reference)
C# Programming Guide
Other Resources
C# Reference