TypeLoadException was unhandled with 3.0.2 and VS2005 RC

TypeLoadException was unhandled with 3.0.2 and VS2005 RC

Postby Guest » Thu 06 Oct 2005 14:32

I am getting the following exception after upgrading to the latest Release Candidate of VS2005 and MySQL.NEt 3.0.2.

System.TypeLoadException was unhandled
Message="Declaration referenced in a method implementation cannot be a final method. Type: 'CoreLab.Common.DbDataReaderBase'. Assembly: 'CoreLab.MySql, Version=3.0.2.0, Culture=neutral, PublicKeyToken=09af7300eec23701'."
Source="OrcaTest"
TypeName="CoreLab.Common.DbDataReaderBase"
StackTrace:
at OrcaTest.clsMySQLAccess.GetOperatorNames()
at OrcaTest.frmLogin.frmLogin_Load(Object sender, EventArgs e) in C:\Archive\VBNET2005\ORCATest\OrcaTest\frmLogin.vb:line 45
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.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.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.SafeNativeMethods.ShowWindow(HandleRef hWnd, Int32 nCmdShow)
at System.Windows.Forms.Control.SetVisibleCore(Boolean value)
at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
at System.Windows.Forms.Control.set_Visible(Boolean value)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at System.Windows.Forms.Form.ShowDialog()
at OrcaTest.frmMain.DotNetBarManager1_ItemClick(Object sender, EventArgs e) in C:\Archive\VBNET2005\ORCATest\OrcaTest\frmMain.vb:line 123
at DevComponents.DotNetBar.DotNetBarManager.AX(BaseItem 3AP)
at DevComponents.DotNetBar.BaseItem.RaiseClick()
at DevComponents.DotNetBar.BaseItem.InternalMouseUp(MouseEventArgs objArg)
at DevComponents.DotNetBar.PopupItem.InternalMouseUp(MouseEventArgs objArg)
at DevComponents.DotNetBar.ButtonItem.InternalMouseUp(MouseEventArgs objArg)
at DevComponents.DotNetBar.MenuPanel.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at DevComponents.DotNetBar.MenuPanel.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.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(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 System.Windows.Forms.Application.Run(ApplicationContext context)
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
at OrcaTest.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81
at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()


I also saw your posts about the problem being in the latest version of the 2.x framework released with VS200 RC.

I am posting here to again stress that development is now halted for me on this project and I can not wait until the final release of VS2005 in order for you to address this problem.

Please take some time to fix this problem and get an update for us ASAP. All of the other custom controls that I use, XCEED, Proessentials, DotNetBar,DotNetMagic have all kept pace and have working releases for VS2005. I would hope that you would join them in putting customer support at the top of your list.
Guest
 

Postby Serious » Thu 06 Oct 2005 14:47

We plan to support release version of .NET Framework 2 as soon as it becomes available.
Serious
 

Postby Serious » Thu 06 Oct 2005 14:51

You can use MySQLDirect .NET Data Provider 3.00 for .NET1 in your .NET2 projects. You can do it in the following way:

- Uninstall version of Data Provider for .NET2 framework;
- Install version for .NET1 framework;
- Open Microsoft Visual Studio;
- Open toolbox using View/Toolbox command;
- In the toolbox execute "Choose Items..." command;
- In the opened dialog box browse for CoreLab.MySql.dll assembly that can by located in the root installation folder;
After that you can use the design-time components and compile your projects that use .NET2 framework.
Serious
 


Return to dotConnect for MySQL