刚办下了签证，寻同行人，定相同航班一起走。
如果已经办妥了签证，请大家登记一下联系方式，定机票时大家可以一起定

 我的联系方式：

朱晔 13651657101

上海徐汇区

mail powerzhuye@citiz.net

msn lovecherry_1983@hotmail.com

我的航班

 

4月12日 (星期六)

航班: Northwest Airlines #26

出发: Shanghai Pudong International Airport, 中国 (PVG) 4月12日(星期六) 10:00 AM

到达: Tokyo Narita, 日本 (NRT) 4月12日(星期六) 1:55 PM

舱位: 经济舱

4月12日 (星期六)

航班: Northwest Airlines #8

出发: Tokyo Narita, 日本 (NRT) 4月12日(星期六) 3:25 PM

到达: Seattle/Tacoma Intl, WA (SEA) 4月12日(星期六) 8:15 AM

舱位: 经济舱

4月18日 (星期五)

航班: Northwest Airlines #2120 (由HORIZON AIR运营)

出发: Seattle/Tacoma Intl, WA (SEA) 4月18日(星期五) 12:00 PM

到达: Portland International Airport, OR (PDX) 4月18日(星期五) 12:50 PM

舱位: 经济舱

4月18日 (星期五)

航班: Northwest Airlines #5

出发: Portland International Airport, OR (PDX) 4月18日(星期五) 2:35 PM

到达: Tokyo Narita, 日本 (NRT) 4月19日(星期六) 4:55 PM

舱位: 经济舱

4月19日 (星期六)

航班: Northwest Airlines #25

出发: Tokyo Narita, 日本 (NRT) 4月19日(星期六) 6:35 PM

到达: Shanghai Pudong International Airport, 中国 (PVG) 4月19日(星期六) 8:55 PM

舱位: 经济舱

Exception Management in .NET阅读笔记

       今天阅读了《Exception Management in .NET》一文，虽然是老文章了，但是其中的一些理念不但正确而且非常有价值。我比较懒，直接把要点复制出来了，呵呵。

异常管理

Ø         An exception management system should be well encapsulated and should abstract the details of logging and reporting from the application’s business logic.

Ø         Exceptions represent a breach of an implicit assumption made within code.

Ø         Exceptions are not necessarily errors.

Ø         You should derive your custom application exceptions from ApplicationException.

异常检测

You should only catch exceptions when you need to specifically perform any of the

following actions:

Ø         Gather information for logging

Ø         Add any relevant information to the exception

Ø         Execute cleanup code

Ø         Attempt to recover

适当使用异常

Throwing exceptions is more expensive than simply returning a result to a caller. Therefore they should not be used to control the normal flow of execution through your code. In addition, excessive use of exceptions can create unreadable and unmanageable code.

异常传播

There are three main ways to propagate exceptions:

Ø         Let the exception propagate automatically：With this approach, you do nothing and deliberately ignore the exception.

Ø         Catch and rethrow the exception：With this approach, you catch and react to the exception, and clean up or perform any other required processing within the scope of the current method. If you cannot recover from the exception, you rethrow the same exception to your caller.

catch(TypeAException e) { // Code to do any processing needed. // Rethrow the exception throw; }

Ø         Catch, wrap, and throw the wrapped exception：If you cannot recover, wrap the exception in a new exception, and throw the new exception back to the caller. The InnerException property of the Exception class explicitly allows you to preserve a previously caught exception. This allows the original exception to be wrapped as an inner exception inside a new and more relevant outer exception.

catch(TypeBException e) { // Code to do any processing needed. // Wrap the current exception in a more relevant // outer exception and rethrow the new exception. throw(new TypeCException(strMessage, e)); }

       Note:As the exception propagates up the call stack, catch blocks can only catch the outer exception. Inner exceptions are programmatically accessible through the InnerException property, but they cannot be matched to a catch block.

什么时候使用内部异常

For example, consider a hypothetical method called LoadUserInfo. This method may load a user’s information from a file that is assumed to exist when the method Exception Management in .NET 9 tries to access it. If the file does not exist, a FileNotFoundException is thrown,which has meaning within the context of the LoadUserInfo method. However, as the exception propagates back up the call stack—for example, to a LogonUser method—a FileNotFoundException exception does not provide any valuable information. If you wrap the FileNotFoundException in a custom exception class (discussed later in this document)—for example, one called FailedToLoadUserInfoException—and throw the wrapper exception, it provides more information and is more relevant to the calling LogonUser method. You can then catch the FailedToLoadUserInfoException exception in the LogonUser method and react to that particular exception type rather than having to catch the FileNotFoundException, which is an implementation detail of another method.

自定义异常

This hierarchy allows your application to benefit from the following:

Ø         Easier development because you can define properties and methods on your base application exception class that can be inherited by your other application exception classes.

Ø         New exception classes created after your application has been deployed can derive from an existing exception type within the hierarchy. Existing exception handling code that catches one of the base classes of the new exception object will catch the new exception without any modifications to the existing code, interpreting it as one of the object’s base classes.

You should only create a new application exception class for an exception type that you need to react to and handle within your code that is not already available in your application exception hierarchy or in the Framework.

管理未处理异常

Ø         You should configure exception management settings within your application’s Web.config file.

<customErrors defaultredirect="http://hostname/error.aspx" mode="on"> <error statuscode="500" redirect="/errorpages/servererror.aspx" /> <error statuscode="404" redirect="/errorpages/filenotfound.htm" /> </customErrors>

Ø         You should be aware that these settings only apply to ASP.NET files (that is, files with specific extensions, such as .aspx and .asmx).

Ø         Page_Error：Page.Error += new System.EventHandler(Page_Error);

Ø         Application_Error：

protected void Application_Error(Object sender, EventArgs e) { Exception exc = Server.GetLastError(); // Perform logging, send any notifications, etc. }

       补充一个，对于网站程序，我们是使用HttpModule来处理未处理异常的，非常方便。

目前公司第一款游戏<纸客帝国>即将公测,第二款游戏也将在年内上市,我们需要您的加入,一起创造麦格特尔的辉煌明天.

运营平台: www.qwd1.com

公司官网: www.magicgrids.com

地    址： 宜山路829号201-210室

邮政编码： 200233

联 系 人： 刘小姐

电子信箱： hr@MagicGrids.com

C++软件开发工程师

工作职责：

1. 从事网络游戏软件项目的开发

2. 从事与项目有关的工具软件的开发。

岗位要求：

1. 计算机或相关专业毕业，本科以上学历，硕士以上学位者优先。

2. 有两年以上相关工作经验，有游戏软件开发经验者优先。

3. 有以下一项或多项专业知识或经验者优先：

a) 了解多种网络协议，精通TCP/IP协议.

b) 熟悉游戏引擎的基本架构，了解游戏制作的基本流程.

c) 熟悉MFC

4. 熟练掌握C/C++等语言，有3年以上相关编程经验者优先。

5. 良好的英语读写能力，大学英语4级以上

6. 具备以结果为导向的工作能力，能合理安排好分配的工作任务并按时完成。

7. 具备团队合作精神。

.NET软件工程师

职位描述：

1.     网络游戏相关运营网站的开发和维护。

2.     网络游戏相关运营工具的开发和维护。

3.     开发基于.NET 2.0和SQL Server 2005平台。

职位要求：

1.     一年以上ASP.NET开发经验，或是5个以上ASP.NET项目开发经验。

2.     熟悉网站开发流程，包括策划、需求、设计、开发、部署以及维护等。

3.     熟悉C#、ASP.NET、Web服务、.NET Remoting、JS、HTML、Windows服务、CSS、AJAX等技术。

4.     熟悉SQL Server 2005的存储过程、触发器、索引、视图、事务等技术。

5.     了解COM+、设计模式、.NET框架、ASP.NET框架、ORM技术等。

6.     对.NET相关技术有学习热情，学习能力强。

7.     工作认真负责、主观能动性强

8.     有一定的技术文档书写能力。

9.     具备良好的表达和沟通的能力。

10.  具备极强的团队精神和合作精神。

11.  对工作有热情，能够在一定压力下工作。