Gregory,
| If you include Team System, you get:
|
| 1. Class Designer
You don't need Team System for Class Designer, its in the Professional
version also.
--
Hope this helps
Jay [MVP - Outlook]
..NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley -
http://www.tsbradley.net
in message | 1. Generics
| 2. Refactoring tools - best with C#
| 3. Improvements in speed for Framework
| even 1.1 assemblies run faster in 2.0
| 4. New sets of APIs - esp. good with ASP.NET
| a) Membership/Profile
| b) Login/Security
| 5. ASP.NET
| a) Master Pages
| b) Improved Data Grid
| c) Local web server so devs can develop on
| machines without IIS
| 6. Ability to have the server monitor changed data
| best with SQL 2005 and 2.0 Framework
| 7. Improved ADO.NET
| a) Faster
| b) More tools
| c) Declarative model (when needed)
| d) Better data access
| 8. Faster Development
| a) Better Intellisense
| b) IDE keeps up with developer
| 9. Partial classes (your idea)
| This is a dual edged sword, as the benefits
| come with some potential gotchas
| 10. Better debugging - much easier to find problems
|
| If you include Team System, you get:
|
| 1. Class Designer
| 2. Unit Testing - similar to nAnt
| 3. Static Code Analysis
|
| With the Architect and Team roles (different SKUs) or the Team Suite, you
| get even more toys.
|
| --
| Gregory A. Beamer
| MVP; MCP: +I, SE, SD, DBA
|
| ***************************
| Think Outside the Box!
| ***************************
|
|
| "Glen W via DotNetMonster.com" wrote:
|
| > I need 10 reasons to give to my boss to convince him to upgrade to VS
2005.
| >
| > So far I've got the 2 obvious ones: Generics and Refactoring, one makes
code
| > safer the other makes writing code easier. I also like snippets and
partial
| > classes.
| >
| > Any other suggestions would be greatly appreciated.
| >
| >
| > --
| > Message posted via DotNetMonster.com
| >
http://www.dotnetmonster.com/Uwe/Forums.aspx/dotnet-general/200510/1
| >