名古屋纪行 3

今天是周六。

昨天日本同事给了几张名古屋这边一个古迹博物馆(明治村)的门票,于是,在 Penny 的带领下,还有 Colin 三人一起到那边走了一遭。

去的路上不太顺,一开始坐错了车,乘过了头,去到了一个分岔口的错误的一个方向上。退回,重新上车。结果一不小心又上错了车,去了同一个错的地方。有劲,就当是乘车玩了。那种比较慢的红色外壳的车。退回,重新上车,最终乘对了。到了犬山站,又乘了二十分的公车,到了。

终于算不虚此行,天气晴朗,蓝天白云,满山的枫叶正当红。三个人开开心心地游玩了所有景点,感叹又一世外桃源。如果能住在这样一个地方该是多么爽的事情。最喜欢有几处景致,可以透过红色的枫树,望见一潭碧蓝的湖水,偶飞的鸟,几点舟,和湖另一边的远山。一颗轻松的心,和想要与人分享的情绪。不考虑其他因素,这真是绝妙的一处。可是,人生又怎么能不考虑其他因素呢?

然而,这一刻,我一定要做回我自己。

晚上,周五推迟的聚会终于启动。几位同胞,老王,老金及其老婆,小郭,去到一家蒙古餐馆。大碗喝酒,大块吃肉,大声聊天。特开心。最后,大家穿上蒙古族的服装纷纷合影,真是开心。很久没有这么放松自己了。

希望这种状态一直保持。不就是做回自己嘛。

P.S. 发现很久不写东西以后,完全不记得文法是什么东西了。

名古屋纪行 3

名古屋纪行 2

本打算至少每天记点流水帐的,没想到,这边的电源插头样式不一致,导致笔记本电源耗尽,只好关机数日作毕。

直到昨天,三浦小姐从中国回来,向她借了个转接器,算是终于又恢复了电力。看来,出国一趟还真是不一样。去年去印度也是一样,到了发现插头没法用。没想到,这次来日本又是好了伤疤忘了疼。不过去年印度这次,同事帮我迅速在楼下买到了转接器。这次在日本,我跑了两个比较大的超市竟然没找到,真是奇怪?

这几天的日子过得倒还算不差。第一次来这个与中国渊源不断的国家,带着无数复杂的观点。不过现在的感觉是,日本这个国家受中国古代影响实在太厉害。到处可见中国的影子。

不过有一点日本没有继承中国的优良传统,那就是吃。这边能吃的东西花样是比较少的。据待的时间久的中国同事说,她已经实在找不到特别想吃的东西了,在这边。

不过没有高楼,环境安静,整洁,这一点,还是需要国内的很多城市学习。要单纯从生活的角度上看的话,这样的城市,倒算是很惬意的。

周四了,明天可以穿随便点了。还有,可能会和这边的中国同事们一起出去吃顿肉,喝顿酒。

名古屋纪行 2

名古屋纪行 1

带着失落的空空的心情,从浦东国际机场登上了飞名古屋的班机。情绪不太好。但是,生活还是要继续。即便有再多困难与酸楚,也只好一个人承担。

名古屋,也许,可以是出现转机的一站吧。

才两个多小时,飞机着陆,时间如此短,让我感觉恍若是趟简单的国内旅行。机场内到处可见中文解释,到处听得见中文语音提示,根本不觉得是到了另外一个国家。

安静,即便是机场,人来人往的地方,感觉也比上海安静了许多。也许是天有点晚了吧,晚上九点多点。

乘快速铁路到市中心,金山站,人多起来了,不过还是安静。

转地下铁再一站到东别院。安静和干净是两大主题了。没有光怪陆离,高楼大厦,但是有星星的落叶,错落有致的屋舍。感觉,第一印象,对这个城市,很不错。假若,在国内也能找到这样一个感觉类似的城市,我想,我会很干脆地舍弃了那么多烦扰,而立即投奔它。

步行一会就到了住处。干净的一室户小租室。常用物品倒是很齐全。很整齐。唯一的问题,没有网络。对于,生活工作离不开网络,再加上身处异地,没有其它生活消遣去处的我,似乎有点不爽了。明天,去公司和行政事务人员问问看能不能加。不过,转念一想,难得有机会真正远离那些纷纷扰扰一段时间,也是好事。干嘛习惯性的又把自己投到那张网中去呢。

很多事物,越想抓得牢,就越容易失去,人也感觉越累,情绪也会越差,何必呢?还是等待顺其自然的好吧。

准备洗洗睡了。名古屋,晚安。

名古屋纪行 1

ReSharper Horizons: ReSharper and Visual Studio 2008

Following is just for your reference, if you are a ReSharper fan.

Since there is a lot of buzz about Visual Studio 2008 release, I thought I would stand and say about ReSharper in relation to this fact.
Released version
ReSharper 3 can be installed with Visual Studio 2008 and works fine, unless you are using C# 3.0 new features, like lambdas, LINQ, extension methods and such. This constructs are not parsed by ReSharper 3, which was developed to support C# 2.0 only. It is not only highlighting which doesn’t support C# 3.0, it is all the core and code intelligence. For example, rename refactoring will not find usages of extension methods and will not update them.
There also could be some glitches, even if you don’t use new C# 3.0 constructs. This is due to the fact that C# 3.0 compiler is always used in Visual Studio 2008 C# projects, regardless of target framework. It it is not widely discussed, but changes in language are wider than just several new features. There are differences in type inference in generics and candidates lookup for binding, to name few. If you happen to hit this special cases, ReSharper could behave incorrectly.
If you are really-really going to immediately jump C# 3.0 wagon, you can disable highlighting (Options / Code Inspection / Settings) and switch to Visual Studio native intellisense (Options / Environment / IntelliSense / General). This will help a bit, but still you cannot trust find usages results, refactorings and many other features.
There was also reported weird problem with Visual Studio 2008 and ReSharper installed on x64 computers – opening Visual Studio’s Find dialog crashes. We are currently trying to reproduce this problem. If you experience this problem, please tell us!
Some people tend to ask for quick-and-dirty hack for ReSharper 3 so that it just parses the code and don’t do anything intelligent with C# 3.0 code. It is not possible. Details are not important here and are pure technical.
Next version
ReSharper 4 is in very active development. Its main purpose is to support C# 3.0 in all of its beauty. This means not only parsing and code intelligence, but also new analysis, refactorings, context actions and quick fixes. We are concentrated on making your development experience with C# 3.0 as smooth and pleasant as possible.
Currently, we have support for implicity typed variables and arrays, extension methods, object and collection initializers and automatic properties. As soon as we complete support for lambdas, queries and anonymous types, we will open Early Access Program. We plan to achieve this goal in January, 2008.
From this point you will be able to download EAP or even nightly builds and try full power of ReSharper 4 with your new C# 3.0 code.
In regards of upgrade policy, we are currently in the process of deciding upgrade cost, who qualifies for free upgrade, or if we want to do something special about this release. I will post about it as soon as I can.
As for release plans, we are aiming at 2008’Q1, hopefully sometime soon after Visual Studio 2008 launch event in February. ReSharper 4 will be available to general public via
Early Access Program at least for 2 months before release.
If you have any questions, do not hesitate to ask in comments.

ReSharper Horizons: ReSharper and Visual Studio 2008

ReSharper Horizons: ReSharper and Visual Studio 2008

.NET Web Product Roadmap (ASP.NET, Silverlight, IIS7) – ScottGu’s Blog

The release of VS 2008 and .NET 3.5 is just a begin of the a series of exiting stuff for MS-based developers. Lets’ take a look at the roadmap what Scott just mentioned.

Releasing the Source Code for the .NET Framework Libraries

ASP.NET 3.5 Extensions Release

  • ASP.NET MVC
  • ASP.NET AJAX Improvements
  • ASP.NET Dynamic Data Support
  • ASP.NET Silverlight Support
  • ADO.NET Data Services (good news is MS will release ADO.NET Entity Framework too)

Silverlight 2.0 Release

  • WPF UI Framework
  • Rich Controls
  • Rich Networking Support
  • Rich Base Class Library Support

IIS 7.0

.NET Web Product Roadmap (ASP.NET, Silverlight, IIS7) – ScottGu’s Blog

.NET Web Product Roadmap (ASP.NET, Silverlight, IIS7) – ScottGu’s Blog

Think about it

To be honest, I am a good man to have a talk, discussion, and/or communication; and most time I am very happy to help anyone who has a good attitude. However, I do need a favor for people who wants get something from me, RESPECT. I am not a FOOL and you are likely not a genius. Think about it.

Think about it