tag:blogger.com,1999:blog-7462882.comments2023-06-05T09:12:14.398-04:00GIS ResearchAnonymoushttp://www.blogger.com/profile/09241601264454722977noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7462882.post-5652248380039666462008-11-25T12:36:00.000-05:002008-11-25T12:36:00.000-05:00Hey, I have an application where there is a scenar...Hey, I have an application where there is a scenario where I've got stuck. There are a no. of assemblies which are not required to be installed in GAC. So I tried to use Assembly.LoadFrom to load such assemblies. But the problem came when a requirement to support 2 versions of application came. In this case, there are 2 different paths for 2 different versions of all the application assemblies, and if someone tries to access both the versions, the LoadFrom doesn't work, as it returns the firstly loaded version of a particular dll(say A.dll from C:\Path1) even if I say LoadFrom(C:\Path2\A.dll). This is something which is putting me off. I don't want to install all such DLLs into GAC, as there are about 150 or more such DLLs, and as such they will unnecessarily clutter the GAC. And 150 *2 = 300 Dlls at a single time in GAC. Is there a way out for this situation?Sumithttps://www.blogger.com/profile/05524571678400260367noreply@blogger.comtag:blogger.com,1999:blog-7462882.post-50735337815089376722007-02-03T18:38:00.000-05:002007-02-03T18:38:00.000-05:00if you want to see how to do it with SMO, here's a...if you want to see how to do it with SMO, here's an app I wrote a while ago that generates scripts for all objects in any 2000 or 2005 database using SMO. source is available.<br /><br />http://www.elsasoft.org/tools.htmAnonymoushttps://www.blogger.com/profile/16973186993580852346noreply@blogger.comtag:blogger.com,1999:blog-7462882.post-1123529389101316172005-08-08T15:29:00.000-04:002005-08-08T15:29:00.000-04:00When a delegate is created,the compiler generates ...When a delegate is created,the compiler generates three methods for you, Invoke, BeginInvoke and EndInvoke. Invoke is used to execute the delegate synchronously (i.e. a line of code such as myDelegate(); is actually compiled as myDelegate.Invoke();). The other two methods are for asynchronous execution, and must always be called as a pair - every BeginInvoke must be matched by a call to EndInvoke somewhere to guarantee that you don't leak resources.Anonymoushttps://www.blogger.com/profile/09241601264454722977noreply@blogger.com