Freigeben über

Porting Issues: CompositeUI.Winforms Unit Tests

  • Artikel

Issue 1:

 

.NET CF Does not support System.Windows.Forms.GiveFeedbackEventArgs and DragEventArgs. In general lacks design time support.

(resolution: short term - remove design time support, long term...)

 

Issue 2:

 

.NET CF Does not support System.Windows.Forms.TabControl.SelectedTab property.

(resolution: use SelectedIndex property instead)

 

Issue 3:

 

.NET CF Does not support System.Windows.Forms.TabControl.TabPageSelection.Remove method.

(resolution: ???)

 

Issue 4:

 

.NET CF Does not support System.Windows.Forms.TabControl.SelectedTab property.

(resolution: use SelectedIndex property instead)

 

Issue 5:

 

TabWorkspace attempts to reference a TabPage in the TabPages collection using a string key (i.e. TabPages[key]). This does not seem to be supported in .Net CF.

(resolution: ???)

 

Issue 6:

 

.NET CF does not support System.Runtime.CompilerServices.CompilerGeneratedAttribute().

(Resources.Designer.cs)

(resolution: ???)

 

Issue 7:

 

In Visual Studio 2005, create a Windows Mobile 5 Windows Form. The TabWorkspace throws error when trying to add control to form.(TabWorkspace.cs)

(resolution: Seems that VS2005 doesn't like the Pages property declared as ReadOnlyDictionary. When declaring as Dictionary, error went away.)

 

Issue 8:

 

System.ComponentModel.CategoryAttribute not implemented in CF.(WindowSmartPartInfo.cs)

(resolution: ???)

 

Issue 9:

 

System.Drawing.ToolboxBitmapAttribute not implemented in CF.(WindowSmartPartInfo.cs)

(resolution: ???)

 

Issue 10:

 

System.Windows.Forms.IWin32Window not implemented in CF. (WindowWorkspace.cs)

(resolution: IWin32Window was used for modal windows. We are going to implement this using a form and manipulating the form title.)

 

Issue 11:

 

Forms are full screen in CF. It doesn't make sense to have a Location or Size in the SmartPartInfo.

(resolution: We've already removed Location and Size from the SmartPartInfo.)

 

Issue 12:

 

There are not practicall using for an Icon in a CF Form.

(resolution: We've removed the Icon from the SmartPart.)

 

Issue 13: Changes to WindowsSmartPartInfo

 

We made some changes to WindowsSmartPartInfo in order to work better match the way windows work on the PocketPC:

  • Removed a number of properties that didn't make sense on the PocketPC.
  • Added a ControlBoxOption property to replace the setters for MinimizeBox and ControlBox. Since the minimize and control settings have a different behavior on the Pocket PC, we created an enum that encapsulated the three available states.

Issue 14:

 

Added a new workspace, called FormWorkspace, that makes it easier to create a set of menus that will appear in a form.