July 17, 2009

what is new in Visual Studio 2010 and the .Net Framework 4.0

Another version, Microsoft VS 2010 and Framework 4.0. I am still working on 2.0. I need to jump 3.0 and 3.5. Companies barely working on 3.5 version, because very less application are being developed for 3.5 version. Don't know when 4.0 will get speed. My whole carrier will go into updating myself for the new versions of Microsoft .net framework, visual studio and of course new Windows. But i guess thats life of a programmers. I am still on XP (loving it).
Anyways with invent of new systems Microsoft is coming with the a lot of feature that surely need developer and System to update. But features are great.
as from 2.0 to 3.5 we got Generics, Linq, entity-framework, WCF, WPF etc. so what's in 2010. & 4.0
here is answer.

jQuery - In 2010 major changes has been done for high performance and standard javascript standards compliant JavaScript IntelliSense engine. Microsoft and Jquery group working together to make developer life easy, so Visual Studio 2010 will be the first version of Visual Studio to ship JQuery as a native part of the ASP.NET solution

MVC - All features of "Preview release of ASP.NET MVC" included in Visual Studio 2010
2010 make very easy to build Model-View-Controller aka MVC sites.
n Visual Studio 2010 we deliver the next generation of ASP.NET web tools that make it easy for developers to use TDD to build Model-View-Controller (MVC) based web sites. Wizard based interface to creating views, generating test project for MVC solution. Various templates are given.

One Click Deployment - IDE provides a wizard, dialogs and design surfaces that make it simple for developers to identify the components of a website that need to be deployed and make it easy to handle the process of moving them from the development machine to the web server, One Click Deployment come as heaven for developers as often moving from development to production various changes need to be done in config file like removal of trace, debug and local database/development connection. There is feature to set custom transformation when moving from development to production. so those will be applied every time.

Silverlight,- Integrated support for silverlight, full debugging support for silverlight applications. existing content can be used on aspx pages very easily. Guess SL 3.0 will also be made native in the final release.

Windows® Azure ™ - Support of Azure tools in 2010. Windows Azure Tools provide the means to create services and applications within the framework of Visual Studio. That includes a project model specifically for Windows Azure, as well as the debugging capabilities of Visual Studio. With Visual Studio, you can build a package containing your service, and use Windows Azure Tools to deploy the package to Windows Azure through the Windows Live Developer Portal.

Parallel Development support: what does it mean.
The .NET Framework 4.0 also provides the core framework support to build parallel applications through technologies such as P-LIINQ and parallel language semantics and framework components. Visual Studio 2010 provides integrated parallel development support. In Visual Studio 2010 the debugger is aware of the parallel nature of code and can present the state of the application execution during debugging across the different parallel execution units. The debugger also has custom displays for parallel code such as task & thread windows and a “multi” or “cactus” stack view window that graphically shows the execution path of the individual tasks.
Vs 10 also got "parallel capable performance analyzer" that helps you to extensively instrument you code to visually see the concurrency issues that are in your applications (WOW).
& this is the one of few new feature of 4.0, all rest are enhancement to Wxx technologies.

Modeling with Code: Thats the feature i was searching in previous versions, its very great feature, may be its already part of rational packs, but with Vs it makes life easy of developer, PM & architect. What is it?
While working with existing code. its very tough to examine real code as model, understand the impact of the changes,
So 2010 has very good integration with code. Now real code can be examine as model & see real code assets. So it creating a full architectural picture of existing code; understanding how they fit together; understanding how they “work.” This leads to better information about using, re-using, or discarding existing code. The Architecture Explorer provides architects and developers a mechanism for visualizing code assets in a number of ways including graphs, stacked diagrams and dependency matrices.
this feature is part of VS team suite
More UML Support.

so now from model you can validate whether presentation directly talking to DB layer. It can also be enforced. (WOW). it will save a lot of man days.

“No-Rrepro” Bugs: Another great feature of team suite.
what the hack it is -> From designing an application through developing code, finding bugs that can’t be reproduced is a common problem – the “no-repro” bug.

  • Visual studio 2010 can specify the exact state of the build used by a tester and allow a comparison to the state of the build used by the developer when trying to reproduce the bug.
  • It has tool "Microsoft Test Runner" case.
  • When the test case is started the Microsoft Test Runner takes a snapshot of the system data, including OS version and Service Pack and other pertinent system data.
  • As the test is being run the tester can use the tool to capture images of the application under test, or even partial or full screen video of the test being run.
  • If an issue is discovered, the tester can create a new bug in Team Foundation Server and attach these artifacts.
  • When attached, the screen capture video is fully indexed with the test steps as bookmarks, making it easier for the developer to see what went wrong on the tester’s machine.
  • All of these artifacts help to eliminate the no-repro scenario, and help build a better bridge between development and test.
Test Impact Window : The new Test Impact View window enables a developer to view a list of tests that need to be run as the result of a code change. The developer can toggle between an Impacted Tests view and a Code Changes view.
• The Impacted Tests view provides a list of tests that need to be run and which code changes are covered by each of the tests.
• The Code Changes view provides a list of code changes and which tests must be run in order to validate each of them.These two views provide a easy way to discover what tests must be run in order to validate the changes to the code base without having to run all of the tests. This ensures that all changes are tested effectively

many more features: F# support, ajax extension,

Training Kit is here: http://blogs.msdn.com/onoj/archive/2009/05/22/visual-studio-2010-and-net-framework-4-training-kit-vs10.aspx

Follow updates : http://twitter.com/onojw

currently beta1 download available.

--Compiled from Microsoft® docs.

No comments: