Modeling that Works with Code in VSTS 2010

For most businesses only 20% of the code being written today for new applications; the majority of work is being done on existing code bases.
When working on existing code, architects and developers don’t necessarily good enough tools to understand the system, know what needs to be done to make required updates, or be able to anticipate the impact of changes made. Often it isn’t until much later that an unexpected bug is discovered as a result of a change.
Our modeling tools have tight integration into the actual code of the application. This means that a developer or architect can use models to explore existing code assets. The new Architecture Explorer in Visual Studio Team System gives developers and architects the capability of 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.
The introduction of the Architecture Layer Diagram means that a developer or architect can use models to enforce constraints on code as well. The Architecture Layer Diagram can be coupled to code making it an active diagram that can be used for validation. For example, when an architect designs a system where the presentation layer should not talk to the data layer, you want to be able to enforce that model at check-in. Visual Studio Team System 2010 can do that. These capabilities delivered in VSTS 2010 are part of the Microsoft’s overall modeling story.

how to incorporate the Validation Application Block into your application

To prepare your application

1. Add a reference to the Validation Application Block assembly. In Visual Studio, right-click your project node in Solution Explorer, and then click Add References. Click the Browse tab and find the location of the Microsoft.Practices.EnterpriseLibrary.Validation.dll assembly. Select the assembly, and then click OK to add the reference.
2. Use the same procedure to set a reference to the Enterprise Library Common assembly, named Microsoft.Practices.EnterpriseLibrary.Common.dll.
3. Follow the same procedure to set a reference to the ObjectBuilder assembly, Microsoft.Practices.EnterpriseLibrary.ObjectBuilder 2 .dll.
4. If you are using the ASP.NET, Windows Forms, or WCF integration assemblies, add one of the following references as appropriate.
   • Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WinForms.dll
   • Microsoft.Practices.EnterpriseLibrary.Validation.Integration.AspNet.dll
   • Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF.dll
5. (Optional) To use elements from the Validation Application Block without fully qualifying the type with the namespace, add the following using statements (C#) or Imports statements (Visual Basic) to the top of your source code file.

   C#
   

   using Microsoft.Practices.EnterpriseLibrary.Validation;
   using Microsoft.Practices.EnterpriseLibrary.Validation.Validators;

   Visual Basic
   

   Imports Microsoft.Practices.EnterpriseLibrary.Validation
   Imports Microsoft.Practices.EnterpriseLibrary.Validation.Validators

Note:

For Visual Basic projects, you can use the References page of the Project Designer to manage references and imported namespaces. To access the References page, select a project node in Solution Explorer. On the Project menu, click Properties. When the Project Designer appears, click the References tab.

Microsoft Web Application Stress Tool 1.1

------------------------
Installation Notes
------------------------

Microsoft Web Application Stress Tool requires Microsoft
Windows NT version 4.0 Service Pack 4 or above and Microsoft
Internet Explorer version 4.0 or above.

------------------------
Online Support
------------------------
To check for the latest news and updates regarding this tool
you can go to the web site http://webtool.rte.microsoft.com.
This web site contains a knowledge base that provides
in-depth answers to performance testing questions and
additional information on the most frequently asked
questions.

------------------------
Known Issues
------------------------
Web Application Stress Tool only supports stress against one
server or DNS name at a time.
To use authentication, you must add users with valid user
names and passwords.
To record, you will need to modify your browser settings if
using a browser other than, or prior to, IE 5.0. See online
help for more information.
Webtool respects the "user-agent: stress-agent" directive in
the ROBOTS.TXT file on a web server and will not start a
stress test against a server or domain that contains this
file with this directive. This file should be located in
the root directory of your web site

In general, you should NOT install the WebTool service on
the web server you are testing since this may interfere with
your results.

The Web Application Stress Tool object model can be used to
start, stop, and configure a test run.  However, this feature
cannot be used to modify a running test in this version of
the tool.

Web Application Stress Tool is year 2000 compliant.

IMPORTANT: Start your test with a small number of
Concurrent Connections and then work your way up to the
desired stress level slowly, watching the processor
utilization on the clients and web server. If the
processor utilization is consistently above 90% on one or
more machines, the test is probably invalid. If this
occurs, decrease the number of concurrent connections or
add more client machines to handle the desired stress load.

On-line help contains a discussion of performance testing
techniques.

Although there is no hard limit on the number of script
items you can have in one script, the most practical limit
is 3000 script items. Beyond that you will find that it
takes an inordinately long time to start and stop tests.

Excel 2007 Developer Reference

This reference contains conceptual overviews, programming tasks, samples, and reference documentation for developing solutions that are based on Microsoft Office Excel 2007.

Publish date of this reference: April 2009 (version 2007)

This documentation can be accessed from the following locations:

• From the product (most recent version):  If you are connected to the Internet, you can view the most recent version of this reference in Excel. Click Help, and in the Search box, under Content from Office Online, click Developer Reference.
• From the product (installed version):   If you are not connected to the Internet, you can still view the version of this reference that was included with your product. Click Help, and in the Search box, under Content from this computer, click Developer Reference. October 2006 (version 2007) is included with the product.
• From the MSDN Library.  To view the April 2009 version of this reference in the MSDN Library, click the items in the MSDN table of contents that is displayed in the navigation pane of your browser.