Remove the ASMX web service exporter from Spring.Web

BreakingChanges.txt

@@ -16,8 +16,7 @@ Changes (3.1 to 4.0)
    - Spring.Services: .NET Remoting exporters and factories, the ASMX web service client proxy
      (WebServiceProxyFactory), Enterprise Services (serviced components), WCF integration and
      the Windows service application host. These are .NET Framework-only technologies that
-     Microsoft has not carried forward to modern .NET. The ASMX web service exporter
-     (WebServiceExporter) is part of Spring.Web and remains.
+     Microsoft has not carried forward to modern .NET.
    - Spring.Messaging.Ems: TIBCO EMS integration. It needed TIBCO's non-redistributable
      TIBCO.EMS.dll and had no runnable tests.
    - Spring.Web.Extensions: ASP.NET AJAX integration (the JavaScript exporter), a .NET
@@ -31,6 +30,15 @@ Changes (3.1 to 4.0)
    4.0." The matching examples (Calculator, EmsQuickStart, WcfQuickStart and
    Web.Extensions.Example) were removed too.
 
+   Spring.Web's ASMX web service exporter (Spring.Web.Services.WebServiceExporter and
+   WebServiceHandlerFactory) is also gone, with no replacement. Remove any *.asmx handler
+   registration that points at Spring.Web.Services.WebServiceHandlerFactory from web.config,
+   together with the WebServiceExporter object definitions. Object definitions named after an
+   .asmx path (which the factory used to configure [WebService] classes) are no longer
+   consulted: ASP.NET compiles and instantiates the .asmx itself. To keep a service, write the
+   .asmx class by hand and resolve the object from the application context, or move to
+   WCF/CoreWCF or ASP.NET Core.
+
 5. Dependency floors were raised: Microsoft.Extensions.Logging.Abstractions 8.0.3,
    Microsoft.Bcl.HashCode 6.0.0, Microsoft.Win32.Registry 5.0.0, System.CodeDom 8.0.0,
    NHibernate 5.7.1, Quartz 3.22.9, and Microsoft.AspNet.Mvc and Microsoft.AspNet.WebApi.WebHost

examples/Spring/SpringAir/readme.txt

@@ -1,16 +1,7 @@
-For .NET 1.1,
-The VS.NET solution is SpringAir.2003.sln
-In order to be able to run SpringAir you will need to create 'SpringAir.2003' 
+The Visual Studio solution is SpringAir.sln.
+In order to be able to run SpringAir you will need to create a 'SpringAir.Web.2010'
 virtual directory using IIS Administrator and point it to the following directory :
- examples\Spring\SpringAir\src\SpringAir.Web.2003 
+ examples\Spring\SpringAir\src\SpringAir.Web.2010
 
-For .NET 2.0, 
-The VS.NET solution is SpringAir.2005.sln
-
-
-
-Set your startup project as SpringAir.Web  
+Set your startup project as SpringAir.Web.2010
 and the start page to .\Web\Home.aspx
-
-If you run .NET 2.0 first and then .NET 1.1, run the nant target 'clean-objs' to remove the object files before starting vs.net 2003
-Or do a clean build from vs.net 2005 before starting vs.net 2003.