At present are only fairly certain we can install .net 3.0 on a user’s machine here at the bank. So when starting new projects, I recommend we select .net 2.0 unless you feel certain the target users will be able to install .net 3.5, and possibly .net 3.5 sp1 since that’s what comes with our VS2008.
Here’s what that grants us access to over .net 2.0:
- Windows Presentation Foundation (WPF), formerly code-named Avalon; a new user interface subsystem and API based on XML and vector graphics, which uses 3D computer graphics hardware and Direct3D technologies. See WPF SDK for developer articles and documentation on WPF.
- Windows Communication Foundation (WCF), formerly code-named Indigo; a service-oriented messaging system which allows programs to interoperate locally or remotely similar to web services.
- Windows Workflow Foundation (WF) allows for building of task automation and integrated transactions using workflows.
- Windows CardSpace, formerly code-named InfoCard; a software component which securely stores a person's digital identities and provides a unified interface for choosing the identity for a particular transaction, such as logging in to a website.
Not much that I know how to take advantage of at present, the only thing I see that might be useful for us to learn is Windows Workflow Foundation.
.Net Framework 3.5 on the other hand brings tons and tons of new features and classes:
Changes since version 3.0
- New language features in C# 3.0 and VB.NET 9.0 compiler
- Adds support for expression trees and lambda methods
- Extension methods
- Expression trees to represent high-level source code at runtime.[22]
- Anonymous types with static type inference
- Language Integrated Query (LINQ) along with its various providers
- LINQ to Objects
- LINQ to XML
- LINQ to SQL
- Paging support for ADO.NET
- ADO.NET synchronization API to synchronize local caches and server side datastores
- Asynchronous network I/O API[22] .
- Peer-to-peer networking stack, including a managed PNRP resolver[23]
- Managed wrappers for Windows Management Instrumentation and Active Directory APIs[24]
- Enhanced WCF and WF runtimes, which let WCF work with POX and JSON data, and also expose WF workflows as WCF services.[25] WCF services can be made stateful using the WF persistence model.[22]
- Support for HTTP pipelining and syndication feeds.[25]
- ASP.NET AJAX is included
- New
System.CodeDomnamespace.
This is not to say that VS2008 did not bring us new features, functionality and enhancements:
No comments:
Post a Comment