文件名称:MVCDemo
- 所属分类：
- Windows编程
- 资源属性：
- [Windows] [Visual.Net] [源码]
- 上传时间：
- 2012-11-26
- 文件大小：
- 307kb
- 下载次数：
- 0次
- 提 供 者：
- china*****
- 相关连接：
- 无
- 下载说明：
- 别用迅雷下载，失败请重下，重下不扣分！
介绍说明－－下载内容均来自于网络，请自行研究使用
按我理解，这就是所说的三层架构了。
File工程负责最底层的文件操作
FileProtocol工程负责具体的流程及协议，将相关数据返回给界面层
UI工程就是具体的界面层了，他只负责显示具体的数据，不负责软件的工作流程。
File, FileProtocol这两个工程都是DLL，注意看一下FileProtocol的工程依赖及附加包含目录。还要再看一下UI工程的工程依赖及附加包含目录。在这里，三个工程，项目解决方案是在同级目录下，通过一个解决方案去包含三个工程。这样做的好处在于，工程可以重用。比如说File工程，他负责最底层的文件操作，以后我们的其它软件项目还会用到它的，因此，以后的项目，在解决方案里直接添加File工程便可以用了。 -According to my understanding, this is referred to a three-tier architecture.
File project is responsible for the bottom of the file operations
FileProtocol charge of the project specific processes and agreement to the relevant data back to the interface layer
UI project is a specific interface layer, and he is only responsible for display of specific data, is not responsible for the software workflow.
File, FileProtocol these two projects are DLL, note that the works look FileProtocol dependence and additional include directories. Would also like to look at what the engineering rely on UI and additional include directories. Here, the three projects, the project solution is at the same level directory, go through a solution contains three projects. The benefit of this is that the project can be reused. For example, File project, he was responsible for the bottom of the file operations, the other software projects the future we will use it, therefore, future projects, in the sol
File工程负责最底层的文件操作
FileProtocol工程负责具体的流程及协议，将相关数据返回给界面层
UI工程就是具体的界面层了，他只负责显示具体的数据，不负责软件的工作流程。
File, FileProtocol这两个工程都是DLL，注意看一下FileProtocol的工程依赖及附加包含目录。还要再看一下UI工程的工程依赖及附加包含目录。在这里，三个工程，项目解决方案是在同级目录下，通过一个解决方案去包含三个工程。这样做的好处在于，工程可以重用。比如说File工程，他负责最底层的文件操作，以后我们的其它软件项目还会用到它的，因此，以后的项目，在解决方案里直接添加File工程便可以用了。 -According to my understanding, this is referred to a three-tier architecture.
File project is responsible for the bottom of the file operations
FileProtocol charge of the project specific processes and agreement to the relevant data back to the interface layer
UI project is a specific interface layer, and he is only responsible for display of specific data, is not responsible for the software workflow.
File, FileProtocol these two projects are DLL, note that the works look FileProtocol dependence and additional include directories. Would also like to look at what the engineering rely on UI and additional include directories. Here, the three projects, the project solution is at the same level directory, go through a solution contains three projects. The benefit of this is that the project can be reused. For example, File project, he was responsible for the bottom of the file operations, the other software projects the future we will use it, therefore, future projects, in the sol
(系统自动生成,下载前可以参看下载内容)
下载文件列表
MVCDemo\bin\File.dll
.......\...\FileProtocol.dll
.......\...\UI.exe
.......\...\user.txt
.......\doc\说明文档.doc
.......\source\File\File.cpp
.......\......\....\File.h
.......\......\....\File.vcproj
.......\......\....\File.vcproj.YHTEAH-57DBC3A8.ＴｏＴｏ.user
.......\......\....Protocol\FileProtocol.vcproj
.......\......\............\FileProtocol.vcproj.YHTEAH-57DBC3A8.ＴｏＴｏ.user
.......\......\............\User.cpp
.......\......\............\User.h
.......\......\Solution\Debug\File.dll
.......\......\........\.....\File.exp
.......\......\........\.....\File.lib
.......\......\........\.....\FileProtocol.dll
.......\......\........\.....\FileProtocol.exp
.......\......\........\.....\FileProtocol.lib
.......\......\........\.....\UI.exe
.......\......\........\Solution.sln
.......\......\........\Solution.suo
.......\......\UI\ReadMe.txt
.......\......\..\res\UI.ico
.......\......\..\...\UI.rc2
.......\......\..\resource.h
.......\......\..\stdafx.cpp
.......\......\..\stdafx.h
.......\......\..\targetver.h
.......\......\..\UI.APS
.......\......\..\UI.cpp
.......\......\..\UI.h
.......\......\..\UI.rc
.......\......\..\UI.vcproj
.......\......\..\UI.vcproj.YHTEAH-57DBC3A8.ＴｏＴｏ.user
.......\......\..\UIDlg.cpp
.......\......\..\UIDlg.h
.......\......\..\user.txt
.......\......\File\Debug
.......\......\....Protocol\Debug
.......\......\Solution\Debug
.......\......\UI\Debug
.......\......\..\res
.......\......\File
.......\......\FileProtocol
.......\......\Solution
.......\......\UI
.......\bin
.......\doc
.......\source
MVCDemo
.......\...\FileProtocol.dll
.......\...\UI.exe
.......\...\user.txt
.......\doc\说明文档.doc
.......\source\File\File.cpp
.......\......\....\File.h
.......\......\....\File.vcproj
.......\......\....\File.vcproj.YHTEAH-57DBC3A8.ＴｏＴｏ.user
.......\......\....Protocol\FileProtocol.vcproj
.......\......\............\FileProtocol.vcproj.YHTEAH-57DBC3A8.ＴｏＴｏ.user
.......\......\............\User.cpp
.......\......\............\User.h
.......\......\Solution\Debug\File.dll
.......\......\........\.....\File.exp
.......\......\........\.....\File.lib
.......\......\........\.....\FileProtocol.dll
.......\......\........\.....\FileProtocol.exp
.......\......\........\.....\FileProtocol.lib
.......\......\........\.....\UI.exe
.......\......\........\Solution.sln
.......\......\........\Solution.suo
.......\......\UI\ReadMe.txt
.......\......\..\res\UI.ico
.......\......\..\...\UI.rc2
.......\......\..\resource.h
.......\......\..\stdafx.cpp
.......\......\..\stdafx.h
.......\......\..\targetver.h
.......\......\..\UI.APS
.......\......\..\UI.cpp
.......\......\..\UI.h
.......\......\..\UI.rc
.......\......\..\UI.vcproj
.......\......\..\UI.vcproj.YHTEAH-57DBC3A8.ＴｏＴｏ.user
.......\......\..\UIDlg.cpp
.......\......\..\UIDlg.h
.......\......\..\user.txt
.......\......\File\Debug
.......\......\....Protocol\Debug
.......\......\Solution\Debug
.......\......\UI\Debug
.......\......\..\res
.......\......\File
.......\......\FileProtocol
.......\......\Solution
.......\......\UI
.......\bin
.......\doc
.......\source
MVCDemo