Spring/spring-net
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

mods to docs to reflect 1.3.2-specific info and references to associated projects

Browse Source
This commit is contained in:
sbohlen
2011-07-28 22:38:12 +00:00
parent cb7db2c161
commit 295dc50dbb
3 changed files with 190 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
doc/reference/src/migration.xml
View File

@@ -152,31 +152,21 @@ NamespaceParserRegistry.RegisterParser(typeof(TxNamespaceParser));
<sect1>
<title>Support for .NET 4</title>
<para>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
<emphasis>In-Proc SxS</emphasis>.</para>
<para>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 <emphasis>In-Process
Side-by-Side</emphasis> or just <emphasis>In-Proc SxS</emphasis>.</para>
<note>
<para>For more information on the In-Process Side-by-Side support
introduced into the .NET 4 Framework, see the MSDN Magazine article
located here:
<uri>http://msdn.microsoft.com/en-us/magazine/ee819091.aspx</uri>
</para>
located here: <uri
ns6:href="http://msdn.microsoft.com/en-us/magazine/ee819091.aspx">http://msdn.microsoft.com/en-us/magazine/ee819091.aspx</uri></para>
</note>
<para><emphasis>In-Prox SxS</emphasis> 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.</para>
<para>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 <emphasis>In-Proc SxS</emphasis> will permit
maximum flexibility for Spring.NET users.</para>
<para>Beginning with Spring.NET 1.3.2, this approach is no longer
necessary and fuill native support of .NET is now provided.</para>
</sect1>
</chapter>

118
doc/reference/src/overview.xml
View File

@@ -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.</para>
<para>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.</para>
<para><link linkend="web-mvc">Spring.Web.Mvc</link> - Use this module to
integrate the functionality of the Spring.Core and Spring.Aop modules into
your ASP.NET MVC 2 projects.</para>
<para><link linkend="web-mvc3">Spring.Web.Mvc3</link> - Use this module to
integrate the functionality of the Spring.Core and Spring.Aop modules into
your ASP.NET MVC 3 projects.</para>
<para><link linkend="ajax">Spring.Web.Extensions</link> - Use this module
to raise the level of abstraction when writing ASP.NET web applications
@@ -289,8 +293,8 @@
<listitem>
<para><link linkend="remoting-quickstart">Distributed Computing</link>
- 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.</para>
</listitem>
@@ -313,6 +317,18 @@
ASP.NET.</para>
</listitem>
<listitem>
<para>ASP.NET MVC2 - Introductory example showing use of dependency
injection and container integration into the ASP.NET MVC2
framework.</para>
</listitem>
<listitem>
<para>ASP.NET MVC3 - Introductory example showing use of dependency
injection and container integration into the ASP.NET MVC3
framework.</para>
</listitem>
<listitem>
<para><link linkend="data-quickstart">Data Access</link> -
Demonstrates the ADO.NET framework showing how to simplify developing
@@ -326,7 +342,7 @@
</listitem>
<listitem>
<para>AJAX : Demonstrates how to access a plain CLR object as a
<para>AJAX : Demonstrates how to access a plain CLR object (POCO) as a
webservice in client side JavaScript</para>
</listitem>
@@ -344,10 +360,10 @@
scheduling.</para>
</listitem>
<!--<listitem>
<para><link lang="" linkend="msmq-quickstart">MSMQ</link> -
Application demonstrating MSMQ helper classes.</para>
</listitem>-->
<listitem>
<para><link linkend="msmq-quickstart">MSMQ</link> - Application
demonstrating MSMQ helper classes.</para>
</listitem>
<listitem>
<para><link linkend="nms-quickstart">NMS</link> - Applicatoin
@@ -356,6 +372,88 @@
</itemizedlist>
</sect1>
<sect1>
<title>Associated Spring.NET Projects</title>
<para>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:</para>
<para>Spring.NET CodeConfig</para>
<itemizedlist>
<listitem>
<para><emphasis>Spring.NET CodeConfig</emphasis> provides the ability
to configure a Spring container using standard .NET code instead of or
in addition to XML configuration.</para>
</listitem>
<listitem>
<para>See <uri
ns6:href="http://springframework.net/codeconfig/">http://springframework.net/codeconfig/</uri>
for resources, downloads, and more information</para>
</listitem>
</itemizedlist>
<para>Spring.NET REST Client</para>
<itemizedlist>
<listitem>
<para><emphasis>Spring.NET REST Client</emphasis> 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.</para>
</listitem>
<listitem>
<para>See <uri
ns6:href="http://springframework.net/rest/">http://springframework.net/rest/</uri>
for resources, downloads, and more information</para>
</listitem>
</itemizedlist>
<para>Spring.NET AMQP</para>
<itemizedlist>
<listitem>
<para><emphasis>Spring.NET AMQP</emphasis> supports the Spring
programming model with AMQP, especially but not limited to
RabbitMQ</para>
</listitem>
<listitem>
<para>See <uri
ns6:href="http://springframework.net/amqp/">http://springframework.net/amqp/</uri>
for resources, downloads, and more information</para>
</listitem>
</itemizedlist>
<para>Spring.NET Visual Studio Add-In</para>
<itemizedlist>
<listitem>
<para><emphasis>Spring.NET Visual Studio Add-In</emphasis> provides
intellisense assistance in authoring Spring XML configuration files in
VS.NET 2010</para>
</listitem>
<listitem>
<para>See <uri
ns6:href="http://springframework.net/amqp/">http://springframework.net/vsaddin/</uri>
for resources, downloads, and more information</para>
</listitem>
</itemizedlist>
<para>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.</para>
</sect1>
<sect1>
<title>License Information</title>

82
doc/reference/src/vsnet.xml
View File

@@ -53,9 +53,10 @@
2002/2003 do not recognize the <literal>xsi:schemaLocation</literal>
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.</para>
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.</para>
<programlisting language="myxml">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;objects xmlns="http://www.springframework.net"
@@ -71,9 +72,10 @@
&lt;/objects&gt;</programlisting>
<para>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</para>
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:</para>
<table>
<title></title>
@@ -83,7 +85,8 @@
<row>
<entry align="center">Visual Studio Version </entry>
<entry align="center">Directory to put Spring .XSD files </entry>
<entry align="center">Directory in which to place Spring .XSD
files </entry>
</row>
</thead>
@@ -108,6 +111,13 @@
<entry><literal>C:\Program Files\Microsoft Visual Studio
9.0\Xml\Schemas</literal></entry>
</row>
<row>
<entry>VS.NET 2010</entry>
<entry><literal>C:\Program Files\Microsoft Visual Studio
10.0\Xml\Schemas</literal></entry>
</row>
</tbody>
</tgroup>
</table>
@@ -186,6 +196,58 @@
embedded assembly resource, for serious development.</para>
</sect1>
<sect1>
<title>Enhancing the XML Editing and Validation Experience using the
Spring.NET Visual Studio 2010 Extension</title>
<para>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 <link
ns2:arcrole=""
ns2:href="http://springframework.net/vsaddin/">http://springframework.net/vsaddin/</link>.</para>
<para>The latest release of the Spring.NET Visual Studio 2010 Extension
provides Intellisense<superscript>tm</superscript> support in VS.NET 2010
for the following areas of editing Spring XML configuration files:</para>
<itemizedlist>
<listitem>
<para>Type completion</para>
</listitem>
<listitem>
<para>Property name completion</para>
</listitem>
<listitem>
<para>Constructor argument name completion</para>
</listitem>
<listitem>
<para>Property value completion for property of type 'Type', 'Enum'
and 'Boolean'</para>
</listitem>
</itemizedlist>
<para>In addition, this tool also provides for the following enhancements
to the Visual Studio 2010 XML Editor experience:</para>
<itemizedlist>
<listitem>
<para>Snippets integration (inline or by menu)</para>
</listitem>
<listitem>
<para>Quickinfo tooltip for properties and types</para>
</listitem>
</itemizedlist>
<para>A brief screencast demonstrating the use of this tool can be viewed
here: <link ns2:arcrole=""
ns2:href="http://maruxelo.free.fr/spring/index2.html">http://maruxelo.free.fr/spring/index2.html</link>
</para>
</sect1>
<sect1>
<title>Solution Templates</title>
@@ -417,9 +479,9 @@
<para>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.</para>
</sect1>
</chapter>