On Fri, Mar 13, 2009 at 21:52, Rick Roen <[email protected]> wrote:
> My typical client setup is to run all the programs from a UNC file path and
> put all the associated DLL in the same path.
That's not common. Apps from network are running in lower trust (by
default), thus admin has to change config file for machine(s).
> If I just replace the FirebirdClient.dll with the updated version I think I
> recall that the programs will fail because they cannot find the version of
> the dll that they were originally compiled with. So what I do is open the
> solution in VS2008, delete and add the FirebirdClient.dll reference to
> update the
> version and then recompile.
>
> Is this not the normal way?
No it isn't. :) First changing major o minor number means, that
something inside changed, so you should test the application befo
deploying. Anyway if you feel brave, you can just say in
app.config/machine.config, that version x.y.z is now z.y.x and the
application will use the new one.
--
Jiri {x2} Cincura (CTO x2develop.com)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
