On 1/16/08, paha <[EMAIL PROTECTED]> wrote:
>
>
> Jiri Cincura wrote:
> >
> > It's because when you specify parth to fbembed.dll, we have to
> > generate some small assembly to load it (in normal way it's searched
> > in standard paths).
> >
> sure, but according to the source code comments, it mus
Jiri Cincura wrote:
>
> It's because when you specify parth to fbembed.dll, we have to
> generate some small assembly to load it (in normal way it's searched
> in standard paths).
>
sure, but according to the source code comments, it must not be saved to
disk in release
#if DEBUG
// In
On 1/16/08, paha <[EMAIL PROTECTED]> wrote:
> i found some funny thing in latest 2.5 build (i made the build against
> latest source from svn, but seems to me it concerns also the last build on
> your www-page). The problem is - two dlls (DynamicAssembly.dll and
> Fb_.dll) are generated in appl
Hi Jiri,
i found some funny thing in latest 2.5 build (i made the build against
latest source from svn, but seems to me it concerns also the last build on
your www-page). The problem is - two dlls (DynamicAssembly.dll and
Fb_.dll) are generated in application folder when i use fbembedd.
Acco
