Submitted by: Robert Kindl (rkindl)

When I reference FirebirdSql.Data.FirebirdClient.dll in "Client-only" project I get following warnings:
Warning 1 The referenced assembly "FirebirdSql.Data.FirebirdClient.dll" has a dependency on "System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" which is not listed as part of the "Client" TargetFrameworkSubset. If this dependent reference is required, you may get compilation errors.

Warning 2 The referenced assembly "FirebirdSql.Data.FirebirdClient.dll" has a dependency on "http://System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which is not listed as part of the "Client" TargetFrameworkSubset. If this dependent reference is required, you may get compilation errors.

Suggested solution for Warning 1
Provide version with conditional symbol ENTITY_FRAMEWORK switched off.

Suggested solution for Warning 2
Provide version with newly introduced conditional symbol SYSTEM_WEB switched off, which could be used in FbConnectionInternal.cs like this:
#⁠if (SYSTEM_WEB)
// showing ApplicationPhysicalPath may be wrong because of connection pooling; better idea?
if (System.Web.Hosting.HostingEnvironment.IsHosted)
return System.Web.Hosting.HostingEnvironment.ApplicationPhysicalPath;
else
#⁠endif
return Process.GetCurrentProcess().MainModule.FileName;

Maybe it will be wise to create new new conditional symbol CLIENTONLY_FRAMEWORK.

In FirebirdSql.Data.FirebirdClient.csproj there is also reference to "System.Design" which is not included in "Client-Only" subset too. But this assembly is not used for anything, so it doesn't generate warning as long as it's not used.

In all cases I would suggest to pre-build all these version as binaries, because many people are afraid of building from source code. It's because they see it as unofficial and unsupported. And it's also harder to mantain (it's much easier to copy one new .dll than rebuilding project with some "custom conditional symbols").