From 295dc50dbb8aca2f6c853213a15a366ccbfcdaee Mon Sep 17 00:00:00 2001 From: sbohlen Date: Thu, 28 Jul 2011 22:38:12 +0000 Subject: [PATCH] mods to docs to reflect 1.3.2-specific info and references to associated projects --- doc/reference/src/migration.xml | 30 +++----- doc/reference/src/overview.xml | 118 +++++++++++++++++++++++++++++--- doc/reference/src/vsnet.xml | 82 +++++++++++++++++++--- 3 files changed, 190 insertions(+), 40 deletions(-) diff --git a/doc/reference/src/migration.xml b/doc/reference/src/migration.xml index dbb89013..653e75dd 100644 --- a/doc/reference/src/migration.xml +++ b/doc/reference/src/migration.xml @@ -152,31 +152,21 @@ NamespaceParserRegistry.RegisterParser(typeof(TxNamespaceParser)); Support for .NET 4 - Beginning with the 1.3.1 release of Spring.NET, initial - compatibility with the .NET 4 Common Language Runtime (CLR) is provided - via the .NET 4 Framework's support for In-Process Side-by-Side deployment - of .NET assemblies. This approach is typically refered to as - In-Proc SxS. + Beginning with the 1.3.2 release of Spring.NET, full compatibility + with the .NET 4 Common Language Runtime (CLR) is provided via a + comprehensive collection of Spring.NET compiled assemblies specifically + targeting the .NET 4 framework. Spring.NET 1.3.1 provided interim support + for .NET 4 via the approach typically refered to as In-Process + Side-by-Side or just In-Proc SxS. For more information on the In-Process Side-by-Side support introduced into the .NET 4 Framework, see the MSDN Magazine article - located here: - http://msdn.microsoft.com/en-us/magazine/ee819091.aspx - + located here: http://msdn.microsoft.com/en-us/magazine/ee819091.aspx - In-Prox SxS permits applicaitons that target - the .NET 4 Framework (and later) to reference and execute assemblies that - target earlier versions of the .NET Framework CLR transparently within the - same process space. By using this approach, Spring.NET ensures maximum - backwards-compatibility with prior .NET Framework releases. - - Subsequent releases of Spring.NET will be compiled to target the - .NET 4 Framework directly but during this transition period where - significant users are using Spring.NET to target pre-.NET 4 applications - while at the same time other users are beginning to target the .NET 4 - Framework CLR, supporting In-Proc SxS will permit - maximum flexibility for Spring.NET users. + Beginning with Spring.NET 1.3.2, this approach is no longer + necessary and fuill native support of .NET is now provided. diff --git a/doc/reference/src/overview.xml b/doc/reference/src/overview.xml index 67020a8d..10cbce67 100644 --- a/doc/reference/src/overview.xml +++ b/doc/reference/src/overview.xml @@ -163,9 +163,13 @@ effectively address common pain-points in ASP.NET such as data binding, validation, and ASP.NET page/control/module/provider configuration. - Spring.Web.Mvc - Use this module to integrate the functionality of - the Spring.Core and Spring.Aop modules into your ASP.NET MVC 2 - projects. + Spring.Web.Mvc - Use this module to + integrate the functionality of the Spring.Core and Spring.Aop modules into + your ASP.NET MVC 2 projects. + + Spring.Web.Mvc3 - Use this module to + integrate the functionality of the Spring.Core and Spring.Aop modules into + your ASP.NET MVC 3 projects. Spring.Web.Extensions - Use this module to raise the level of abstraction when writing ASP.NET web applications @@ -289,8 +293,8 @@ Distributed Computing - A calculator demonstrating remote service abstractions that let you - 'export' a plain CLR object (POCO) via .NET Remoting, Web Services, - or an EnterpriseService ServiceComponent. Corresponding client side + 'export' a plain CLR object (POCO) via .NET Remoting, Web Services, or + an EnterpriseService ServiceComponent. Corresponding client side proxies are also demonstrated. @@ -313,6 +317,18 @@ ASP.NET. + + ASP.NET MVC2 - Introductory example showing use of dependency + injection and container integration into the ASP.NET MVC2 + framework. + + + + ASP.NET MVC3 - Introductory example showing use of dependency + injection and container integration into the ASP.NET MVC3 + framework. + + Data Access - Demonstrates the ADO.NET framework showing how to simplify developing @@ -326,7 +342,7 @@ - AJAX : Demonstrates how to access a plain CLR object as a + AJAX : Demonstrates how to access a plain CLR object (POCO) as a webservice in client side JavaScript @@ -344,10 +360,10 @@ scheduling. - + + MSMQ - Application + demonstrating MSMQ helper classes. + NMS - Applicatoin @@ -356,6 +372,88 @@ + + Associated Spring.NET Projects + + There is a lot more to Spring.NET than just the Spring.NET project + itself. Spring.NET is enriched and empowered by a collection of supporting + projects that provide additional capabilities beyond those found in the + core Spring.NET Framework. Ranging from configuration-enhancing tools and + libraries to REST clients to support for additional messaging frameworks + and standards, the list of associated projects is growing rapidly and + includes some of the following: + + Spring.NET CodeConfig + + + + Spring.NET CodeConfig provides the ability + to configure a Spring container using standard .NET code instead of or + in addition to XML configuration. + + + + See http://springframework.net/codeconfig/ + for resources, downloads, and more information + + + + Spring.NET REST Client + + + + Spring.NET REST Client simplifies + communication with HTTP servers, and enforces RESTful principles. It + handles HTTP connections, leaving application code to provide URLs + (with possible template variables) and extract results. + + + + See http://springframework.net/rest/ + for resources, downloads, and more information + + + + Spring.NET AMQP + + + + Spring.NET AMQP supports the Spring + programming model with AMQP, especially but not limited to + RabbitMQ + + + + See http://springframework.net/amqp/ + for resources, downloads, and more information + + + + Spring.NET Visual Studio Add-In + + + + Spring.NET Visual Studio Add-In provides + intellisense assistance in authoring Spring XML configuration files in + VS.NET 2010 + + + + See http://springframework.net/vsaddin/ + for resources, downloads, and more information + + + + Adopters of Spring.NET are encouraged to explore these projects (and + more!) that help to round out the comprehensive Spring.NET experience and + provide additional capabilities beyond those of the core Spring.NET + Framework to increase developer efficiency and effectiveness. + + License Information diff --git a/doc/reference/src/vsnet.xml b/doc/reference/src/vsnet.xml index fb157850..5fbce702 100644 --- a/doc/reference/src/vsnet.xml +++ b/doc/reference/src/vsnet.xml @@ -53,9 +53,10 @@ 2002/2003 do not recognize the xsi:schemaLocation element. If you reference the Spring.NET XML schema as shown below, you can get intellisense and validation support while editing a Spring - configuration file in VS.NET 2005/2008. In order to get this functionality - in VS.NET 2002/2003 you will need to register the schema with VS.NET or - include the schema as part of your application project. + configuration file in VS.NET 2005/2008/2010. In order to get this + functionality in VS.NET 2002/2003 you will need to register the schema + with VS.NET or include the schema as part of your application + project. <?xml version="1.0" encoding="UTF-8"?> <objects xmlns="http://www.springframework.net" @@ -71,9 +72,10 @@ </objects> It is typically more convenient to install the schema in VS.NET, - even for VS.NET 2005/2008, as it makes the xml a little less verbose and - you don't need to keep copying the XSD file for each project you create. - For VS.NET 2003 the schema directory is + even for VS.NET 2005/2008/2010, as it makes the xml a little less verbose + and you don't need to keep copying the XSD file for each project you + create. The following table lists the schema directories for each version + of VS.NET: @@ -83,7 +85,8 @@ Visual Studio Version  - Directory to put Spring .XSD files  + Directory in which to place Spring .XSD + files  @@ -108,6 +111,13 @@ C:\Program Files\Microsoft Visual Studio 9.0\Xml\Schemas + + + VS.NET 2010 + + C:\Program Files\Microsoft Visual Studio + 10.0\Xml\Schemas +
@@ -186,6 +196,58 @@ embedded assembly resource, for serious development. + + Enhancing the XML Editing and Validation Experience using the + Spring.NET Visual Studio 2010 Extension + + If you are using VS.NET 2010, you are encouraged to install the + Spring.NET Visual Studio 2010 Extension. For more information and to + download the latest version of this 100% free tool, visit http://springframework.net/vsaddin/. + + The latest release of the Spring.NET Visual Studio 2010 Extension + provides Intellisensetm support in VS.NET 2010 + for the following areas of editing Spring XML configuration files: + + + + Type completion + + + + Property name completion + + + + Constructor argument name completion + + + + Property value completion for property of type 'Type', 'Enum' + and 'Boolean' + + + + In addition, this tool also provides for the following enhancements + to the Visual Studio 2010 XML Editor experience: + + + + Snippets integration (inline or by menu) + + + + Quickinfo tooltip for properties and types + + + + A brief screencast demonstrating the use of this tool can be viewed + here: http://maruxelo.free.fr/spring/index2.html + + + Solution Templates @@ -417,9 +479,9 @@ Spring provides API documentation that can be integrated within Visual Studio. There are two versions of the documentation, one for .NET - 1.1 and one for .NET 2.0/3.0. They differ only in the format applied and - the versions of VS.NET that supported. There is also standalone HTMLHELP - format API documentation. You will need to download the help file + 1.1 and one for .NET 2.0 and later. They differ only in the format applied + and the versions of VS.NET that supported. There is also standalone + HTMLHELP format API documentation. You will need to download the help file seperately from the distribution.