blocks|key|229882|text|好吧，试着下载一些已经存在的开源项目。其中一个相当复杂，但如果你能理解它，那就非常酷了--+orchard|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|229883|最佳实践是将此逻辑移动到DAL+(数据访问层)或BLL(业务逻辑层)。取决于应用程序的复杂性。|229884|entityMap|0|LINK|mutability|MUTABLE|url|http://www.orchardproject.net/^0|1A|7|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Well, try to download some already existing opensource projects. One of them is rather complex, but very cool if you'll get understanding of it - <a href="http://www.orchardproject.net/" rel="nofollow">orchard</a>

The best practice is moving this logic to DAL (data access layer) or BLL(business logics layers). Depends on complexity of your application.

blocks|key|228270|text|我建议从this+tutorial开始。它首先使用EF代码，但如果您愿意，您可以简单地用普通的edmx模型文件夹替换代码优先DbContext+(提示：ObjectContext文件夹)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|228271|App_Code是特定于网站项目的。国际海事组织，这是一个可怕的方式来组织所有的网站，除了最简单的。MVC项目是一个Web应用程序项目，所以没有App_Code，您的类几乎可以在任何地方定义。|228272|entityMap|0|LINK|mutability|MUTABLE|url|http://www.asp.net/mvc/tutorials/getting-started-with-aspnet-mvc3^0|1Q|9|24|D|4|D|0|0|0|8|20|8|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

I'd recommend starting with <a href="http://www.asp.net/mvc/tutorials/getting-started-with-aspnet-mvc3" rel="nofollow">this tutorial</a>. It uses EF code first, but you can simply replace the code first <code>DbContext</code> with a normal edmx <code>ObjectContext</code> if you wish (hint: Models folder).

<code>App_Code</code> is specific to Web Site Projects. IMO, its a terrible way to organize all but the simplest of web sites. An MVC project is a Web Application Project, so there is no <code>App_Code</code> and your classes can be defined pretty much anywhere.

blocks|key|3097151|text|App_Code在网站项目中是必需的，因为它有特殊的含义。它的意思是“不要将这些文件提供给web浏览器”。在ASP.NET+MVC中，文件在大多数情况下不直接提供给浏览器，因此App_Code不是必需的。您可以随心所欲地将代码文件放在您想要的任何文件夹中，因为这些文件被编译成DLL，通常不会发布到网站本身。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3097152|使用独立库也是一个很好的解决方案。|3097153|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

App_Code is necessary in Web Site projects because it has a special meaning. It means "Don't serve these files to a web browser". In ASP.NET MVC, files are not directly served to the browser in most cases, so App_Code is not necessary. You can place code files whereever you want, in any folder you want because these files are compiled into a DLL and not typically published to the website itself.

Using a stand-alone library is also a fine solution.

blocks|key|3097165|text|我也有同样的问题，我的类Utility.cs在我的MVC项目中没有被识别。我将构建操作"Content“更改为"Compile”，这解决了我的问题。希望这能有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3097166|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same issue, my class Utility.cs was not recognized inside my MVC project. I changed the Build Action "Content" to "Compile" and that solved my problem.
Hope that helps.

blocks|key|3097255|text|对于那些不想要第二个项目/类库，只想要一个简单的文件夹来存放几个c#类的人，我建议使用“App_Classes”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3097256|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For those who don’t want a second project/class library and just want a simple folder for a few c# classes, I propose “App_Classes”.

blocks|key|2883230|text|没有人真正解释为什么App_Code一开始就存在。它是您放置代码文件以获得动态编译(在运行时)的地方。这就是App_Code的首要原因，也是它特别的原因。你可以把代码放在任何你想要的文件夹中，但是你必须用编译动作来标记它来编译，而在App_Code中这是不必要的，事实上，App_Code中的大多数文件甚至都不是项目的一部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2883231|它也适用于ASP.NET+MVC项目，你只需要用.cshtml扩展名来命名你的代码文件即可。|2883232|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

No one really explains why App_Code exists in the first place. It's the place where you put code files to get dynamic compilation (at runtime). That's the number one reason for App_Code and why it is special. You can put code in any folder you want but you will have to mark it with Compile action to compile while in App_Code that is not necessary, in fact, most files in App_Code aren't even a part of a project.

It does work in ASP.NET MVC projects too you just have to name your code files with .cshtml extension.

In ASP.NET Webform, <code>App_Code</code> is standard folder to putting code and using it at run-time.But I think this folder is kind of different in ASP.NET MVC, my question is:

<ul>
<li>where should I put my code ( Extension methods , Helpers , ... ) in ASP.NET MVC. When I store code in <code>App_Code</code> folder, I can't use theme in <code>controller</code> but they work fine in <code>views</code>.</li>
<li>About Entity Framework, the same question, where should I put edmx and tt files. I'm not using Code-First</li>
</ul>

Update:

After some search, finally I created a new Class Library project in my solution, code is available in all <code>controllers</code> and <code>views</code>. I still don't know why the code in <code>App_Code</code> is not available in controller

ASP.NET MVC 3 and App_Code folder

在ASP.NET Webform中，App_Code是放置代码并在运行时使用的标准文件夹，但我认为这个文件夹在ASP.NET MVC中有些不同，我的问题是：我应该把我的代码放在哪里(扩展方法，帮助器，... )在ASP.NET MVC中。当我将代码存储在App_Code文件夹中时，我不能在controller中使用主题...

问ASP.NET MVC 3和App_Code文件夹
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET MVC 3和App_Code文件夹EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET MVC 3和App_Code文件夹
EN