Question

仅读到使用密码档案材料的可能性。 bpx.cs, 而不是网络应用项目中的密码()。显然,这只是造成档案在装上该页时才编造的,它不会再comp(右吗?)。

是否有消极或意想不到的副作用,使用密码,而不是在网络应用项目中编码?

Answer 1

我认为,如果贵国的场址一无所有,你可能会遇到支持问题。 (《民法》或《刑法》)

i.e. 如果你试图在生产现场提出一个问题,即你处理的错误告诉你属于某个档案或名称空间,那么你必须停止检查你支持的每个档案和控制,然后才能发现该网页是作为汇编的组件的一部分运行还是从现场的密码操作。

如果你试图有好坏的环境,你也会陷入冲突或消失的地名空间。

参看《刑法》:

Your production source code can sit on your production website. If the code is all compiled in a DLL in your bin directory, there is no absolute guarantee that the code you have on your development environment or source control is what s out there. (Sure it SHOULD be, but if everything was always as it should be, many of us wouldn t have jobs fixing other people s code!)
For updates, you only have to push out single files, not an entire assembly.
You would be able to have developments in progress on other pages that you don t need to back out before recompiling and publishing to production.

意见:

Since you re not pushing out a compiled assembly, you may have errors within individual files, that won t necessarily be caught unless someone visits each specific page or if you are sure to compile before deploying.
You may have conflicting namespaces in codefiles that may never be caught and could cause confusion or errors.
Performance issues for dynamic compilation