|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Firebird on Wondows Vista?
Hi All,
Have anybody tested Firebird on Windows Vista? I'm trying it with .net provider for Firebird, but no success? Anybody care to share experience ? |
|
#2
|
||||
|
||||
|
Quote:
__________________
My blog Tutorials about OSS databases, DBMonster ... Contribute to OSS Development, fill bug reports! Developer Shed eSupport Commented my.ini/my.cnf (ADD YOUR OWN CONFIG TRICK) An introduction to database normalization Natural or Surrogate key Custom ordering for your results Correlated and uncorrelated subqueries Don't turn your outer joins into inner joins Random data (with a bias) |
|
#3
|
|||
|
|||
|
I have a VS C# 2005 WinForms application using Firebird embedded database, ver 1.5, via the .NET provider - FirebirdClient 2.0 for .NET Framework 2.0.
It runs fine on Windows XP. No problems connecting and quering the database. However on Windows Vista RC2 the application starts, but when it tries to connect to the Firebird db via the .NET provider, an exception occurs with the following details: Code:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
at FirebirdSql.Data.Firebird.FbConnectionPool.create()
at FirebirdSql.Data.Firebird.FbConnectionPool.CheckOut()
at FirebirdSql.Data.Firebird.FbConnection.Open()
at System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)
at TestAccounts.Form1.Form1_Load(Object sender, EventArgs e) in C:\Users\Yas\Desktop\TestAccounts\TestAccounts\Form1.cs:line 37
at System.Windows.Forms.Form.OnLoad(EventArgs e)
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.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.308 (rtmLHS.050727-3000)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
TestAccounts
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Yas/Desktop/TestAccounts/TestAccounts/bin/Debug/TestAccounts.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.308 (rtmLHS.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.308 (rtmLHS.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.308 (rtmLHS.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.308 (rtmLHS.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_64/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.308 (rtmLHS.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
FirebirdSql.Data.Firebird
Assembly Version: 1.6.3.0
Win32 Version: 1.6.3.0
CodeBase: file:///C:/Users/Yas/Desktop/TestAccounts/TestAccounts/bin/Debug/FirebirdSql.Data.Firebird.DLL
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
|
|
#4
|
|||
|
|||
|
Have you tried to debug the application from Microsoft Visual C# Express Edition (or whatever IDE you are using), to see the exact statement that produces the exception?
I had trouble with Vista and Firebird. The connection.Open() command wouldn't work because the database is somehow protected from regular users in Vista (haven't figured that out yet). Everything worked well when I launched my application "As Administrator", there was a dialog asking me whether I grant permission to my application to elevate to Administrator. To do this automaticly, I read about adding a manifest to the application (See "Vista UAC Elevation C#" on Google to find more). To make your application run as administrator each time (envoking the corresponding dialog at start), create a file named <project name>.exe.manifest into the project folder. Write the following into the file: Code:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity version="1.0.0.0" processorArchitecture="X86" name="project_name" type="win32"/>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="requireAdministrator"/>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
then add a post-build event to the project properties. Write the following: "$(DevEnvDir)..\..\SDK\v2.0\bin\mt.exe" -manifest "$(ProjectDir)$(TargetName).exe.manifest" –outputresource:"$(TargetDir)$(TargetFileName)";#1 this will add the manifest to the application, which will tell Vista to run it as Administrator. It uses an utility in .NET SDK, mt.exe. Original Article |
|
#5
|
|||
|
|||
|
We had a problem with using Firebird on Vista Home Edition... the application was .net forms based and the exception we got was obscure. Turns out we needed to install Visual C Runtime dlls.
msvcp71.dll this is a C++ runtime library msvcr71.dll this is a C runtime library For some reason though, other versions of Vista did not have this problem. Good luck! |
![]() |
| Viewing: Dev Shed Forums > Databases > Firebird SQL Development > Firebird on Wondows Vista? |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|