Missing sqlceme35.dll

[zacks]

I am trying to write an application that pulls data out of a SQL
Server CE database file, an SDF file. It works just fin on my computer
(running XP Pro). But when a co-worker tries to run it on his XP Pro
computer, he gets an error that it is unable to load a DLL, namely
sqlceme35.dll.

I am wondering why the application runs fine on my computer but not
his?

The app was installed on both computers using a Setup project MSI
file.

Developed with VS2008 with Target Framework set to 2.0.

 

[kimiraikkonen]

I am trying to write an application that pulls data out of a SQL
Server CE database file, an SDF file. It works just fin on my computer
(running XP Pro). But when a co-worker tries to run it on his XP Pro
computer, he gets an error that it is unable to load a DLL, namely
sqlceme35.dll.

I am wondering why the application runs fine on my computer but not
his?

The app was installed on both computers using a Setup project MSI
file.

Developed with VS2008 with Target Framework set to 2.0.

I think you should copy the DLL on co-worker's computer's system32
directory then register it via regsvr32.

 

[Nicholas Paldino [.NET/C# MVP]]

That looks to be an assembly distributed with SQL Server Compact Edition
3.5. Do you actually have that installed on the other machine?

 

[zacks]

I think you should copy the DLL on co-worker's computer's system32
directory then register it via regsvr32.

That is an unaccepatable solution. We expect to eventually distribute
this application to our customers, and would prefer that the setup
includes everything that is needed. I tried to add the DLL as a
reference but VS2008 would not let me.

 

[zacks]

    That looks to be an assembly distributed with SQL Server Compact Edition
3.5.  Do you actually have that installed on the other machine?

Not yet, but will try. But the question is why? IMHO, you shouldn't
have to.

 

[Arne Vajhøj]

I am trying to write an application that pulls data out of a SQL
Server CE database file, an SDF file. It works just fin on my computer
(running XP Pro). But when a co-worker tries to run it on his XP Pro
computer, he gets an error that it is unable to load a DLL, namely
sqlceme35.dll.

I am wondering why the application runs fine on my computer but not
his?

The app was installed on both computers using a Setup project MSI
file.

Developed with VS2008 with Target Framework set to 2.0.

Your app needs:

System.Data.SqlServerCe.dll
sqlceme35.dll
sqlceqp35.dll
sqlcese35.dll

The first is a .NET assembly. The last 3 are Win32 DLL's.

Nothing need to be installed. Just put the 4 DLL's in same
dir as your EXE.

Arne

 

[Nicholas Paldino [.NET/C# MVP]]

Well, yes, you should, because the EULA for SQL Server Compact Edition
3.5 probably says that you can't redistribute parts of the install, but have
to install the whole thing. AFAIK, the dll you are looking for is not a
part of the .NET framework.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

That looks to be an assembly distributed with SQL Server Compact Edition
3.5. Do you actually have that installed on the other machine?

Not yet, but will try. But the question is why? IMHO, you shouldn't
have to.

 

[ErikEJ]

For more information on SQL Compact deployment, see
http://msdn2.microsoft.com/en-us/library/bb219481.aspx

 

[kimiraikkonen]

Your app needs:

System.Data.SqlServerCe.dll
sqlceme35.dll
sqlceqp35.dll
sqlcese35.dll

The first is a .NET assembly. The last 3 are Win32 DLL's.

Nothing need to be installed. Just put the 4 DLL's in same
dir as your EXE.

Arne

Actually, if OP refenced DLLs and builded/run the app(exe), i think
they must have been copied to the app's folder automatically.

 

[zacks]

Your app needs:

System.Data.SqlServerCe.dll
sqlceme35.dll
sqlceqp35.dll
sqlcese35.dll

The first is a .NET assembly. The last 3 are Win32 DLL's.

Nothing need to be installed. Just put the 4 DLL's in same
dir as your EXE.

OK, I already had the first file since it was a reference in the
project. I manually added the other three. I do not get the unable to
load DLL error, but I do get an error when trying to open the
connection. Exception message is "Unspecified error".

 

[zacks]

Actually, if OP refenced DLLs and builded/run the app(exe), i think
they must have been copied to the app's folder automatically.

Visual Studio will not allow me to add these DLLs as references.
Claims that they are not valid assemblies.

 

[Arne Vajhøj]

Visual Studio will not allow me to add these DLLs as references.
Claims that they are not valid assemblies.

The last 3 are Win32 DLL's not .NET assemblies.

Arne

 

[Arne Vajhøj]

OK, I already had the first file since it was a reference in the
project. I manually added the other three. I do not get the unable to
load DLL error, but I do get an error when trying to open the
connection. Exception message is "Unspecified error".

Can we get the complete exception text ?

And maybe a code snippet around the relevant line ?

Arne

 

[kimiraikkonen]

Visual Studio will not allow me to add these DLLs as references.
Claims that they are not valid assemblies.- Hide quoted text -

- Show quoted text -

That's annoying if the assemlies are really valid. However in VB 2005,
i also can't reference some DLLs which are denied by VS claiming
they're not COM-compatible or valid assembly or kinda errors..For my
subject's DLL, I suspect they're written as unmanaged DLLs plus
suspecting that they are written in C++.

For example i can'T reference that DLL on a VB site on VB 2005:

http://www.vbcodesource.org/downloads/encoderex.zip

 

[zacks]

For more information on SQL Compact deployment, see

http://msdn2.microsoft.com/en-us/library/bb219481.aspx

OK, this was the best suggestion yet. But this page did not go quite
far enough. For the files to be installed on the application folder,
you also MUST add all seven of the files to the Application Folder in
the Setup project.

Now, the real mystery is, how come this application ever ran just fine
for me before I added these DLLs to the project at all?!?

 

[ErikEJ]

SQL Compact is installed globally on your machine (as part of VS 2008,
perhaps?).

Your colleague did not have SQL Compact installed.

--
Erik Ejlskov Jensen, Mobile App Dev MCTS
Check out my SQL Compact blog at
http://erikej.blogspot.com

For more information on SQL Compact deployment, see

http://msdn2.microsoft.com/en-us/library/bb219481.aspx

OK, this was the best suggestion yet. But this page did not go quite
far enough. For the files to be installed on the application folder,
you also MUST add all seven of the files to the Application Folder in
the Setup project.

Now, the real mystery is, how come this application ever ran just fine
for me before I added these DLLs to the project at all?!?