Add Encoding iso_2022_kr -> euc_kr
Throws ConfigurationErrorsException in case the file specified in configSource does not exist, to match with MS.NET's behavior.
Fixes a bug in ConfigurationElementCollection.
Extension to commit 17bd0c42c5646b4ab08342fbf8137e7c5bfc0738. This ensures that inheritedLimitIndex will always be >= 0.
changed namespace to MonoTests.* in order to be captured by TEST_HARNESS_FLAGS make option.
Added new test for CodeGenerator.GenerateFromCompileUnit. Verifies that CS1529 rule (imports first) is being obeyed by generator. Test signals, fixup required.
Made global namespace import being generated topmost, even before assembly attributes.
Better unit test case and cause description. Added references to CSharp generator and tests.
Added test to CSharp Code Generator with global namespace import and assembly attribute to render imports first. (Note: Adresses CS1529 ruling).
CSharpCodeGenerator now obeys CS1529 when rendering global namespace imports alongside with assembly attribute with GenerateFromCompileUnit.
Fixed space indents to tabs to adhere to Mono coding guidelines.
Provides basic support for ConfigurationElement.ElementInformation.IsPresent
Provides basic support for ConfigurationElement.ElementInformation.IsPresent.
Fixes a bug in WebConfigurationManager

Following is a step by step guide to create a testing project:

(1) Create an ASP.NET project in MonoDevelop
(2) Create a folder "base"
(3) Create two subfolders called "sub1" and "sub2" inside of "base"
(4) Create a web.config file in both sub folders "sub1" and "sub2" and enter the following code:

<configuration>
  	<appSettings>
		<add key="myText" value="src=sub1"/>
	</appSettings>
</configuration>

Set the "value=" element to the appropriate value of the corresponding sub folder.

(5) Enter the following code in Default.aspx.cs
public void Page_Load(object sender, EventArgs args)
{
	//c2.ConfigPath contains wrong path
	Configuration c1 = WebConfigurationManager.OpenWebConfiguration("~/base/sub1");
	Configuration c2 = WebConfigurationManager.OpenWebConfiguration("~/base/sub2");
			
	//myText_sub2 refers to the wrong AppSettings entry
	KeyValueConfigurationElement myText_sub1 = (KeyValueConfigurationElement)c1.AppSettings.Settings["myText"];
	KeyValueConfigurationElement myText_sub2 = (KeyValueConfigurationElement)c2.AppSettings.Settings["myText"];
}
Fix -O=shared support in mono_delegate_ctor ().
Xamarin-2938: Fix Screen.FromControl

We have to convert the location of the control to screen coordinates
so that we end up with the correct screen in a multi-monitor setup.
This patch fixes Screen.FromControl, Screen.FromHandle, and
Screen.GetWorkingArea.

Change-Id: I6c4fd65833d012e832d97d610c79abc792e57adf
Avoid passing a Module to the GetSigHelper methods (), which can happen if an ILBuilder is used from a dynamic method. Fixes #1900.
[System.ServiceModel] Speed up Bug652331_2Test test execution.

For reasons I currently can't explain, the Service1Client test type
appears to support having only one async operation "in flight" at a
time. As a result of this, calling multiple Async methods on the
Service1Client instance, as was done previously, would result in not
all of the event handlers being invoked, and the test timing out
after 60s instead of exiting quickly because all event handlers had
been raised.

I don't understand enough of WCF & this code to say why Service1Client
can have only one async operation in progress at once, but making this
change so that each async operation operates on a separate instance
speeds up the Bug652331_2Test execution from 60s to 5s.
[System.ServiceModel] Don't try to deserialize `void` messages.

Fixes: http://bugzilla.xamarin.com/show_bug.cgi?id=1164

The breakage reported in #1164 was caused by commit 106fdeb4, which
fixed bxc206. The problem is that in fixing bxc206, response messages
of a type having a MessageContractAttribute custom attribute were
changed to have a `void` return type, according to the
MessageDescription's Body.ReturnValue.Type property.

This fix is correct, in that it's what .NET does, but it broke XML
deserialization which expected the "actual" return type to exist, not
`void`.

Case in point: the added IService1.EndJSMGetDatabases() method will
have a MessageDescription with a Body.ReturnValue.Type=typeof(void).
The problem is that deserializing this message will fail:

	System.Runtime.Serialization.SerializationException: Deserializing
	type 'System.Void'. Expecting state 'EndElement'. Encountered state
	'Text' with name '' with namespace ''.

Obviously this is not good. ;-)

The fix is simple: don't use the MessageDescription's ReturnValue if
it's `typeof(void)`.

There are two added wrinkles:

 1. Writing a test case for the above.

 2. The test case broke with another error: a NRE within
    BaseMessagesFormatter.MessageObjectToParts(). This is because
    when ContractDescriptionGenerator.GetMessage() sets the
    ReturnValue for a response message, it doesn't set
    MessagePartDescription.MemberInfo.
    BaseMessagesFormatter.MessageObjectToParts(), meanwhile, was
    checking the ReturnValue's MemberInfo...which was null.

    Add a null check here so that the actual bug can be tested.
Fix Type.GetType () when an assembly resolver is used without a type resolver. Fixes #644.