具有网站模型的 SubWebFolder 和多个 bin 文件夹？
我正在寻找一些关于子网站文件夹的最佳方法是什么以及在网站项目模型中拥有多个 bin 文件夹的建议。用于在稍后阶段添加新页面，无需重新编译网站的核心文件，也无需构建完整的插件框架 api。我知道能够将编译后的 dll 放入主 bin 文件夹中，并将新页面文件复制到子文件夹中，但我正在寻找一种更有组织的文件/文件夹方法。
以下是使用 WAP 的方法： 移动代码隐藏程序集/DLL使用 ASP.NET 1.1 到与 /BIN 不同的文件夹
我还应该提到，我发现我仍然可以通过调整此处提到的配置部分来使用网站项目模型的旧方法来完成此操作，但我想知道这是否有任何副作用。
I am looking for some advice on how what is the best approach to subweb folders and having mutliple bin folders in the WebSite Project model. For adding new pages at a later stage without recompiling the core files of a website and without building a full fledged Plug-in framework api. I am aware of being able to drop in the compiled dlls into the main bin folder and to just copy over the new page files to a sub folder but I am looking for a more organized file/folder approach.
Here is the how it was done with WAP:
Moving the Code-Behind Assemblies/DLLs to a different folder than /BIN with ASP.NET 1.1
Multiple /bin folders in ASP.NET
I should also mention that I see that I can still do it the old way with the website project model by making the adjustment to the config section mentioned here but I was wondering if that has any side affects.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您是否正在尝试将新的 DLL 或新的源代码复制到您的站点？请注意，对于源，网站中的最佳位置是 App_Code 文件夹。在那里，您可以创建任何您喜欢的任意文件夹结构，并且它们都将在运行时构建到程序集中。然后，每个页面都会获得对该程序集的引用，并且能够使用其中的类型。
Are you trying to copy new DLL's or new sources to your site? Note that for sources, the best place in web sites is the App_Code folder. In there, you can create any arbitrary folder structure that you like, and it will all be built at runtime into an assembly. Then, every page gets a reference to that assembly and is able to use types from there.