[Mono-dev] ZipArchiveEntry - issue with reopening entries
I've been trying to use the latest version of the Open XML SDK with Mono
4.3.3 (built off the master branch), and as described at
https://github.com/OfficeDev/Open-XML-SDK/issues/74 I'm running into a
problem that looks to be a Mono issue.
I think it essentially reduces down to the situation that the code
using (ZipArchive archive = new ZipArchive(input, ZipArchiveMode.Update))
{
ZipArchiveEntry selectorEntry = archive.GetEntry("readme.txt");
using (Stream temp = selectorEntry.Open())
{
Console.WriteLine("Open1");
}
using (Stream temp = selectorEntry.Open())
{
Console.WriteLine("Open2");
}
}
Works on MS .NET4.5 but on Mono throws an exception on the second open,
because it thinks the stream is already open although it has actually been
closed.
I'm wondering, should the
if (openStream != null && Archive.Mode == ZipArchiveMode.Update)
throw new IOException("The entry is already currently open
for writing.");
In ZipArchiveEntry.Open() be a bit more clever, and do something like check
if the stream has been disposed, even though it's non-null?
--
View this message in context:
http://mono.1490590.n4.nabble.com/ZipArchiveEntry-issue-with-reopening-entries-tp4667333.html
Sent from the Mono - Dev mailing list archive at Nabble.com.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Building 4.2 on OS X
Speaking of a 64bit OSX build, I see that a universal build has appeared at http://download.mono-project.com/archive/4.2.1/macos-10-universal/ Getting closer to an official release now :-) -- View this message in context: http://mono.1490590.n4.nabble.com/Building-4-2-on-OS-X-tp4666924p4666951.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Building 4.2 on OS X
I've built the 4.2.1.91 tarball successfully on 64bit OSX, though that was using a downloaded 32bit 4.2 build as the compiler. fwiw, when I tried building the latest Git master recently I got some failures due to missing definitions for the new TLS stuff, and it worked after cleaning everything out and adding $PREFIX/bin to the path (must have been trying to build against the old assemblies i guess). -- View this message in context: http://mono.1490590.n4.nabble.com/Building-4-2-on-OS-X-tp4666924p4666925.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] 32 bit mono
I'm interested to know if there are any time frames for this as well - I'm currently working on a project that needs to use a 64bit Mono on OSX, and it would be nice to have an idea when there might be an official release. Thanks, Richard Webb -- View this message in context: http://mono.1490590.n4.nabble.com/32-bit-mono-tp4666741p4666745.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] System.DirectoryServices.DirectoryEntry.ObjectSecurity property
Right, first change in :-) Are we looking at 4.3.0 to get this sort of addition into a release build, or is there still a possibility of changes getting into 4.2.(0/1)? I'm currently doing OSX dev with a local 64bit build of 4.2.1 and I can patch that if i need to, but it would be useful to know for reference. Thanks, Richard Webb -- View this message in context: http://mono.1490590.n4.nabble.com/System-DirectoryServices-DirectoryEntry-ObjectSecurity-property-tp4666718p4666734.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] System.DirectoryServices.DirectoryEntry.ObjectSecurity property
Ok. Is it worth me doing a pull request to add a stub implementation? (Some of the other props there just throw NotImplementedException on call, so I can do the same). I've also found another issue with the ActiveDirectoryObjectNotFoundException class apparently not being present, so I may need to do something with that as well. -- View this message in context: http://mono.1490590.n4.nabble.com/System-DirectoryServices-DirectoryEntry-ObjectSecurity-property-tp4666718p4666723.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Having a problem with signed XML files
Hi all, I have a Windows product that uses signed XML files which I'm trying to get running under Mono on OSX, and I'm running into a verification failure at runtime. I'm pretty hazy about how the internals of this stuff works, but debugging through it, the issue seems to be occurring in System.Security.Cryptography.Xml.SignedXml.GetReferenceHash(), due to the call to FixupNamespaceNodes added @ https://github.com/mono/mono/commit/b2f49647aaa8a62b90c21db8211cbe15723dd132#diff-92a9806a06b3715be52b2894cb7546d6R326 Which takes the XML in the form And copies the xmlns attributes on the ArrayOfString node onto the Object node. If I skip over the FixupNamespaceNodes call, it all appears to work. Anyone have any thoughts on how to proceed with this? The 'I haven't solved the puzzle on why it is needed though.' comment on the commit doesn't fill me with confidence :-( Thanks, Richard Webb -- View this message in context: http://mono.1490590.n4.nabble.com/Having-a-problem-with-signed-XML-files-tp4666719.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] System.DirectoryServices.DirectoryEntry.ObjectSecurity property
Hi all When trying to build some Windows .Net libs in Mono (on OSX in this case, but I don't think that matters), I got a compile error due to the 'ObjectSecurity' property of System.DirectoryServices.DirectoryEntry being missing. I was wondering, is there a reason for that, or is it an oversight? As it happens I don't actually need to use the returned object on the Mono build at the moment, but the compile error is annoying. Thanks, Richard Webb -- View this message in context: http://mono.1490590.n4.nabble.com/System-DirectoryServices-DirectoryEntry-ObjectSecurity-property-tp4666718.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
