On Mon, 2010-05-10 at 07:29 -0700, Bonfo wrote: > I've used DbLinq for a simple utility that we needed in our company. > Now i completed it, or at least, it is at a stable stage. I'd like to > build a simple package that each developer here can use to install the > utility in their machine. > > Which is the best way to put DbLinq DLLs in the package?!
The same way you put any other unsigned assemblies in your package. :-) They're just assemblies, there's nothing particularly special about them. So if this is a binary/installer package, make sure that you install the DbLinq assemblies you need alongside your program (in the same directory) so that the normal .NET assembly prober can find them. For ASP.NET webapps, place the DbLinq assemblies into the 'bin' directory (same as with any other assembly). For source packages, a common convention is to place 3rd party assemblies into a "lib" directory, and reference these assemblies from your .csproj files. Do the same with DbLinq as you would any other 3rd party assembly. See also: http://code.google.com/p/dblinq2007/wiki/Installation - Jon -- You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/dblinq?hl=en.
