te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>prism:Support for AssemblyLoadContext - Loading a module with multiple versions - Stack Overflow

你的位置：首页>programmer>prism:Support for AssemblyLoadContext - Loading a module with multiple versions - Stack Overflow

prism:Support for AssemblyLoadContext - Loading a module with multiple versions - Stack Overflow

programmeradmin2025-02-212浏览0评论

By using AssemblyLoadContext .NET does allow for multiple versions of a given module/dll to be loaded into an application.

Prism though requires to have Modules that are Unique by name. Because of this technically it is NOT POSSIBLE to use Prism in a scenario where I have the more than one version of the same module loaded twice.

Have to point out that I am using DryIoc as dependency resolver and DryIoc has no problems with this scenario. For this to work one just has to use the WithoutInterpretationForTheFirstResolution DryIoc Container Rules when creating the container. In this case, instead of the simple name, DryIoc will use full type info to identify objects.

Is there any chance to add support this scenario in Prism? By "this scenario" I mean: Assamblies that have same name but different version.

Thanks for your attention.

与本文相关的文章