Enterprise Solution 管理软件开发框架流程实战
1 定义模块和功能
执行系统功能(SAUTSF),在系统主文件(System Master File SAMF)模块中增加功能SAMFEM,Employee Master。
给有权限的用户组分配功能SAMFEM的权限,包含新增,删除,修改,打印,过帐权限,这是功能权限。
如果需要增加字段权限,比如可以编辑员工薪资字段,应该修改用户表(User)增加权限字段。
2 定义导航菜单
把增加的功能放置到合适的功能菜单中,菜单项的位置根据需要而定。比如员工主文件,可以放置到主档定义中,还可以放置一份到人事管理的设定菜单项中。定义一个菜单项位置,系统会生成三个地方的导航菜单项:标题栏下的主菜单(ToolStrip), 导航树右边的列表视图(ListView),导航图的上下文菜单(ContextMenu),三种方式帮助用户快速查找与执行功能。
3 设计数据库表
以员工表为例子,员工表的数据库脚本如下:
CREATE TABLE [dbo].[Employee]
(
[Recnum] [numeric] (18, 0) NOT NULL IDENTITY(1, 1),
[EmployeeNo] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[Department] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[ProductionGroup] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[CompanyCode] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[BranchCode] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[Name] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[Account] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[Password] [nvarchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[Gender] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[Birthday] [datetime] NULL,
[Mobile] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[Address] [nvarchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[HomeTelephone] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[Post] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[Type] [char] (4) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[Suspended] [char] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL CONSTRAINT [DF__tEmployee__Enabl__32CB82C6] DEFAULT ((1)),
[JobTitle] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[JoinDate] [datetime] NULL,
[LeftDate] [datetime] NULL,
[Photo] [image] NULL
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO
ALTER TABLE [dbo].[Employee] WITH NOCHECK ADD CONSTRAINT [CKC_TYPE_TEMPLOYE] CHECK (([Type]=(1) OR [Type]=(0)))
GO
ALTER TABLE [dbo].[Employee] ADD CONSTRAINT [PK_TEMPLOYEE] PRIMARY KEY CLUSTERED ([EmployeeNo]) ON [PRIMARY]
GO
ALTER TABLE [dbo].[Employee] WITH NOCHECK ADD CONSTRAINT [FK_Employee_Department] FOREIGN KEY ([Department]) REFERENCES [dbo].[Department] ([DepartmentCode])
GO
ALTER TABLE [dbo].[Employee] NOCHECK CONSTRAINT [FK_Employee_Department]
GO
4 LLBL Gen Pro生成实体映射
执行程序LLBL Gen Pro,连接到数据库并添加Employee数据表,最后点击生成源代码文件。

一般情况下用默认的命名规则即可。比如Item_No映射的实体字段名是ItemNo,默认去掉下划线。
5 实体数据访问接口与实现生成
用Template目录中的Code Smith模板生成接口与实现类,代码如下:
数据接口类:
public interface IEmployeeManager
{
EmployeeEntity GetEmployee(System.String EmpNo);
EmployeeEntity GetEmployee(System.String EmpNo, IPrefetchPath2 prefetchPath);
EmployeeEntity GetEmployee(System.String EmpNo, IPrefetchPath2 prefetchPath, ExcludeIncludeFieldsList fieldList); EntityCollection GetEmployeeCollection(IRelationPredicateBucket filterBucket);
EntityCollection GetEmployeeCollection(IRelationPredicateBucket filterBucket, ISortExpression sortExpression);
EntityCollection GetEmployeeCollection(IRelationPredicateBucket filterBucket, ISortExpression sortExpression, IPrefetchPath2 prefetchPath);
EntityCollection GetEmployeeCollection(IRelationPredicateBucket filterBucket, ISortExpression sortExpression, IPrefetchPath2 prefetchPath, ExcludeIncludeFieldsList fieldList); EmployeeEntity SaveEmployee(EmployeeEntity employee);
EmployeeEntity SaveEmployee(EmployeeEntity employee, EntityCollection entitiesToDelete);
EmployeeEntity SaveEmployee(EmployeeEntity employee, EntityCollection entitiesToDelete, string seriesCode); void DeleteEmployee(EmployeeEntity employee); bool IsEmployeeExist(System.String EmpNo);
bool IsEmployeeExist(IRelationPredicateBucket filterBucket);
int GetEmployeeCount(IRelationPredicateBucket filterBucket); EmployeeEntity CloneEmployee(System.String EmpNo);
void PostEmployee(System.String EmpNo);
void PostEmployee(EmployeeEntity employee);
}
数据实现类:
[RemoteService("EmployeeManager")]
public class EmployeeManager : Foundation.Common.ManagerBase, IEmployeeManager
{
public EmployeeEntity GetEmployee(System.String EmpNo)
{
IPrefetchPath2 prefetchPath = new PrefetchPath2((int)EntityType.EmployeeEntity);
prefetchPath.Add(EmployeeEntity.PrefetchPathEmployeeTrainings);
return GetEmployee(EmpNo, prefetchPath);
}
public EmployeeEntity GetEmployee(System.String EmpNo, IPrefetchPath2 prefetchPath)
{
return GetEmployee(EmpNo, prefetchPath, null);
}
public EmployeeEntity GetEmployee(System.String EmpNo, IPrefetchPath2 prefetchPath, ExcludeIncludeFieldsList fieldList)
{
EmployeeEntity employee = new EmployeeEntity(EmpNo);
using (DataAccessAdapterBase adapter = GetCompanyDataAccessAdapter())
{
bool found = adapter.FetchEntity(employee, prefetchPath, null, fieldList);
if (!found) throw new Foundation.Common.RecordNotFoundException("Invalid Employee");
}
return employee;
}
public EntityCollection GetEmployeeCollection(IRelationPredicateBucket filterBucket)
{
return GetEmployeeCollection(filterBucket, null);
}
public EntityCollection GetEmployeeCollection(IRelationPredicateBucket filterBucket, ISortExpression sortExpression)
{
return GetEmployeeCollection(filterBucket, sortExpression, null);
}
public EntityCollection GetEmployeeCollection(IRelationPredicateBucket filterBucket, ISortExpression sortExpression, IPrefetchPath2 prefetchPath)
{
return GetEmployeeCollection(filterBucket, sortExpression, prefetchPath, null);
}
public EntityCollection GetEmployeeCollection(IRelationPredicateBucket filterBucket, ISortExpression sortExpression, IPrefetchPath2 prefetchPath, ExcludeIncludeFieldsList fieldList)
{
EntityCollection employeeCollection = new EntityCollection(new EmployeeEntityFactory());
using (DataAccessAdapterBase adapter = GetCompanyDataAccessAdapter())
{
adapter.FetchEntityCollection(employeeCollection, filterBucket, 0, sortExpression, prefetchPath, fieldList);
}
return employeeCollection;
}
public EmployeeEntity SaveEmployee(EmployeeEntity Employee)
{
return SaveEmployee(Employee, null);
}
public EmployeeEntity SaveEmployee(EmployeeEntity Employee, EntityCollection entitiesToDelete)
{
return SaveEmployee(Employee, entitiesToDelete, string.Empty);
}
public EmployeeEntity SaveEmployee(EmployeeEntity Employee, EntityCollection entitiesToDelete, string seriesCode)
{
using (DataAccessAdapterBase adapter = GetCompanyDataAccessAdapter())
{
try
{
adapter.StartTransaction(IsolationLevel.ReadCommitted, "SaveEmployee");
adapter.SaveEntity(Employee, true, false);
IEmployeeTrainingManager trainingManager = ClientProxyFactory.CreateProxyInstance<IEmployeeTrainingManager>();
foreach (var employeeTraining in Employee.EmployeeTrainings)
{
trainingManager.SaveEmployeeTraining(employeeTraining);
}
adapter.Commit();
}
catch
{
adapter.Rollback();
throw;
}
}
return Employee;
}
public void DeleteEmployee(EmployeeEntity Employee)
{
using (DataAccessAdapterBase adapter = GetCompanyDataAccessAdapter())
{
if (!adapter.IsEntityExist<EmployeeEntity>(Employee))
return;
try
{
adapter.StartTransaction(IsolationLevel.ReadCommitted, "DeleteEmployee");
IEmployeeTrainingManager trainingManager = ClientProxyFactory.CreateProxyInstance<IEmployeeTrainingManager>();
foreach (var employeeTraining in Employee.EmployeeTrainings)
{
trainingManager.DeleteEmployeeTraining(employeeTraining);
}
adapter.DeleteEntity(Employee);
adapter.Commit();
}
catch
{
adapter.Rollback();
throw;
}
}
}
public bool IsEmployeeExist(System.String EmpNo)
{
RelationPredicateBucket filterBucket = new RelationPredicateBucket();
filterBucket.PredicateExpression.Add(EmployeeFields.EmployeeNo == EmpNo);
return IsEmployeeExist(filterBucket);
}
public bool IsEmployeeExist(IRelationPredicateBucket filterBucket)
{
return (GetEmployeeCount(filterBucket) > 0);
}
public int GetEmployeeCount(IRelationPredicateBucket filterBucket)
{
using (DataAccessAdapterBase adapter = GetCompanyDataAccessAdapter())
{
return adapter.GetDbCount<EmployeeEntity>(filterBucket);
}
}
public EmployeeEntity CloneEmployee(System.String EmpNo)
{
EmployeeEntity source = this.GetEmployee(EmpNo);
EmployeeEntity employee = (EmployeeEntity)CloneEntity(source);
return employee;
}
public void PostEmployee(System.String EmpNo)
{
return;
}
public void PostEmployee(EmployeeEntity Employee)
{
return;
}
}
6 界面设计,控件数据绑定,查找与钻取
Windows窗体设计的主要流程步骤
1) 拖一个EntityCollection组件到界面中,这个组件来自于LLBL Gen Pro生成的数据库映射项目。
设置EntityFactoryToUse=Kingston.FactoryClasses.EmployeeEntityFactory。
2) 拖多个BindingSource组件到界面。每一层控件都需要一个BindingSource组件,如果界面是单笔数据操作,还需要拖一个空的BindingSource组件到界面中,并将它设为窗体的NavigatorBindingSource。
3) 依次绑定控件与数据源组件的属性。要注意选对控件,TextEditor,NumbericEditor。对于必须输入值的控件,要设置Required=true,对于映射到主键字段的控件,要设AutoFind=true。
4) 给控件增加查找与钻取。
5) 设置控件的tab index。

7 验证和计算逻辑
1) 增加实体属性的默认值。修改文件EmployeeEntity.Implementation.cs
public partial class EmployeeEntity
{
protected override void OnInitialized()
{
base.OnInitialized(); // Assign default value for new entity
if (Fields.State == EntityState.New)
{
#region DefaultValue // __LLBLGENPRO_USER_CODE_REGION_START DefaultValue
this.Fields[(int) EmployeeFieldIndex.Suspended].CurrentValue = false;
// __LLBLGENPRO_USER_CODE_REGION_END #endregion
2) 增加自动带值。比如输入员工所在的部门编码,要自动带入部门名称。
private void OnChangeDepartment(string originalValue)
{
IDepartmentManager departmentManager =CreateProxyInstance<IDepartmentManager>();
if (departmentManager.IsDepartmentExist(Department))
{
ExcludeIncludeFieldsList fieldList = new ExcludeIncludeFieldsList(false);
fieldList.Add(DepartmentFields.FullName);
DepartmentEntity department = departmentManager.GetDepartment(Department, null, fieldList);
this.DepartmentName = department.FullName;
}
}
3) 增加验证代码,对需要验证的属性值进行验证。
值验证:
public override bool ValidateFieldValue(IEntityCore involvedEntity, int fieldIndex, object value)
{
bool result = base.ValidateFieldValue(involvedEntity, fieldIndex, value); if (!result) return false;
switch ((EmployeeFieldIndex)fieldIndex)
{
case EmployeeFieldIndex.Department:
return ValidateDepartment((string)value, (EmployeeEntity)involvedEntity);
break;
private bool ValidateDepartment(string value, EmployeeEntity EGEntity)
{
if (!string.IsNullOrWhiteSpace(value))
{
IDepartmentManager departmentManager = CreateProxyInstance<IDepartmentManager>();
departmentManager.ValidateDepartment(value);
}
return true;
}
删除验证:
public override void ValidateEntityBeforeDelete(IEntityCore involvedEntity)
{
base.ValidateEntityBeforeDelete(involvedEntity);
EmployeeEntity employeeEntity = (EmployeeEntity)involvedEntity;
ISalesmanManager salesmanManager = CreateProxyInstance<ISalesmanManager>(); RelationPredicateBucket filterBucket = new RelationPredicateBucket();
filterBucket.PredicateExpression.Add(SalesmanFields.EmployeeNo == employeeEntity.EmployeeNo);
if (salesmanManager.IsSalesmanExist(filterBucket))
{
throw new FieldValidationException("Employee No. already used in salesman");
}
保存前验证:
public override void ValidateEntityBeforeSave(IEntityCore involvedEntity)
{
base.ValidateEntityBeforeSave(involvedEntity);
EmployeeEntity employeeEntity = (EmployeeEntity)involvedEntity; if (string.IsNullOrWhiteSpace(employeeEntity.EmployeeNo))
{
throw new EntityValidationException("Employee No. is required");
}
8 生成并发布程序
打开Visual Studio 2015或用MSBUILD生成程序。

执行.NET Reactor批处理脚本,将生成的文件复制到客户的更新服务器中。
Enterprise Solution 管理软件开发框架流程实战的更多相关文章
- Enterprise Solution 企业管理软件开发框架
Enterprise Solution 开源项目资源汇总 Visual Studio Online 源代码托管 企业管理软件开发框架 Enterprise Solution 是一套管理软件开发框架,在 ...
- Enterprise Solution 应用程序开发框架培训
一.系统架构 C# .NET 4.0 + Win Form + SQL Server 2005 二.五大核心模块 (菜单设计器Menu Designer,查询设计器Query Designer,报表设 ...
- Enterprise Solution 3.1 企业应用开发框架 .NET ERP/CRM/MIS 开发框架,C/S架构,SQL Server + ORM(LLBL Gen Pro) + Infragistics WinForms
行业:基于数据库的制造行业管理软件,包含ERP.MRP.CRM.MIS.MES等企业管理软件 数据库平台:SQL Server 2005或以上 系统架构:C/S 开发技术 序号 领域 技术 1 数据库 ...
- Enterprise Solution 开源项目资源汇总 Visual Studio Online 源代码托管 企业管理软件开发框架
Enterprise Solution 是一套管理软件开发框架,在这个框架基础上开发出一套企业资源计划系统Enterprise Edition. 现将Enterprise Solution开发过程中遇 ...
- Enterprise Solution 企业资源计划管理软件 C/S架构,支持64位系统,企业全面应用集成,制造业信息化
Enterprise Solution是一套完整的企业资源计划系统,功能符合众多制造业客户要求.系统以.NET Framework技术作为开发架构,完善的功能可有效地帮助企业进行运营策划,减低成本,如 ...
- 从国内流程管理软件市场份额看中国BPM行业发展
随着互联网+.中国制造2025.工业4.0等国家战略的支持与引导,企业在数字经济时代的信息化表现惊人,越来越多企业认识到,对于企业的发展来说,信息自动化远远还不够,企业的战略.业务和IT之间需保持高度 ...
- 流程及迭代驱动测试管理软件, itest 发布到开源中国
itest 源码已发布到码云 ,项目已被开源中国收录!详见 https://www.oschina.net/p/itest-cn 测试人自己开发,汇聚10年沉淀,独创流程驱动测试.度量展现测试人价值 ...
- Enterprise Solution 界面设计规范
Enteprise Solution有一套自己的界面设计规范,也是很多年(10年以上)管理软件界面精华的积累.没有一个软件从一开始就很善于界面设计,许多个小小的改善,比如控件位置的移动,控件摆放顺序的 ...
- 仿OpenStack开发云计算管理软件
仿OpenStack开发云计算管理软件 使用Python语言开发一套类似OpenStack的云计算管理平台LouCloud,具备基本的用户,服务器,镜像与 虚拟机管理功能,学习IaaS,虚拟化,Lib ...
随机推荐
- Java 线程
线程:线程是进程的组成部分,一个进程可以拥有多个线程,而一个线程必须拥有一个父进程.线程可以拥有自己的堆栈,自己的程序计数器和自己的局部变量,但不能拥有系统资源.它与父进程的其他线程共享该进程的所有资 ...
- CSS 选择器及各样式引用方式
Css :层叠样式表 (Cascading Style Sheets),定义了如何显示HTML元素. 目录 1. 选择器的分类:介绍ID.class.元素名称.符合.层次.伪类.属性选择器. 2. 样 ...
- Entity Framework 教程——Entity Framework中的实体类型
Entity Framework中的实体类型 : 在之前的章节中我们介绍过从已有的数据库中创建EDM,它包含数据库中每个表所对应的实体.在EF 5.0/6.0中,存在POCO 实体和动态代理实体两种. ...
- 程序员必须要知道的Hadoop的一些事实
程序员必须要知道的Hadoop的一些事实.现如今,Apache Hadoop已经无人不知无人不晓.当年雅虎搜索工程师Doug Cutting开发出这个用以创建分布式计算机环境的开源软...... 1: ...
- org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.jca:service=LocalTxCM,name=egmasDS
17:34:37,235 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 17:34:37,281 INFO [ ...
- Conversion to Dalvik format failed: Unable to execute dex: Multiple dex files define ...
Conversion to Dalvik format failed: Unable to execute dex: Multiple dex files define ... 这个错误是因为有两个相 ...
- 图解DevExpress RichEditControl富文本的使用,附源码及官方API
9点半了,刚写到1.2. 该回家了,明天继续写完. 大家还需要什么操作,留言说一下,没有的我明天继续加. 好久没有玩DevExpress了,今天下载了一个玩玩,发现竟然更新到14.2.5了..我去 ...
- 自定义ConfigSection
CCustom configuration section with intelisense
- Android快乐贪吃蛇游戏实战项目开发教程-06虚拟方向键(五)绘制方向键箭头
本系列教程概述与目录:http://www.cnblogs.com/chengyujia/p/5787111.html本系列教程项目源码GitHub地址:https://github.com/jack ...
- jetBrain系列软件
请尽量支持正版软件!https://www.jetbrains.com/ 本文仅供参考 以下提供一种方法可以无限期体验JetBrain2016系列软件. 1.下载JetbrainsCrack-2.5. ...