blocks|key|1626132|text|这只是猜测，但似乎您正在尝试使用基于UI的体系结构模式来构建您的业务层。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1626133|通常，您的模型、视图和控制器都维护在主web应用项目中。任何支持函数(如BL和DL)都是通过类库添加的。Visual模板就是围绕这个概念构建的，这就是为什么您必须用GUID手动添加支持--以及为什么它会自动创建视图。|1626134|如果我想问一问，你为什么要在你的BL中建立控制器？如果您试图将UI与服务器代码分离，那么WebAPI可能是一个更好的选择。|1626135|更新-几个有用的链接|offset|length|style|BOLD|1626136|ProDinner+-+ASP.NET+MVC示例应用程序|1626137|具有实体框架、Autofac、ASP.NET+MVC和单元测试的分层应用程序|1626138|架构指南:+ASP.NET+MVC框架%2BN层%2B实体框架等等|1626139|entityMap|0|LINK|mutability|MUTABLE|url|https://prodinner.codeplex.com/|1|https://code.msdn.microsoft.com/Service-Layer-Entity-7a1fac6c|2|http://www.codeproject.com/Articles/70061/Architecture-Guide-ASP-NET-MVC-Framework-N-tier-En^0|0|0|0|0|A|0|0|T|0|0|0|12|1|0|0|T|2|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|16|8|@$H|17|I|18|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@]|9|@$H|1A|I|1B|1|1C]]|A|$]]|$1|N|3|O|5|6|7|1D|8|@]|9|@$H|1E|I|1F|1|1G]]|A|$]]|$1|P|3|Q|5|6|7|1H|8|@]|9|@$H|1I|I|1J|1|1K]]|A|$]]|$1|R|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]|Z|$5|U|V|W|A|$X|10]]|11|$5|U|V|W|A|$X|12]]]]

This is just a guess, but it seems like you are try to use a UI-based architectural pattern to build your business layer.

Typically, your models, views, and controllers are all maintained in the main web-app project. Any supporting functions (like your BL and DL) are added via class libraries. The Visual Studio MVC templates are built around that concept, which is why you had to manually add support with the GUID - and why it automatically creates the view.

If I may ask, why are you trying to build controllers into your BL? If you are trying to decouple your UI from your server code, perhaps WebAPI would be a better option.

UPDATE - A few helpful links

<a href="https://prodinner.codeplex.com/" rel="nofollow">ProDinner - ASP.NET MVC Sample App</a>

<a href="https://code.msdn.microsoft.com/Service-Layer-Entity-7a1fac6c" rel="nofollow">N Layered App with Entity Framework, Autofac, ASP.NET MVC and Unit Testing</a>

<a href="http://www.codeproject.com/Articles/70061/Architecture-Guide-ASP-NET-MVC-Framework-N-tier-En" rel="nofollow">Architecture Guide: ASP.NET MVC Framework + N-tier + Entity Framework and Many More</a>

blocks|key|1626172|text|你的大部分问题归结为使用脚手架。脚手架是伟大的，当你刚刚开始或为非常简单的项目，但它很快下降超过这一点。具体来说，通过脚手架添加控制器是为MVC项目设计的，因此它希望在MVC项目中找到您可以找到的东西。此外，它在Views中的适当目录中创建脚手架视图，因为这也是它设计的目的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1626173|那么，最简单的解决办法就是不要使用脚手架。控制器只是一个继承自Controller的类。那里没什么特别的。然后，您可以在想要创建视图的地方创建视图。|1626174|entityMap^0|2Y|5|0|V|A|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

Most of your issues boil down to using the scaffold. The scaffold is great when you're just starting out or for extremely simple projects, but it quickly falls down beyond that. Specifically, adding a controller via scaffold is designed for an MVC project, so it expects to find things you'd find in an MVC project. Additionally, it creates scaffolded views in an appropriate directory in <code>Views</code> because, again, that's what it's designed to do.

The simplest solution, then, is to just not use the scaffolds. A controller is just a class that inherits from <code>Controller</code>. Nothing special there. Then, you can create the views where you want to create them.

Visual Studio 2015 + all updates.
Asp .Net Web application (MVC).

I start off by adding a few class libraries and separating the Asp .Net WA into layers i.e. DataAccess, Business Logic and the web project itself.

Once separated I add relevant references and everything is working as I expect it to be (i.e. the application functions as it did before I separated it into layers).

In my BL (Controllers are found here). I don't have the option to Add a Controller, like you would when right clicking the Controllers folder in the default project, so add the below line

<pre><code>&lt;ProjectTypeGuids&gt;{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}&lt;/ProjectTypeGuids&gt;
</code></pre>

to the csproj file for my class library and the Add Controller option now appears. Create a controller but throws an error which was due to not having a web.config file - add this file and all works (although it would be nice to have this library working without a web.config file).

The problem I've hit is, when the Controller is created it also adds a View template within the class library but my Views folder is located in my web project.

Have I done this wrong? Is there a workaround so when a controller is created, it also creates the Views into the correct project? Or another approach for this?

Create Controller and add Views to another project

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

Visual 2015 +所有更新。.Net应用程序(MVC)。首先，我添加了几个类库，并将Asp .Net WA划分为各个层，即DataAccess、业务逻辑和web项目本身。一旦分离，我就添加相关的引用，所有的东西都像我期望的那样工作(也就是说，应用程序的功能就像我把它划分成层之前那样)。在我的BL (控制器在这里...

问创建控制器并向另一个项目添加视图
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问创建控制器并向另一个项目添加视图EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问创建控制器并向另一个项目添加视图
EN