Refractoring Making changes to your code like, "pulling a large stretch of inline code into its own method" or "converting a field to be a property." The Refactoring support makes this easy to do The key tenet of Extreme Programming created by Kent Beck is constant Refactoring. Under this programming model, you are developing code rapidly and iteratively, but to keep your code from becoming a jumbled mess, you must constantly Refactor. Refactoring is a C# only feature[enter][/center]
Edit and Continue Visual Basic has always been about Rapid Application Development (RAD). One key feature is the ability to fix runtime errors on the fly. With Visual Basic .NET 1.0 and Visual Basic .NET 1.1, this powerful feature wasn't included. This feature is on-board for Whidbey. If you run into an exception at runtime, you get an exception helper that provides tips for fixing common errors, but more importantly, you can edit the code, select F5, and it continues right where you left off. Edit and Continue is VB .NET only feature
ClickOnce ClickOnce make it easy to install applications and provide ongoing updates (Self-Updating), rather than forcing to distribute new versions of application, can just deploy the portion of the application which has changed. In the .NET Framework 1.0 and 1.1, href-exes were not able to solve many deployment issues. Href-exes are also known as ''no-touch deployment, or zero impact deployment''. Essentially, with versions 1.0/1.1, you can deploy an application to a Web server, allowing users to browse to the URL for the exe, as in: You can run me by clicking this link When the user clicks the link, the application downloads to their Internet files cache and runs. To keep this from being a huge security hole, the application permissions are restricted based on the URL (Intranet applications get different permissions than Internet applications, for example), or other factors. This means that some applications no longer need to be deployed in the traditional sense; no more setup.exe or MSI
href-exes have a number of limitations
The .NET Framework must be pre-installed on the client machine.
There's no good way to bootstrap the .NET Framework down if it's not there.
Most non-trivial applications consist of the main .exe and a number of assembly files. With href-exes, the assembly files are downloaded on demand, which is great for corporate Intranet applications, but there's no way to download the application in one shot so that you know it can be safely used off-line.
Limited support for versioning.
The application doesn't hook into Add/Remove Programs, and the application doesn't install Start menu shortcuts.
ClickOnce deployment differs from href-exes in some significant ways
ClickOnce applications are self-updating.
With href-exes you can only make the application self-updating through the use of custom code or through the use of a component, such as the .NET Application Updater component.
With ClickOnce, updates can also be marked as mandatory or optional.
When applications are installed through ClickOnce, they show up in the start menu and they can be uninstalled through the '''Add/Remove Programs''' feature.
ClickOnce works its magic through two XML manifest files.
The first is an ''application manifest'' and
The second is a ''deployment manifest''.
The application manifest describes the application itself, which includes information about the application assemblies, dependencies, and files that make up the application. The application manifest also states the required permissions, and the location where updates can be downloaded.
The deployment manifest points to the location of the application manifest and files, and instructs the clients on which version of the application they should be running.
SmartTags This provides access to information and common tasks without forcing you to constantly navigate away from your work area [enter][/center]
Code Snippets With code snippets, you can insert generic "template" code that requires only that you fill in the blanks. You can access code snippets by right-clicking in the code editor and navigating in the context menu to Insert Snippets [enter][/center]
Exporting IDE Settings With Whidbey, migrating and persisting IDE settings are a simple process of navigating to Tools Import/Export Settings. [enter][/center]
Line Revision Marks Line Revision marks allow you to see the changes you've made during a coding session. When writing code in the IDE, you'll notice yellow and Lime lines appearing down the left hand side of the code editor window. [enter][/center]To change the color, navigate to '''Tools Options''' in the IDE, and then choose '''Show All Settings'''. After that expand '''Environment''' click on the '''Fonts and Colors'''. Scroll down the '''Display Items'''
'''Track changes before Save''' - yellow
'''Track Changes after Save''' - Lime
Temporary Projects Visual Studio .NET 2002 and Visual Studio .NET 2003 both had a propensity to persist your temporary ideas as permanent projects on your hard disk. This created the ''WindowsApplication1,2,3...n'' problem. Visual Studio .NET supports the idea of temporary projects. if you attempt to close the IDE without saving, it will prompt you to either save or ''discard'' the project
About the author Vidya Vrat Agarwal, a Microsoft .NET Purist, and a MCSD.NET, MCAD.NET, MCSD, MCT. He is also a Life Member of Computer Society of India (CSI). He started working on Microsoft.NET with its beta release. He has been involved in software development, corporate trainings, T3 programs, technical writing and consultation for Microsoft.NET for various corporate clients. Presently he is working with LionBridge Technologies in Mumbai - India, where he works with Microsoft Dept. on Whidbey and Yukon and his business card reads Subject Matter Expert His technical profile holds .NET Framework, VC#, VB.NET, WebServices, Remoting, SQL Server, COM, DCOM, COM+, MTS, MSMQ. Whidbey, Yukon and Longhorn.
