PackageExplorer Work Item Rss Feed

Created Issue: Validate crashes if document contains altChunk

robertk — Mon, 25 May 2009 19:32:10 GMT

Apparently it attempts to treat it as an XML document, while it can be several types of document: html, xml or in my case: docx.

This is the exception:
Data at the root level is invalid. Line 1, position 1.

at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.Load(Stream inStream)
at PackageExplorer.AddIns.ValidationInspector.DefaultValidationService.ValidatePart(DocumentPart documentPart, XmlSchemaSet schemas) in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer.AddIns.ValidationInspector\DefaultValidationService.cs:line 84
at PackageExplorer.AddIns.ValidationInspector.DefaultValidationService.Validate(DocumentPart documentPart) in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer.AddIns.ValidationInspector\DefaultValidationService.cs:line 62
at PackageExplorer.AddIns.ValidationInspector.ValidateDocumentPartCommand.Execute() in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer.AddIns.ValidationInspector\ValidateDocumentPartCommand.cs:line 39
at PackageExplorer.UI.Menu.ToolStripMenuItem.OnClick(EventArgs e) in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer\UI\Menu\ToolStripMenuItem.cs:line 62
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

COMMENTED FEATURE: Open Workbook Protected Excel 2007 Files

jlundstocholm — Thu, 08 Nov 2007 21:44:00 GMT

Hi,

Im interested if its possible to get an Excel 2007 with Workbook Protection turned on to be viewd in the explorer.

If workshhet protection is the infoamrion is in the XML but for Workbook protection the file seems to get encrypted. Has anyone anyinformation on this?

Would like to know of a way to provide the password for it to be decrypted into a state to unzip the file again for the XML.

Many Thanks

Gary Howlett
Comments: ** Comment from web user: jlundstocholm **

Just to clarify:

The encryption technique is actually open - it is just not documented very well and by design left outside of the spec, A password-protected OOXML-file is saved as (when using MS Office) a Compound File and encrypted using the MS Office Crypto API. If you are using the Packaging API in System.IO.Packaging (.Net 3.0) you can use the System.IO.Packaging.EncryptedPackageEnvelope class to manipulate the password protected files.

COMMENTED FEATURE: Hangs up when moving the splitter

Wouterv — Fri, 10 Aug 2007 16:45:10 GMT

Steps to re-produce:
1. Start the app.
2. View->Document inspector
3. Drag and move the splitter to left. The splitter which is at the right edge of the "document inspector" pane.
4. Repeat the #3 (~4-6 times usualy enough)

Actual result:
The apps hangs up.

I use Vista64 Ultimate.
Here I pested the info which come up:

at WeifenLuo.WinFormsUI.DockPanel.set_DockLeftPortion(Double value)
at WeifenLuo.WinFormsUI.DragHandler.DockWindowSplitter_OnEndDrag(Boolean abort)
at WeifenLuo.WinFormsUI.DragHandlerBase.EndDrag(Boolean abort)
at WeifenLuo.WinFormsUI.DragHandlerBase.System.Windows.Forms.IMessageFilter.PreFilterMessage(Message& m)
at System.Windows.Forms.Application.ThreadContext.ProcessFilters(MSG& msg, Boolean& modified)
at System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at PackageExplorer.Program.Main(String[] args)
Comments: ** Comment from web user: Wouterv **

Error found to be due to lacking 64bit support in Weifenluo docking library. Status will move to closed. I will seek other support for docking on 64 bit operating systems.

COMMENTED ISSUE: Crash on opening 3.0.0 RC1

Wouterv — Fri, 10 Aug 2007 09:45:33 GMT

I'm having a crash running 3.0.0 RC1, have not been able to pass this...

Here's my (Dutch localized...) stack trace:

bij System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
bij System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
bij System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
bij System.Activator.CreateInstance(Type type, Boolean nonPublic)
bij System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
bij System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
bij System.Reflection.Assembly.CreateInstance(String typeName, Boolean ignoreCase)
bij PackageExplorer.Core.AddInModel.AddIn.CreateObject(String className) in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer.Core\AddInModel\AddIn.cs:regel 215
bij PackageExplorer.Core.AddInModel.Codons.ClassCodon.BuildItem(Object owner, ArrayList subItems) in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer.Core\AddInModel\Codons\ClassCodon.cs:regel 37
bij PackageExplorer.Core.AddInModel.DefaultAddInTreeNode.BuildItem(Object caller) in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer.Core\AddInModel\DefaultAddInTreeNode.cs:regel 140
bij PackageExplorer.Services.WorkbenchService.get_DefaultWorkbench() in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer\Services\WorkbenchService.cs:regel 34
bij PackageExplorer.Services.WorkbenchService.CreateInspectorWindow(IContentExplorer explorer, String title, ToolStrip inspectorMenu) in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer\Services\WorkbenchService.cs:regel 124
bij PackageExplorer.Commands.CreateInspectorsCommand.Execute() in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer\Commands\CreateInspectorsCommand.cs:regel 46
bij PackageExplorer.Program.Main(String[] args) in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer\Program.cs:regel 56
Comments: ** Comment from web user: Wouterv **

Guys, I feel that this is a culture related issue. (since the class name I am trying to instantiate should be correct as it is for me). Can you inform me what cutlure settings are being used on your machines?
Also, I noticed that I constructed an error dialog which hides the exception message :( I'll get an updated version for you to try which does mention the correct error name.

COMMENTED ISSUE: Crash on opening 3.0.0 RC1

CompMan86 — Thu, 09 Aug 2007 21:10:34 GMT

I'm getting the same thing I thing. My stack trace (Windows server 2003 Standard edition)

at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Reflection.Assembly.CreateInstance(String typeName, Boolean ignoreCase)
at PackageExplorer.Core.AddInModel.AddIn.CreateObject(String className) in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer.Core\AddInModel\AddIn.cs:line 215
at PackageExplorer.Core.AddInModel.Codons.ClassCodon.BuildItem(Object owner, ArrayList subItems) in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer.Core\AddInModel\Codons\ClassCodon.cs:line 37
at PackageExplorer.Core.AddInModel.DefaultAddInTreeNode.BuildItem(Object caller) in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer.Core\AddInModel\DefaultAddInTreeNode.cs:line 140
at PackageExplorer.Services.WorkbenchService.get_DefaultWorkbench() in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer\Services\WorkbenchService.cs:line 34
at PackageExplorer.Services.WorkbenchService.CreateInspectorWindow(IContentExplorer explorer, String title, ToolStrip inspectorMenu) in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer\Services\WorkbenchService.cs:line 124
at PackageExplorer.Commands.CreateInspectorsCommand.Execute() in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer\Commands\CreateInspectorsCommand.cs:line 46
at PackageExplorer.Program.Main(String[] args) in C:\Documents and Settings\Wouter\My Documents\Visual Studio 2005\Projects\PackageExplorer\PackageExplorer\Program.cs:line 56

COMMENTED ISSUE: Crash on opening 3.0.0 RC1

Wouterv — Wed, 08 Aug 2007 08:35:10 GMT

Maarten, have you got an exception message for me as well?

CREATED ISSUE: Crash on opening 3.0.0 RC1

maartenba — Tue, 07 Aug 2007 19:45:12 GMT

COMMENTED ISSUE: Open Workbook Protected Excel 2007 Files

Wouterv — Sat, 04 Aug 2007 21:21:47 GMT

This will not be available soon.

COMMENTED ISSUE: Hangs up when moving the splitter

Wouterv — Sat, 04 Aug 2007 21:20:26 GMT

The Weifenluo docking library is incompatible with 64 bit operating systems. My guess is due to parsing of window messages. This will not be fixed immediately as I have no alternative to the docking UI. The architecture does allow easy switching of docking library, it is fully factored out.
V3.0.0 does not support 64 bit operating systems

COMMENTED ISSUE: Improve XML identation

Wouterv — Sat, 04 Aug 2007 21:18:13 GMT

Could be a nice feature to format OpenXML to ident every element, just like IE do.
Collapsing nodes doesn't need to be added, IMHO.
Comments: ** Comment from web user: Wouterv **

3.0.0 version contains format document button for XML editor

CREATED ISSUE: Improve XML identation

RubensFarias — Wed, 18 Jul 2007 19:20:47 GMT

Could be a nice feature to format OpenXML to ident every element, just like IE do.
Collapsing nodes doesn't need to be added, IMHO.

CLOSED ISSUE: Application Hangs when reaload an external modified doc

Wouterv — Wed, 06 Jun 2007 19:08:45 GMT

When you open the doc, uses the document inspector, open any xml file to view in, lauch the external program to modify it, save, close, it ask you to reload, reload it and it will hangs!!

COMMENTED ISSUE: Application Hangs when reaload an external modified doc

Wouterv — Wed, 06 Jun 2007 17:13:14 GMT

When you open the doc, uses the document inspector, open any xml file to view in, lauch the external program to modify it, save, close, it ask you to reload, reload it and it will hangs!! Comments: ** Comment from web user: Wouterv **

This is a known issue, and 100% my stupidity. I will resolve this for the next version.

COMMENTED ISSUE: Hangs up when moving the splitter

Wouterv — Wed, 06 Jun 2007 17:12:05 GMT

Steps to re-produce: 1. Start the app. 2. View->Document inspector 3. Drag and move the splitter to left. The splitter which is at the right edge of the "document inspector" pane. 4. Repeat the #3 (~4-6 times usualy enough) Actual result: The apps hangs up. I use Vista64 Ultimate. Here I pested the info which come up: at WeifenLuo.WinFormsUI.DockPanel.set_DockLeftPortion(Double value) at WeifenLuo.WinFormsUI.DragHandler.DockWindowSplitter_OnEndDrag(Boolean abort) at WeifenLuo.WinFormsUI.DragHandlerBase.EndDrag(Boolean abort) at WeifenLuo.WinFormsUI.DragHandlerBase.System.Windows.Forms.IMessageFilter.PreFilterMessage(Message& m) at System.Windows.Forms.Application.ThreadContext.ProcessFilters(MSG& msg, Boolean& modified) at System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at PackageExplorer.Program.Main(String[] args) Comments: ** Comment from web user: Wouterv **

I am unable to reproduce this problem on my machine. The second difficulty will be the stacktrace. My code is not executing, hence I cannot fix this issue.

CLOSED ISSUE: Crash when opening app

Wouterv — Wed, 06 Jun 2007 17:07:31 GMT

I'm using Package Explorer on Vista x64 and get this error when starting the application: GUID muss 32 Ziffern mit 4 Bindestrichen enthalten (...) (GUID has to contain 32 numbers with 4 dashes ...) The app continues to run, but it's not possible to open a file. This is the stack trace: bei System.Guid..ctor(String g) bei PackageExplorer.DockPanel.DeserializeDockContentFromPersistString(String persistString) bei WeifenLuo.WinFormsUI.DockPanelPersist.LoadFromXml(DockPanel dockPanel, Stream stream, DeserializeDockContent deserializeContent, Boolean closeStream) bei WeifenLuo.WinFormsUI.DockPanelPersist.LoadFromXml(DockPanel dockPanel, String filename, DeserializeDockContent deserializeContent) bei PackageExplorer.DockPanel.OnCreateControl() bei System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) bei System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) bei System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) bei System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) bei System.Windows.Forms.Control.CreateControl() bei System.Windows.Forms.Control.WmShowWindow(Message& m) bei System.Windows.Forms.Control.WndProc(Message& m) bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

CLOSED ISSUE: Binary Editor crashes on large files

Wouterv — Wed, 06 Jun 2007 17:07:06 GMT

Binary Editor crashes on large files

CLOSED ISSUE: About box & version info

Wouterv — Wed, 06 Jun 2007 17:06:22 GMT

It's not a bug, but a feature that is apparently missing. The Package Explorer exe file lacks version information & there's no about box in the application itself, so it's hard to check if one has current version of PE or not. It'd be nice if those two did exist. The about box could also contain clickable URL of this site, to make checking for new version easier. It'd be best if there was some "Check for updates" function in the app (nothing automatic), which would compare the application's version with current version number on the web and inform the user if they are same or not and in the second case would give the user some link/button to click to enter the download page. Thank you for otherwise very good application.

COMMENTED ISSUE: Open Workbook Protected Excel 2007 Files

Wouterv — Sun, 20 May 2007 17:56:42 GMT

Hi, Im interested if its possible to get an Excel 2007 with Workbook Protection turned on to be viewd in the explorer. If workshhet protection is the infoamrion is in the XML but for Workbook protection the file seems to get encrypted. Has anyone anyinformation on this? Would like to know of a way to provide the password for it to be decrypted into a state to unzip the file again for the XML. Many Thanks Gary Howlett Comments: ** Comment from web user: Wouterv **

This might be possible but I believe the encryption technique is not open.

CREATED ISSUE: Open Workbook Protected Excel 2007 Files

ghowlett — Fri, 18 May 2007 12:43:52 GMT

Hi, Im interested if its possible to get an Excel 2007 with Workbook Protection turned on to be viewd in the explorer. If workshhet protection is the infoamrion is in the XML but for Workbook protection the file seems to get encrypted. Has anyone anyinformation on this? Would like to know of a way to provide the password for it to be decrypted into a state to unzip the file again for the XML. Many Thanks Gary Howlett

COMMENTED ISSUE: Hangs up when moving the splitter

DataByte — Wed, 16 May 2007 17:41:03 GMT

Steps to re-produce: 1. Start the app. 2. View->Document inspector 3. Drag and move the splitter to left. The splitter which is at the right edge of the "document inspector" pane. 4. Repeat the #3 (~4-6 times usualy enough) Actual result: The apps hangs up. I use Vista64 Ultimate. Here I pested the info which come up: at WeifenLuo.WinFormsUI.DockPanel.set_DockLeftPortion(Double value) at WeifenLuo.WinFormsUI.DragHandler.DockWindowSplitter_OnEndDrag(Boolean abort) at WeifenLuo.WinFormsUI.DragHandlerBase.EndDrag(Boolean abort) at WeifenLuo.WinFormsUI.DragHandlerBase.System.Windows.Forms.IMessageFilter.PreFilterMessage(Message& m) at System.Windows.Forms.Application.ThreadContext.ProcessFilters(MSG& msg, Boolean& modified) at System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at PackageExplorer.Program.Main(String[] args) Comments: ** Comment from web user: DataByte **

I had the same problem. Also running Vista Ultimate x64