- 15 10月, 2010 5 次提交
-
-
由 Atsushi Eno 提交于
-
由 Geoff Norton 提交于
Android's fork() function does not properly update the pthread_internal_t->threadid variable to point to the tid of the fork()'d thread, and instead still points to the pid of zygote. As a result we need to track the android tid's manually since gettid() is sane, and use an alternate to pthread_kill on android Additionally, disable sgen support on android until the same work has been done there r: kumpera, vargaz
-
由 Rodrigo Kumpera 提交于
* class.c (mono_class_is_open_constructed_type): Treat generic type definition as an open type too. All code that checks is_open does to make sure the generic instance is realizable.
-
由 Rodrigo Kumpera 提交于
* marshal.c (mono_marshal_get_castclass_with_cache): Use the right parameter for the cache. * marshal.c (mono_marshal_get_isinst_with_cache): Use the right parameter for the cache. In the negative case store the obj_vtable and not the cache address.
-
由 Atsushi Eno 提交于
-
- 14 10月, 2010 14 次提交
-
-
由 Atsushi Eno 提交于
SecurityTokenParameters.InitializeSecurityTokenRequirement() needs to become protected internal, so changed all overrides as well. Some implementation in WindowsStreamSecurityBindingElement is needed only for NetTcpBinding implementation. Had to disable a test in SymmetricSecurityBindingElement that depended on OneWay support (which is not yet done).
-
由 Jb Evain 提交于
-
由 Jb Evain 提交于
-
由 Atsushi Eno 提交于
-
由 Marek Safar 提交于
-
由 Marek Safar 提交于
-
由 Marek Safar 提交于
-
由 Ankit Jain 提交于
Add GetFrameworkPaths and PrepareForBuild as dependencies for the ResolveAssemblyReferences target. This is required when it is invoked directly from MD. Patch from Michael Hutchinson (mhutchinson@novell.com).
-
由 Atsushi Eno 提交于
-
由 Atsushi Eno 提交于
-
由 Gonzalo Paniagua Javier 提交于
-Fix validation of display name and email. -Cache user, host and ToString() values. -Fix Equals and GetHashCode. Fixes bug 645871.
-
由 Rodrigo Kumpera 提交于
* verify.c (is_valid_generic_instantiation): If the generic instantiation is open, GTDs can appear in mutual types.
-
由 Rodrigo Kumpera 提交于
* verify.c (mono_verifier_verify_class): The generic instance over its parent generic arguments will end up extending a GTD. The check against not extending a GTD is only valid for not generic instance types.
-
由 Sebastien Pouliot 提交于
* SocketAsyncEventArgs.cs: Remove TODO on SocketClientAccessPolicy Protocol property
-
- 13 10月, 2010 14 次提交
-
-
由 Marek Safar 提交于
-
由 Marek Safar 提交于
-
由 Marek Safar 提交于
-
由 Marek Safar 提交于
-
由 Jb Evain 提交于
This fixes #645765.
-
由 Rolf Bjarne Kvinge 提交于
-
由 Ankit Jain 提交于
All targets that get built are tracked by the engine, to avoid unnecessary builds of targets. This should be reset on engine.Build, unless it is explicitly requested *not to* reset it, via BuildFlags.
-
由 Ankit Jain 提交于
MSBuild hosts like monodevelop, which use the same logger for multiple builds, get errors/warnings from older builds. So, reset them whenever the BuildFinished event is raised. ILogger.Shutdown () is invoked when the host is about to quit, according to msdn, so can't use that.
-
由 Jonathan Pryor 提交于
The problem is that Android only exposes Java APIs for ~everything of consequence, including/especially X509 Certificate validation. Since we want Mono-based HTTPS support to use the underlying platform certificates, this requires some amount of Java-using glue. However, we don't want to pull in a ton of Java glue into System.dll (bleh!), so we'll instead place the glue into Mono.Android.dll's Android.Runtime.AndroidEnvironment.TrustEvaluateSsl(), and instead create a delegate which will invoke TrustEvaluateSsl() when needed.
-
由 Gonzalo Paniagua Javier 提交于
When disposing a socket that has more than one asynchronous read/write pending, one of the callbacks could call DisposeAllOnClose() while another one is waiting on the lock. Once the lock is acquired, queue.Count will be 0 and Dequeue would fail. This if fixed now. Fixes bug #645675.
-
由 Gonzalo Paniagua Javier 提交于
-
由 Jb Evain 提交于
-
由 Marek Safar 提交于
-
由 Jb Evain 提交于
The Expression Tree interpreter was previously limited to lambda expression for either an Action or a Func delegate. This fix removes this limitation. Fixes #645770.
-
- 12 10月, 2010 7 次提交
-
-
由 Sebastien Pouliot 提交于
-
由 Sebastien Pouliot 提交于
* Makefile: Compile tests with TEST defined (to include System.Web.Util. MachineKeySectionUtils unit tests) * System.Web.dll.sources: Move MachineKeySectionUtils.cs from System. Web.Configuration_2.0 to System.Web.Util * System.Web_test.dll.sources: Move MachineKeySectionUtilsTest.cs from System.Web.Configuration_2.0 to System.Web.Util * System.Web.Configuration_2.0/MachineKeySection.cs: Adjust using clauses. Uncomment some code. Fix TripleDES versus 3DES for Validation under NET_4_0. Remove 'private' on fields/methods. * System.Web.Handlers/AssemblyResourceLoader.cs: Adjust using clauses * System.Web.Security/MembershipHelper.cs: Adjust using clauses * System.Web.Security/RolePrincipal.cs: Adjust using clauses * System.Web.SessionState_2.0/SessionId.cs: Adjust using clauses * System.Web.UI/LosFormatter.cs: Adjust using clauses. * System.Web.Util/MachineKeySectionUtils.cs: Moved from System.Web. Configuration_2.0. Rename namespace and remove 'internal' on type declaration * Test/System.Web.Util/MachineKeySectionUtilsTest.cs: Moved from Test/ System.Web.Configuration/MachineKeySectionTest.cs. Add test case for TripleDES versus 3DES
-
由 Sebastien Pouliot 提交于
* System.Web.Configuration_2.0/MachineKeyRegistryStorage.cs: Remove key length check and generic key generation. * System.Web.Configuration_2.0/MachineKeySection.cs: Add support for 4.0 ValidationAlgorithm and the use of custom algorithms (validation and decryption). Allow the use of any, valid, key length (based on the algorithm). Let each algorithm creates its own key (e.g. special needs, default length...) * System.Web.Configuration_2.0/MachineKeySectionUtils.cs: Remove key generation (from random) code and 192bits key length hack (won't work with custom algorithms). Add support for new (4.0) algorithms, including custom ones. Provide uniform/shared code to Encrypt/Decrypt, Sign/Verify and EncryptSign/VerifyDecrypt using MachineKeySection data. * System.Web.Configuration_2.0/MachineKeyValidation.cs: Add new (4.0) values. * System.Web.Configuration_2.0/MachineKeyValidationConverter.cs: Add support for new (4.0) algorithms. * System.Web.Handlers/AssemblyResourceLoader.cs: Use the new common cryptographic code and base64 the encrypted data. * System.Web.Security/FormsAuthentication.cs: Use the new common cryptographic code and base64 the signed and/or encrypted data. * System.Web.Security/MembershipHelper.cs: Use the new common cryptographic code - this should be 100% compatible with existing data. * System.Web.Security/RolePrincipal.cs: Use the new common cryptographic code. * System.Web.Security/SqliteMembershipProvider.cs: Adapt code for internal API change. * System.Web.UI/LosFormatter.cs: Adapt code for internal API change. Fix some small behaviro changes wrt NET_4_0 * System.Web.UI/ObjectStateFormatter.cs: Use the new common cryptographic code. * System.Web.UI/Page.cs: Remove code that is now unneeded (with the new common cryptogrraphic code). * System.Web.Configuration_2.0/MachineKeyCompatibilityMode.cs: New. * Test/System.Web.Configuration/MachineKeyValidationConverterTest.cs: Add more, mostly 4.0, test cases. * Test/System.Web.Security/FormsAuthenticationTest.cs: Add test case to ensure HashPasswordForStoringInConfigFile is not case sensitive. * Test/System.Web.UI/LosFormatterTest.cs: Add some rountrip test cases with the different ctors
-
由 Paolo Molaro 提交于
* console-io.h, console-null.c, console-unix.c, console-win32.c, gc.c: instead of executing tons of managed code in signal context, we wake up the finalizer thread and any complex console-specific code will be handled there. This can cause a (usually small) delay, but it's much better than deadlocking.
-
由 Paolo Molaro 提交于
* loader.c: we don't search the current directory anymore for shared libraries referenced in DllImport attributes, as it has a slight security risk. We search in the same directory where the referencing image was loaded from, instead. Fixes bug# 641915.
-
由 Marek Habersack 提交于
-
由 Zoltan Varga 提交于
-