By Purnell W Glenn - 2/10/2008
When trying to create a New File Group, I get the following error. MissingMethodException
Method not found: 'Void MicroFour.StrataFrame.UI.Windows.Forms.ChildFormDialog.set_ParentForm(MicroFour.StrataFrame.UI.Windows.Forms.BaseForm)'. Source : DatabaseDTK Stack Trace:
at MicroFour.StrataFrame.Data.FileGroupProperties.InitializeComponent()
at MicroFour.StrataFrame.Data.FileGroupProperties..ctor(Int32 DatabasePK, Int32 FileGroupPK)
at MicroFour.StrataFrame.Data.ProfileEditorDialog.ShowFileGroupProperties(Int32 FileGroupPK)
at MicroFour.StrataFrame.Data.ProfileEditorDialog.cmi_Profile_AddFileGroup_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
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.ScrollableControl.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.OnMessage(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)
|
By Trent L. Taylor - 2/10/2008
Purnell,I am not sure why this would be causing an error. I have double-checked to make sure that something isn't missing here, but the first thing I might suggest, especially since there have been so many enhancements included on this most recent post, I would load the 1.6.5 beta because assuming that something is wrong, you will need to be on the most recent version before we could really troubleshoot this anyway. You can get the most recent install here: http://forum.strataframe.net/FindPost14258.aspx If the problem persists after the update then we can dig a little deeper.
|
By Trent L. Taylor - 2/10/2008
I just looked at your error again and noticed what was going on....it looks as though your StrataFrame UI is either old or not update to date. The install is still a good idea, but this is not related to the DDT, but rather the ChildFormDialog control (which is being used in this instance). Make sure that you don't have any old StrataFrame assemblies in the GAC (which the install should remove). But the easiest thing would probably be to just load the update as it would more than likely resolve this issue.
|
By StrataFrame Team - 2/11/2008
Yep, MissingMethodException always means that the assemblies are not of the same version... the referencing assembly is expecting a method to be in a referenced assembly, but it's no longer there. It could be caused by a name change, a method signature change, or simply a method removal, but it just means that the referencing assembly you have was not built against the referenced assembly that you have. So, like Trent said, just load the update so you can be sure that all of your assemblies were built together as a group.
|
By Purnell W Glenn - 2/11/2008
Loading the 1.6.5 ver created the issue.
|
By Trent L. Taylor - 2/11/2008
Purnell,I understand  But it is actually not 1.6.5 that is the crux of the issue. The bottom line is that you have more than one assembly of the same name and version out there on disk somewhere. We did not change the assembly from, just the file version, so you have a mixture of new and old assemblies that are being referenced. So you need to remove all of your StrataFrame references in the GAC, just to make sure all of the old references are gone, next you want to get the new assemblies back in....that is why we recommended loading the install again once this is done. This is a common issue with .NET and assemblies being out of sync. So we understand the problem, we are just trying to help you get to a resolution in the fewest number of steps.
|
By Angela Sampaio - 3/18/2008
Hello,
I am having a problem like this, that started to happen after the upgrade from version 1.6.5. 
I reinstalled the update of version, but has not worked ...
Below the stack-trace
--------------------------------------------------------------------------------------------------
MissingMethodException
Método não encontrado: 'Void MicroFour.StrataFrame.UI.Windows.Forms.SearchFieldItem.set_InitiallyEnabled(Boolean)'.
Source : GoLiveCorporate
Stack Trace:
em GoLiveCorporate.frmProjeto.InitializeComponent()
em GoLiveCorporate.frmProjeto..ctor()
em GoLiveCorporate.frmMDI.item_frmProjeto_LinkClicked(Object sender, NavBarLinkEventArgs e)
em DevExpress.XtraNavBar.NavBarItem.RaiseLinkEvent(Object linkEvent, NavBarItemLink link)
em DevExpress.XtraNavBar.NavBarItem.RaiseLinkClicked(NavBarItemLink link)
em DevExpress.XtraNavBar.NavBarItem.RaiseLinkClickedCore(NavBarItemLink link)
em DevExpress.XtraNavBar.NavBarControl.RaiseLinkClicked(NavBarItemLink link)
em DevExpress.XtraNavBar.ViewInfo.NavBarViewInfo.DoLinkClick(NavBarHitInfo hitInfo)
em DevExpress.XtraNavBar.ViewInfo.NavBarViewInfo.DoClick(NavBarHitInfo hitInfo)
em DevExpress.XtraNavBar.ViewInfo.NavigationPaneViewInfo.DoClick(NavBarHitInfo hitInfo)
em DevExpress.XtraNavBar.ViewInfo.NavBarViewInfo.OnMouseUp(MouseEventArgs e)
em DevExpress.XtraNavBar.NavBarControl.OnMouseUp(MouseEventArgs ev)
em System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
em System.Windows.Forms.Control.WndProc(Message& m)
em DevExpress.XtraNavBar.NavBarControl.WndProc(Message& m)
em System.Windows.Forms.Control.ControlNativewindow.OnMessage(Message& m)
em System.Windows.Forms.Control.ControlNativewindow.WndProc(Message& m)
em System.Windows.Forms.Nativewindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
--------------------------------------------------------------------------------------------------------
Thanks
Angela
|
By Trent L. Taylor - 3/18/2008
Angela,You still have the old StrataFrame assemblies that are being referenced instead of the new assemblies. First, click StrataFrame -> Version... within Visual Studio to see if all of the assemblies come back as 1.6.5. Next, open the solution that you are having issues with. Once open, right-click the solution and click "Clean Solution" then right-click the solution again and click "Rebuild Solution." If it doesn't work after that let me know. The bottom line is that there is an old StrataFrame assembly somewhere that doesn't have the new properties that is being seen and referenced by your solution.
|
By Angela Sampaio - 3/19/2008
Hi,
The version of the all assemblies is 1.6.5.
I did the "clean solution" and "rebuild solution".
In my computer the system that I am developing works correctly, but in computers that have the system installed continued with the problem even after the upgrade of the system with the new dlls (clean solution / rebuid). 
|
By Trent L. Taylor - 3/19/2008
In my computer the system that I am developing works correctly, but in computers that have the system installed continued with the problem even after the upgrade of the system with the new dlls (clean solution / rebuid). So your development machine is working, but machines that are running your application are not. Is that correct? If so, you have be sure to remove any assemblies from teh GAC and add the new assemblies. If you are not using the GAC on your applicaiton, then you need to make sure that you are distributing the new assemblies. The one thing that I am nearly 100% confident of is that you have old StrataFrame assemblies that are being referenced instead of the new assemblies. One reason we only changed the file version instead of the assembly version is to reduce the complications of updating existing projects. You should just be able to load the new SF install and start working versus having to change all of your references. Search for StrataFrame assemblies on the machine that is not working (including the GAC [c:\windows\assembly]), compare them to the version on your machine that is working. That should at least help you track down the rogue assemblies
|
|