www.go-mono.com/docs -> docs.go-mono.com

Fixes mono#360

archived/atksharp.md

@@ -8,5 +8,5 @@ redirect_from:
 AtkSharp
 ========
 
-Go to the [MonoDoc API page](http://go-mono.org/docs/index.aspx?tlink=5@N%3aAtk) for reference.
+Go to the [MonoDoc API page](http://docs.go-mono.com/index.aspx?tlink=5@N%3aAtk) for reference.
 

archived/cryptography.md

@@ -40,20 +40,20 @@ Namespace: **System.Security.Cryptography**
 
 **Status**
 
--   All classes are present. Most of them have (minimal) documentation in [monodoc](http://www.go-mono.com/docs/index.aspx).
+-   All classes are present. Most of them have (minimal) documentation in [monodoc](http://docs.go-mono.com/index.aspx).
 -   Most classes have their unit tests. Some tests like [SymmetricAlgorithmTest](http://anonsvn.mono-project.com/viewvc/trunk/mcs/class/corlib/Test/System.Security.Cryptography/SymmetricAlgorithmTest.cs?rev=9817&view=log) are generated by external tools.
 
  Namespace: **System.Security.Cryptography.X509Certificates**
 
 **Status**
 
--   X.509 certificates are parsed using 100% managed code (using the [Mono.Security.ASN1](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aMono.Security.ASN1) class).
+-   X.509 certificates are parsed using 100% managed code (using the [Mono.Security.ASN1](http://docs.go-mono.com/monodoc.ashx?link=T%3aMono.Security.ASN1) class).
 -   Software Publisher Certificates (SPC) used by Authenticode(tm) to sign assemblies are supported and **minimally** validated.
 -   Unit tests are generated from a set of existing certificates (about a dozen) each having different properties. Another set of certificates (more than 700) are used for a more complete test (but isn't part of the standard test suite for size and time consideration, i.e. a 7.5Mb C# source file).
 
  **Notes**
 
--   The classes under [Mono.Security.X509.\*](http://www.go-mono.com/docs/monodoc.ashx?link=N%3aMono.Security.X509) (in Mono.Security.dll assembly) are a much better alternative - and will continue to evolve to support the security tools.
+-   The classes under [Mono.Security.X509.\*](http://docs.go-mono.com/monodoc.ashx?link=N%3aMono.Security.X509) (in Mono.Security.dll assembly) are a much better alternative - and will continue to evolve to support the security tools.
 
 Assembly: System
 ----------------
@@ -170,9 +170,9 @@ Namespace: **Mono.Security.Cryptography**
 
 **Status**
 
--   A [RNGCryptoServiceProvider](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aMono.Security.Cryptography.RNGCryptoServiceProvider) built on top of CryptoAPI.
+-   A [RNGCryptoServiceProvider](http://docs.go-mono.com/monodoc.ashx?link=T%3aMono.Security.Cryptography.RNGCryptoServiceProvider) built on top of CryptoAPI.
 -   Wrapper classes for unmanaged versions of hash algorithms: MD2, MD4, MD5 and SHA1 are supported. **Note**: some algorithms shouldn't be used in new design because they aren't considered safe for some usage - this includes MD2, MD4, MD5 and SHA1. They are included to preserve interoperability with older applications (e.g. some old, but still valid, X.509 certificates use MD2, MD4 is required for NTLM authentication ...).
--   Classes have minimal documentation available in [monodoc](http://www.go-mono.com/docs/index.aspx).
+-   Classes have minimal documentation available in [monodoc](http://docs.go-mono.com/index.aspx).
 
 **TODO**
 

archived/gconftutorial.md

@@ -73,7 +73,7 @@ Most nontrivial applications will need to store user preferences. Traditionally,
 
 What are we going to do in this tutorial?:
 
--   Create a [checkbox](http://www.go-mono.com/docs/monodoc.ashx?tlink=6@ecma%3a877%23CheckButton%2f) and an [editbox](http://www.go-mono.com/docs/monodoc.ashx?tlink=6@ecma%3a980%23Entry%2f)
+-   Create a [checkbox](http://docs.go-mono.com/monodoc.ashx?tlink=6@ecma%3a877%23CheckButton%2f) and an [editbox](http://docs.go-mono.com/monodoc.ashx?tlink=6@ecma%3a980%23Entry%2f)
 -   Link them with [GConf](http://www.gnome.org/projects/gconf/)
 -   Test live notification with [GConf-Editor](http://cvs.gnome.org/viewcvs/gconf-editor/)
 
@@ -272,7 +272,7 @@ References
 ==========
 
 -   [GConf Web Site](http://www.gnome.org/projects/gconf/)
--   [GConf# Documentation](http://www.go-mono.com/docs/index.aspx?link=N:GConf)
+-   [GConf# Documentation](http://docs.go-mono.com/index.aspx?link=N:GConf)
 -   [GNOME HIG](http://developer.gnome.org/projects/gup/hig/)
 
 

archived/gtksharper.md

@@ -20,7 +20,7 @@ Gtk# is a Graphical User Interface Toolkit for mono and .Net. The project binds
 References
 ----------
 
--   [Online API Documentation](http://www.go-mono.com/docs/monodoc.ashx?tlink=root:/classlib-gnome)
+-   [Online API Documentation](http://docs.go-mono.com/monodoc.ashx?tlink=root:/classlib-gnome)
 -   [What's New?](/GtkSharpNewInVersion2x)
 -   [Release Plans](/GtkSharpPlan)
 -   [Articles and Tutorials](/Articles) on Gtk#.

archived/monomac_documentation_api_design.md

@@ -126,7 +126,7 @@ MonoMac mirrors in C# the hierarchy of classes from Objective-C. For example, th
 
 Although this namespace provides bindings for the underlying Objective-C Foundation types, in a few cases we have mapped the underlying types to .NET types. For example:
 
-1.  Instead of dealing with [NSString](http://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Classes/NSString_Class/Reference/NSString.html#//apple_ref/doc/uid/TP40003744) and [NSArray](http://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Classes/NSArray_Class/NSArray.html#//apple_ref/doc/uid/TP40003620) the runtime instead exposes these as C# [string](http://www.go-mono.com/docs/index.aspx?link=T:System.String) and strongly typed [" array](http://www.go-mono.com/docs/index.aspx?link=T:System.Array)s throughout the API.
+1.  Instead of dealing with [NSString](http://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Classes/NSString_Class/Reference/NSString.html#//apple_ref/doc/uid/TP40003744) and [NSArray](http://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Classes/NSArray_Class/NSArray.html#//apple_ref/doc/uid/TP40003620) the runtime instead exposes these as C# [string](http://docs.go-mono.com/index.aspx?link=T:System.String) and strongly typed [" array](http://docs.go-mono.com/index.aspx?link=T:System.Array)s throughout the API.
 2.  Various helper APIs are exposed here to allow developers to bind third party Objective-C APIs, other OS X APIs or APIs that are not currently bound by MonoMac.
 
 For more details on binding APIs see the [MonoMac Binding Generator](/MonoMac/Documentation/Binding_New_Objective-C_Types) section.

archived/monomacnew.md

@@ -12,7 +12,7 @@ MonoMacNew
 
 Getting Started
 
-[API Documentation](http://www.go-mono.com/docs/N:MonoMac)
+[API Documentation](http://docs.go-mono.com/N:MonoMac)
 
 \<div style="clear: both;"/\>
 

archived/monotouch_api.md

@@ -67,43 +67,43 @@ Major Namespaces
 MonoTouch.ObjCRuntime
 ---------------------
 
-The [MonoTouch.ObjCRuntime](http://www.go-mono.com/docs/index.aspx?tlink=20@N:MonoTouch.ObjCRuntime) namespace allows developers to bridge the worlds between C# and Objective-C. This is a new binding designed specifically for the iPhone based on the experience from Cocoa# and Gtk#.
+The [MonoTouch.ObjCRuntime](http://docs.go-mono.com/index.aspx?tlink=20@N:MonoTouch.ObjCRuntime) namespace allows developers to bridge the worlds between C# and Objective-C. This is a new binding designed specifically for the iPhone based on the experience from Cocoa# and Gtk#.
 
 MonoTouch.Foundation
 --------------------
 
-The [MonoTouch.Foundation](http://www.go-mono.com/docs/index.aspx?link=N:MonoTouch.Foundation) namespace provides the basic data types designed to interoperate with the Objective-C Foundation framework that is part of the iPhone and it is the base for object oriented programming in Objective-C.
+The [MonoTouch.Foundation](http://docs.go-mono.com/index.aspx?link=N:MonoTouch.Foundation) namespace provides the basic data types designed to interoperate with the Objective-C Foundation framework that is part of the iPhone and it is the base for object oriented programming in Objective-C.
 
-MonoTouch mirrors in C# the hierarchy of classes from Objective-C. For example, the Objective-C base class [NSObject](http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/Foundation/Classes/NSObject_Class/Reference/Reference.html) is usable from C# via [MonoTouch.Foundation.NSObject](http://www.go-mono.com/docs/index.aspx?link=T:MonoTouch.Foundation.NSObject).
+MonoTouch mirrors in C# the hierarchy of classes from Objective-C. For example, the Objective-C base class [NSObject](http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/Foundation/Classes/NSObject_Class/Reference/Reference.html) is usable from C# via [MonoTouch.Foundation.NSObject](http://docs.go-mono.com/index.aspx?link=T:MonoTouch.Foundation.NSObject).
 
 Although this namespace provides bindings for the underlying Objective-C Foundation types, in a few cases we have mapped the underlying types to .NET types. For example:
 
--   Instead of dealing with [NSString](http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/Foundation/Classes/NSString_Class/Reference/NSString.html) and [NSArray](http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/Foundation/Classes/NSArray_Class/Reference/Reference.html) the runtime instead exposes these as C# [string](http://www.go-mono.com/docs/index.aspx?link=T:System.String)s and strongly typed [array](http://www.go-mono.com/docs/index.aspx?link=T:System.Array)s throughout the API.
+-   Instead of dealing with [NSString](http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/Foundation/Classes/NSString_Class/Reference/NSString.html) and [NSArray](http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/Foundation/Classes/NSArray_Class/Reference/Reference.html) the runtime instead exposes these as C# [string](http://docs.go-mono.com/index.aspx?link=T:System.String)s and strongly typed [array](http://docs.go-mono.com/index.aspx?link=T:System.Array)s throughout the API.
 -   Various helper APIs are exposed here to allow developers to bind third party Objective-C APIs, other iPhone APIs or APIs that are not currently bound by MonoTouch.
 
 For more details on binding APIs see the MonoTouch Binding Generator section.
 
 ### NSObject
 
-The [NSObject](http://www.go-mono.com/docs/index.aspx?link=T:MonoTouch.Foundation.NSObject) type is the foundation for all the Objective-C bindings.
+The [NSObject](http://docs.go-mono.com/index.aspx?link=T:MonoTouch.Foundation.NSObject) type is the foundation for all the Objective-C bindings.
 
-While Mono will provide garbage collection for all of your objects, we made the `MonoTouch.Foundation.NSObject` implement the [http:/monodoc/T:System.IDisposable System.IDisposable] interface. If your type needs to perform deterministic finalization, override the [NSObject.Dispose(bool) method](http://www.go-mono.com/docs/index.aspx?link=M:MonoTouch.Foundation.NSObject.Dispose(System.Boolean)).
+While Mono will provide garbage collection for all of your objects, we made the `MonoTouch.Foundation.NSObject` implement the [http:/monodoc/T:System.IDisposable System.IDisposable] interface. If your type needs to perform deterministic finalization, override the [NSObject.Dispose(bool) method](http://docs.go-mono.com/index.aspx?link=M:MonoTouch.Foundation.NSObject.Dispose(System.Boolean)).
 
 MonoTouch.UIKit
 ---------------
 
-The [MonoTouch.UIKit](http://www.go-mono.com/docs/index.aspx?link=N:MonoTouch.UIKit) namespace contains a 1 to 1 mapping to all of the UI components that make up CocoaTouch in the form of C# classes. The API has been modified to follow the conventions used in the C# language.
+The [MonoTouch.UIKit](http://docs.go-mono.com/index.aspx?link=N:MonoTouch.UIKit) namespace contains a 1 to 1 mapping to all of the UI components that make up CocoaTouch in the form of C# classes. The API has been modified to follow the conventions used in the C# language.
 
 C# delegates are provided for common operations. See the [delegates](#delegates) section for more information.
 
 OpenGLES
 --------
 
-For OpenGLES we distribute a [modified version](http://www.go-mono.com/docs/index.aspx?link=N:OpenTK) of the [OpenTK](http://www.opentk.com) API, an object-oriented binding to OpenGL that has been modified to use CoreGraphics data types and structures as well as only exposing the functionality that is available on the iPhone.
+For OpenGLES we distribute a [modified version](http://docs.go-mono.com/index.aspx?link=N:OpenTK) of the [OpenTK](http://www.opentk.com) API, an object-oriented binding to OpenGL that has been modified to use CoreGraphics data types and structures as well as only exposing the functionality that is available on the iPhone.
 
-OpenGLES 1.1 functionality is available through the [ES](http://www.go-mono.com/docs/index.aspx?link=T:OpenTK.Graphics.ES11.ES) type.
+OpenGLES 1.1 functionality is available through the [ES](http://docs.go-mono.com/index.aspx?link=T:OpenTK.Graphics.ES11.ES) type.
 
-OpenGLES 2.0 functionality is available through the [ES](http://www.go-mono.com/docs/index.aspx?link=T:OpenTK.Graphics.ES20.ES) type.
+OpenGLES 2.0 functionality is available through the [ES](http://docs.go-mono.com/index.aspx?link=T:OpenTK.Graphics.ES20.ES) type.
 
 Binding Design
 ==============
@@ -150,9 +150,9 @@ For example, consider the [UIWebView](http://developer.apple.com/iphone/library/
 
 For many types, MonoTouch will automatically create an appropriate delegate which will forward the UIWebViewDelegate calls onto C# events. For UIWebView:
 
--   The [webViewDidStartLoad](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIWebViewDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIWebViewDelegate/webViewDidStartLoad:) method is mapped to the [UIWebView.LoadStarted](http://www.go-mono.com/docs/index.aspx?link=E:MonoTouch.UIKit.UIWebView.LoadStarted) event.
--   The [webViewDidFinishLoad](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIWebViewDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIWebViewDelegate/webViewDidFinishLoad:) method is mapped to the [UIWebView.LoadFinished](http://www.go-mono.com/docs/index.aspx?link=E:MonoTouch.UIKit.UIWebView.LoadFinished) event.
--   The [webView:didFailLoadWithError](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIWebViewDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIWebViewDelegate/webView:didFailLoadWithError:) method is mapped to the [UIWebView.LoadError](http://www.go-mono.com/docs/index.aspx?link=E:MonoTouch.UIKit.UIWebView.LoadError) event.
+-   The [webViewDidStartLoad](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIWebViewDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIWebViewDelegate/webViewDidStartLoad:) method is mapped to the [UIWebView.LoadStarted](http://docs.go-mono.com/index.aspx?link=E:MonoTouch.UIKit.UIWebView.LoadStarted) event.
+-   The [webViewDidFinishLoad](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIWebViewDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIWebViewDelegate/webViewDidFinishLoad:) method is mapped to the [UIWebView.LoadFinished](http://docs.go-mono.com/index.aspx?link=E:MonoTouch.UIKit.UIWebView.LoadFinished) event.
+-   The [webView:didFailLoadWithError](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIWebViewDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIWebViewDelegate/webView:didFailLoadWithError:) method is mapped to the [UIWebView.LoadError](http://docs.go-mono.com/index.aspx?link=E:MonoTouch.UIKit.UIWebView.LoadError) event.
 
 For example, this simple program times the time it takes to load a web view:
 
@@ -165,7 +165,7 @@ web.LoadFinished += (o, e) => endTime = DateTime.Now;
 
 ### Strongly typed via a Delegate property
 
-If you would prefer not to use events, you can provide your own [UIWebViewDelegate](http://www.go-mono.com/docs/index.aspx?link=T:MonoTouch.UIKit.UIWebViewDelegate) subclass and assign it to the [UIWebView.Delegate](http://www.go-mono.com/docs/index.aspx?link=P:MonoTouch.UIKit.UIWebView.Delegate) property. Once UIWebView.Delegate has been assigned, the UIWebView event dispatch mechanism will no longer function, and the UIWebViewDelegate methods will be invoked when the corresponding events occur.
+If you would prefer not to use events, you can provide your own [UIWebViewDelegate](http://docs.go-mono.com/index.aspx?link=T:MonoTouch.UIKit.UIWebViewDelegate) subclass and assign it to the [UIWebView.Delegate](http://docs.go-mono.com/index.aspx?link=P:MonoTouch.UIKit.UIWebView.Delegate) property. Once UIWebView.Delegate has been assigned, the UIWebView event dispatch mechanism will no longer function, and the UIWebViewDelegate methods will be invoked when the corresponding events occur.
 
 For example, this simple type records the time it takes to load a web view:
 
@@ -194,15 +194,15 @@ The above is used in code like this:
 
 The above will create a UIWebViewer and it will instruct it to send messages to an instance of Notifier, a class that we created to respond to messages.
 
-This pattern is also used to control behavior for certain controls, for example in the UIWebView case, the [UIWebView.ShouldStartLoad](http://www.go-mono.com/docs/index.aspx?link=P:MonoTouch.UIKit.UIWebView.ShouldStartLoad) property allows the UIWebView instance to control whether the UIWebView will load a page or not.
+This pattern is also used to control behavior for certain controls, for example in the UIWebView case, the [UIWebView.ShouldStartLoad](http://docs.go-mono.com/index.aspx?link=P:MonoTouch.UIKit.UIWebView.ShouldStartLoad) property allows the UIWebView instance to control whether the UIWebView will load a page or not.
 
-The pattern is also used to provide the data on demand for a few controls. For example the [UITableView](http://www.go-mono.com/docs/index.aspx?link=T:MonoTouch.UIKit.UITableView) control is a powerful table rendering control and both the look and the contents are driven by an instace of a [UITableViewDataSource](http://www.go-mono.com/docs/index.aspx?link=T:MonoTouch.UIKit.UITableViewDataSource).
+The pattern is also used to provide the data on demand for a few controls. For example the [UITableView](http://docs.go-mono.com/index.aspx?link=T:MonoTouch.UIKit.UITableView) control is a powerful table rendering control and both the look and the contents are driven by an instace of a [UITableViewDataSource](http://docs.go-mono.com/index.aspx?link=T:MonoTouch.UIKit.UITableViewDataSource).
 
 ### Loosely typed via the WeakDelegate property
 
 In addition to the strongly typed property, there is also a weak typed delegate that allows the developer to bind things differently if desired. Everywhere where a strongly typed `Delegate` property is exposed in MonoTouch's binding a corresponding `WeakDelegate` property is also exposed.
 
-When using the `WeakDelegate` you are responsible for properly decorating your class using the [Export](http://www.go-mono.com/docs/index.aspx?link=T:MonoTouch.Foundation.ExportAttribute) attribute to specify the selector. For example:
+When using the `WeakDelegate` you are responsible for properly decorating your class using the [Export](http://docs.go-mono.com/index.aspx?link=T:MonoTouch.Foundation.ExportAttribute) attribute to specify the selector. For example:
 
 ``` csharp
 class Notifier : NSObject  {