Custom Query (35 matches)
Results (28 - 30 of 35)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#7 | wontfix | Display of error when .Net Framework 2.0 not present | michelpons | michelpons |
Description |
I have created a Virtual Machine running under Win XP Pro. When Microsoft .Net Framework 2.0 is not installed, there is an error message and the installer exits. Was wondering if the dialog could not be reduced to one screen showing up instead of two like nowadays. |
|||
#12 | wontfix | Log of installation | michelpons | michelpons |
Description |
During the installation itself, the user is looking at a screen where a status line appears and where text is displayed for a very short period of time (speed depends obviously on computer performance). Would it be possible to obtain a log of the installation and to have it accessible from the final installation screen. This would raise the issue of where to store that log. |
|||
#20 | wontfix | Marshal.ReleaseComObject | michelpons | jasper |
Description |
Documentation should mention that for .NET implementations, all external objects must be released using Marshal.ReleaseComObject when they go out of scope. Otherwise .NET will not release the COM objects until GC is invoked, which causes external references to temporary objects to linger, and causes objects to be locked passed Terminate. It should be mentioned that Marshal.ReleaseComObject will render a COM object inaccessible, so this should not be done on a particular interface to a COM object while other interfaces to the same object must remain valid. Example: IPersistStreamSave should Marshal.ReleaseComObject the stream pointer within the routine. Example: objects connected to unit ports should Marshal.ReleaseComObject at Disconnect and Terminate. |