dotNET Tools Weblog

Microsoft .NET Tools
www.dotneTTools.org


This page is powered by Blogger. Isn't yours?
Thursday, February 27, 2003
 
C#->VB.NET
This one does c# to vb.net
http://aspalliance.com/aldotnet/examples/translate.aspx
http://www.xmlforasp.net/codeSection.aspx?csID=44

 
征集.NET WebLog
我想网络上应该有许多针对.NET的WebLog吧,中国呢?
所以先去CSDN发了一帖,看是否有志同道合者。
另外似乎还需要一些ASP.NET的空间,不知那里有Free的。
无论是.NET的WebLog还是ASP.NET的免费空间,只要你能帮忙那么告诉我:)

http://expert.csdn.net/Expert/topic/1470/1470839.xml?temp=.9055292
http://expert.csdn.net/Expert/topic/1470/1470838.xml?temp=.8429682
http://expert.csdn.net/Expert/topic/1470/1470841.xml?temp=.9639704
http://expert.csdn.net/Expert/topic/1470/1470844.xml?temp=.5738184


 
你的邻居也许是你最远的朋友
很喜欢这样的一个感觉:和你的用户或者你就是用户通过Internet的方式进行交流,也许是你帮他解决一个问题,也许是他帮你解决一个问题,也许是因为工作的原因大家共同磋商一件事情,也许因为知道永远不会见到对方,反而会更加真正的对待事情本身,会尽心尽力的把事情做得更好。如果刚好对方是一家著名的公司或是一个名人那么你的自豪感油然倍增,其实我们这一代接触EMail或Internet也就是5年多一些8年的时间,但是比起我们的父辈,似乎Internet就像我们从小而生的一样,一种特质一种感觉深深的印在头脑里感觉里,有时感觉离开Internet我们可能无法正常的生活,同时有时也深信Internet一定会改变未来或是创造未来。

看看今天有什么:)
The Future of Java
http://www.newsfactor.com/perl/story/20816.html
Jason Hunter, formerly a member of the Java Community Process executive committee, credits some of Java's advances to a perhaps unlikely source: ".NET has been beneficial to the evolution."

Since Java is no longer the "next big thing," and hype-heavy headlines about it have largely disappeared from tech and mainstream publications, one might harbor the impression that the language and platform are falling by the wayside. In fact, Java has finally achieved one of the highest honors the tech industry can bestow: It is taken for granted as part of the infrastructure on which many companies depend.

Hunter agreed there is no danger that .NET will displace Java. "Basically, I think .NET is Pepsi and Java is Coke," he said. "They're very similar, but they each have some of their own quirks and differences. Some people like one more than the other."

Is .NET's 'C' Sharper Than C++ or Java?
http://www.newsfactor.com/perl/story/20584.html
Learn everything you can; be as eclectic as you can,

Will Microsoft Be the Web-Services Winner?
http://www.newsfactor.com/perl/story/20821.html
The Ghost of Success

In its Web services bid, Microsoft may be haunted by its own success. Or rather, its path to the success.

Its Office suite and other key business applications were an easy sale to those using its Window operating system. As we entered the Internet age, Microsoft added a browser to the equation. Sure, said the computing public, we're on board.

So the company has a long term pattern: Build on past success, leveraging a user base tied to its proprietary system. With each new era, it encountered little resistance as it walked consumers down the Microsoft path.

A New World

But to succeed in Web services, the software giant has to look itself in the mirror and say, firmly, "I need a new attitude." Web services is all about interoperability, and embracing industry-wide standards. If my machine is going to speak to your machine, we need a common language.

A successful strategy for Web services is founded on putting aside the proprietary in favor of the universal. No vendor does this naturally, and based on history, it's a particularly unnatural act for Microsoft.

Clearly, there's some churning within Microsoft about its Web services strategy -- some kind of internal struggle, as we saw last month when Redmond decided to drop the .NET moniker from its Web services offering. Microsoft head Bill Gates had often promoted .NET as the centerpiece of the company's new effort. And now the term won't exist. Hmmm, all is not well in world of Microsoft Web services.

The MIDI Model --我喜欢这段历史
The music hardware industry confronted an identical problem in the early '80s and resolved it to the betterment of all vendors. Synthesizer makers like Roland and Korg had so-so sales of stand-alone machines, but understood that massive sales would result if their synthesizers could talk to each other.

So they all got together and created an industry-wide standard, Music Instrument Digital Interface (MIDI). The resulting interoperability was a gold mine for vendors as consumers were able to mix and match vendors' products.

The twist on this -- and here's where Microsoft's long history of software development gives it an advantage -- is that some vendors added their own touches. One, for example, added extensions to the standard that allowed its products to shine.

The bottom line: Microsoft, for all its historic insistence on the proprietary, could still be the dominant player in a world based on interoperability.


Tuesday, February 25, 2003
 
What is new in Visual Studio.NET 2003 中文版
Visual Studio.NET 2003中Visual C++.NET有多么强大的功能?关注它吧

Visual Studio.NET 2003 新特性(最快最新中文版本介绍)
http://www.dotnettools.org/article/VSNET2003.htm

Loki,Visual Studio.NET中专门提到了它,现在它也有For VC++ 7.1的版本了。
http://www.geocities.com/rani_sharoni/LokiPort.html

这个世界上有三个比较奇怪的模板类库,如果以前你不知从现在开始注意它们:
boost http://www.boost.org/
STLPort http://www.stlport.org/
Loki http://freshmeat.net/projects/lokilibrary/

目前只有STLPort我试过,但没有在Visual Studio.NET 2003中编译通过,当然只是今天,2003年2月25日为止,我想不久也会编译通:)

我专门保留了一个Loki for VC++ 7.1的版本在我的网站,你可以Download它。
www.dotNETTools.org/download/loki/LokiPort_VC7.zip
原始网站:http://www.geocities.com/rani_sharoni/LokiPort.html

Last update: May 19, 2002
Directions:
To use Loki, simply extract the files from the archive, give your compiler access to their path, and include them appropriately in your code via #include.

If you use the small object allocator directly or indirectly (through the Functor class) you must add SmallObj.cpp to your project/makefile.
If you use Singletons with longevity you must add Singleton.cpp to your project/makefile.

Compatibility:
This is ported version of Loki to VC.NET (VC7 - 9466) it is only targeted for this compiler.
To compile your sources with the original Loki you'll have to place it in a separate directory.

More info:
http://moderncppdesign.com
http://www.geocities.com/rani_sharoni/LokiPort.html

还有一个For VS 6.0的版本:
www.dotNETTools.org/download/loki/lokiVC6port.zip
原始网站:
http://fara.cs.uni-potsdam.de/~kaufmann/?page=lokiport

Loki VC 6.0 Port or how to produce C1001 - Internal Compiler Errors
-------------------------------------------------------------------
Version: 0.3b

Introduction/Compatibility:
---------------------------
This is a partial MSVC 6.0 Sp5 compatible port of Andrei Alexandrescu's excellent Loki Library.
Because I could not retain the originial interface in all places, this port is not
compatible to the original library and therefore code using this port *cannot* generally be
used together with the original lib.
This is, of course, a great pity.
So if you know of a complete and full interface-compatible VC 6.0
port or if you know how to improve this port, please let me know.

Contact:
--------
For any suggestions, bug reports, comments and questions please email me to
Hume@c-plusplus.de

Using this port:
----------------
To use this port, simply extract the files from the archive, give your compiler access to
their path, and include them appropriately in your code via #include.

If you use the small object allocator directly or indirectly (through the Functor class)
you must add SmallObj.cpp to your project/makefile.

If you use Singletons with longevity you must add Singleton.cpp to your project/makefile.

Fixes:
------

Jan 30, 2003:
-------------
* In TypeTraits.h: Fixed bugs in TypeTraits' scalar and array detection.
const and volatile detection is now based on techniques from boost's type traits
(see http://www.boost.org/libs/type_traits/)
Added Enum- and pointer-to-member-function-detection code.
Thanks to M. Yamada.

More info:
----------
The original Loki library can be found here: http://moderncppdesign.com
For Rani Sharoni's VC 7.0 port see: http://www.geocities.com/rani_sharoni/LokiPort.html


Saturday, February 22, 2003
 
微软准备向测试用户寄送 Office Beta 2 Kit
见下面的EMail:
**Action required to receive Office Beta 2 kit**

**Do not reply as this email is being sent to you from an un-monitored account. Due to Microsoft's security requirements, the hyperlink(s) contained in this email may not automatically open your browser. If you experience any difficulty, please copy the link and paste into your browser. **

Dear XXXXX ,

This message is in regards to your address information. In the coming weeks, we will be shipping your Beta 2 kit for the Office 11 and Office Family applications.

Please review the address information above. This is the mailing address where your Office Beta 2 kit will be delivered.

If the mailing address above is CORRECT, no action or confirmation email is required.
If the mailing address above is INCORRECT, you will need to update your contact information by doing the following:

Visit www.betaplace.com
Enter your BetaID & Password: XXXXX/XXXXXXXXXX

Select Modify Contact Information.

Once you log in, you will be taken to the general BetaPlace homepage to update your personal data. At this time, you may or may not have access to further information about the Office 11 Beta 2 release.

A definitive delivery date is not available at this time. We’re sorry, but inquiries regarding a ship date will not receive a response.

Thank you,
The Microsoft Office Team


Thursday, February 20, 2003
 
.NET 2003

今天有些空闲的时间,说说昨天,去三亚参加了金蝶2003年经销商大会(当然我不是经销商:)),有些感悟,算是总结上一年自己对.NET的看法。

说起.NET,我们必须针对不同的人来讲(微软语):
对开发人员
贯穿微软整个产品线的 Web Services 的实施方式
与.NET相关的微软产品以及合作伙伴的产品可以通过Web Services实现跨平台的互用,并且为寻求将现有投资和未来投资连接起来的客户提供价值

IT用户
.NET定位于攻克三种最棘手的信息技术难点:连接公司内部和商业伙伴之间全然不同的系统;通过提高开发者生产力来解决冗积的应用障碍;以及帮助IT公司在目前的经济状况中实现事半功倍。

商务类型的用户
NET是贯穿整个产品线的软件技术。这些产品与标准使得客户能够将不同的信息、系统和装置进行连接以满足他们自身和商务的需要,能和他的用户、Partner、客户更紧密、经济和敏捷的联系起来

消费用户
It’s the ability to access and act upon information anytime, anywhere and on any device
.NET使客户能够轻松的体验.NET世界,实现大量丰富和激动人心的下一代用户体验,通过多媒体的手段实现新的视觉呈现和显示

对于.NET不同的人应该有不同的定义,不如你对一个普通消费者讲.NET Framework ?????,那什么是.NET?
我总结的.NET :)
.NET
对开发人员是指 .NET Framework
对技术人员是指 Microsfot.NET 平台*
对消费者是指 .NET 体验
对商业来说是指互连—”.NET Connected”
对Internet来说是指基于Internet的XML Web Services的平台
对微软来说是实现自己目标的一种软件、Microsoft.NET是开创性的行动本身,是产品广泛的大家族,是微软的又一个品牌

(*.NET 平台包括.NET智能客户和.NET智能客户端软件、.NET Enterprise Server , Web Services, .NET Framework & Tools, .NET体验)

会上徐少春将 Kingdee EAS比作是一套组合家具形象的讲给下面的经销商听,我想微软就是生产这些家具的木材、铝合金、胶水、玻璃和各种家具工具的公司;而.NET应该是一种方法论,有它,人们可以有一套方法、一个平台和一套工具很快的将家具生产出来,而这些家具都带有一个明显的特性-“Connected”,也就是说.NET不是软件开发或架构放之四海的方法论,但它对于解决有关面向Connected和Internet应用最好最经济的一种方法。


 
J2EE 1.4 delayed until Summer

"Right now, most organizations are not even using the [J2EE] features that exist already. Most of them are using Java Server Pages, but there's not a lot of Enterprise JavaBeans use going on," said Daryl Plummer, an analyst at Stamford, Conn.-based Gartner Inc. "I'm hard-pressed to believe that anybody but the most leading-edge Java users are going to be generally impacted by a significant delay."

weblog: This is what I see in the field as well: Servlets and JSP’s (maybe Struts or something like it) and POJO’s (plain old java objects). The J2EE vision of component-based reuse (EJB) and being able to compose new apps from existing components has never come about. The best candidates for .NET are those who are looking at their investments in J2EE (over years) and wondering what it bought them…
http://www.computerworld.com/developmenttopics/development/java/story/0,10801,78204,00.html

老新闻,前天无法上网,现在补上。


Sunday, February 16, 2003
 
SQL SLAMMER BETA Version 3 TOOLS Testing
*DO NOT REPLY, AS THIS IS BEING SENT FROM AN UNMONITORED ACCOUNT*
Internet ID: new2001@msn.com
BetaID: 469XXX

Hello all,

We greatly appreciate the efforts you’ve made so far to help us test these tools. There is still time to continue testing. So, if at all possible, please download tools or continue testing and provide us with your feedback! There are newsgroups set up, so please feel free to post your comments, concerns… When you’re finished testing, be sure to complete the survey on www.betaplace.com.

Thank you!!

Maria "Daisy" Adalbert
Program Manager
Microsoft SQL Server Development Team
Bld.35/3845

这个测试工具包包括:
sql-msde-criticalupdate_enu.msi (11.11 MB)
SQLCritUpdPkg_ENU_PWD.exe (21.71 MB)
应该有下面的一些工具:
SQL Critical Update Wizard
SQL Scan Tool
SQL Check
SQL Critical Update
SMS Deployment Tool

安装和运行Eclipse 2.1 M5
Asked for specific instructions to get Eclipse running.

1.Download the most recent IKVM binaries (I just updated them).
2.Download Eclipse. I use build M5.
3.Unzip both zip files. Here I will assume that both are unzipped in the root of C: (the ikvm zip creates an ikvm directory and all the Eclipse files end up in an eclipse directory)
4.Download eclipse.bat, save it in the eclipse directory.
5.Open a Command Prompt window and cd into the eclipse directory and run eclipse.bat
M5具体的新特性有哪些?见这里

Inside info on Windows 2003 --Straight from Bink Windows XP

I have some exclusive info on the last stages of Windows 2003.

ESCROW is final stage where Microsoft deploys the build on their own production servers

Windows Server 2003 Build 3757
This build was NOT meant to be published, but Microsoft Dev Team badly wanted to release a new feature for public testing - ”IE Hardening”
Basically, it’s a policy that you set for the server, and it makes Internet Explorer only reach sites listed in ”Trusted Sites”.

Windows Server 2003 Build 3760
Targeted for ESCROW, this was first targeted as ”the final RC build”. A few problems surfaced and id did not make it.

Windows Server 2003 Build 3763
New build targeted for ESCROW, to be ”final RC build” to go public. Build 3763 is the last one to have public BETA RC PID.
Starting with Build 3764 real PID’s apply. Old BETA-keys do not apply.

Windows Server 2003 Build 3764
Finalized Thursday and publish Friday morning, this is the same as build 3763 but has the new “full” shipping PID’s. Otherwise it’s identical to 3763.

Windows Server 2003 Build 3765
Targeted for 2003-02-07, published 2003-02-08 and ESCROW, intended as RTM/GOLDEN. Minor changes compared to 3764.
The final build number will differ from 3765, but if build 3765 is stable – survives testing without showstoppers – it’s the code in this build that will be “golden”.
No new code will be checked in after this date, if not a “showstopper”.

RTM
Time is critical. With the commitment of launch the 24th of April (boxes in stores), Microsoft has to RTM the code March 12, 2003.
The code that is RTM has to survive about 15 days of ESCROW before RTM.

有关这个非凡的Server的信息:http://www.microsoft.com/windowsserver2003/default.mspx

VS .NET 2003 is comin out very soon,
17th Feb 2003. (doubt)
24th Apri 2003. (mostly)
非微软官方的证实发布时间:)


Saturday, February 15, 2003
 
Valentine's Day

情人节是非常美妙的节日,如何是有情人的还是没有情人的:)
有些有趣的东西送给你的网络情人吧,当然如果你使用MSN Messenger

(l)({)({)({)({)(l)(l)(l)({)(l)(})(})(})(l)(l)(l)(l)(l)
(l)({)({)({)(l)({)({)({)(l)(l)(})(})(})(l)(l)(})(})(})
(l)({)({)({)(l)({)({)({)(l)(l)(})(})(})(l)(l)(l)(l)(l)
(l)({)({)({)(l)({)({)({)(l)(})(l)(})(l)(})(l)(})(})(})
(l)(l)(l)(l)({)(l)(l)(l)({)(})(})(l)(})(})(l)(l)(l)(l)

({)({)({)(f)(f)(f)(L)(L)(f)(L)(L)(f)(f)(f)(})(f)(f)(})(f)
(f)({)(f)(f)(f)(L)(L)(L)(L)(L)(L)(L)(f)(f)(})(f)(f)(})(f)
(f)({)(f)(f)(f)(f)(L)(L)(L)(L)(L)(f)(f)(f)(})(f)(f)(})(f)
(f)({)(f)(f)(f)(f)(f)(L)(L)(L)(f)(f)(f)(f)(})(f)(f)(})(f)
({)({)({)(f)(f)(f)(f)(f)(L)(f)(f)(f)(f)(f)(f)(})(})(f)(f)

(F)(F)(F)(F)(F)(F)(F)(F)(F)(F)(F)(F)(F)
(F)(F)(F)(L)(L)(F)(F)(F)(L)(L)(F)(F)(F)
(F)(F)(L)(L)(L)(L)(F)(L)(L)(L)(L)(F)(F)
(F)(L)(L)(L)(L)(L)(L)(L)(L)(L)(L)(L)(F)
(F)(L)(L)(L)(L)(L)(L)(L)(L)(L)(L)(L)(F)
(F)(F)(L)(L)(L)(L)(L)(L)(L)(L)(L)(F)(F)
(F)(F)(F)(L)(L)(L)(L)(L)(L)(L)(F)(F)(F)
(F)(F)(F)(F)(L)(L)(L)(L)(L)(F)(F)(F)(F)
(F)(F)(F)(F)(F)(L)(L)(L)(F)(F)(F)(F)(F)
(F)(F)(F)(F)(F)(F)(L)(F)(F)(F)(F)(F)(F)
(F)(F)(F)(F)(F)(F)(F)(F)(F)(F)(F)(F)(F)

不要骗MM哦!

MSDN有一篇不错的文章:
How to Share Session State Between Classic ASP and ASP.NET. download code


Monday, February 10, 2003
 
The Five Phases

这才刚刚调试好我的weblog,模样马马虎虎、网络状态也总是不好,不知不觉中已经是一个"weblog"了:),我不知道,不过可以用它来记录我的生活的故事和感受了。这种形式更有趣。调试成功总共花了2小时,说起来挺困难的:) 讲起来人生的许多事情都挺象《The Five Phases》中的场景。
多少也会有些喜悦。

The Five Phases
Don Box
Originally appeared in the July 1995 issue of C++ Report

Starting with this issue of the Report, I will be acting as Associate Editor, lending a hand as we introduce new columns and features that relate to the particular challenges that face C++ developers that use PCs in general and Microsoft Windows in particular. Our goal is to augment, not replace, the current lineup with additional columnists that are focused on core issues related to using C++ in the personal computing arena.

I accepted the job of Associate Editor with trepidation. Knowing that many of the pieces I would be responsible for would be related to Microsoft Windows, I feared that I would be perceived as a Microsoft sympathizer, which, in these current McCarthy-esque times, might be hazardous to my career. One only needs to read a handful of postings on USENET or pick up a copy of Business Week to see that there is a growing faction in our society that sees the Redmond Menace as the next evil empire. While I doubt that Microsoft poses a real nuclear threat, the idea of long protracted senate hearings is not that far fetched.

It is possible that people feel especially passionate about Microsoft because they produce an operating system. To many, an operating system is like a religion or political party: an affiliation based on extremely personal choices and beliefs. I was once guilty of this attitude. Because, to many, operating systems are such a personal issue, I feel compelled to relate my own experiences of coping with life under Windows, to help others who are going through the transition now or may begin the transition in the near future.

My name is Don. I write programs that run under Microsoft Windows.

My story is rather simple. I didn’t always work under Windows. For many years, I was quite happy writing software for the Macintosh for personal recreation and later to feed my family. In parallel, I wound up writing UNIX code while serving a 4-8 year sentence at the University of California. I was blissfully oblivious to the world of Intel-based PCs until 1993, when, armed with the Microsoft C7 compiler and a no-name 486 box, I inadvertently started my descent into the valley of colliding IRQs and arbitrary filename limitations.

My motivation for buying a PC was innocent enough: I had grown tired of the slow compile-link-debug cycles I was experiencing under Macintosh Programmer’s Workshop using Apple’s CFRONT-based compiler, and knew that any compiler that ran on a PC would have to be faster than the then-current generation of Mac compilers. My assumptions about raw compilation speed were correct, however, I did not take into account the massive time investment required to get a circa-1993 Windows box to actually work.

I had no intention of writing Windows programs per se, and I had certainly never planned on understanding the four classes of pointers commonly used in Windows 93 and MS-DOS. It just happened.

While discussing my story with a friend that had followed a similar path, I discovered that many had traveled this road before me, and that the route often follows the following five phases.

Phase 1: Ignorance
People in the ignorance phase are often heard saying "FooOS is the last operating system I’ll need to know." This mindset is often encouraged by overly romanticized stories of an operating system’s origins, usually involving a band of bright renegade engineers that independently create the one true operating system without the support of their monolithic corporate employer. Many modern operating systems have very rich cultures to propagate such stories. Steven Levy’s Insanely Great and Peter Salus’s A Quarter Century of UNIX do a reasonable job of documenting the mythology, dialects, and artwork of two such cultures.

Phase 2: Denial
The denial phase usually begins when a respected colleague or a complete department in an organization goes over to "the dark side." P2’s see the adoption of Windows as a lack of confidence in the one true operating system, and often launch into a long, yet eloquent, defense at the mere mention of the Northwest region of the United States. It is not uncommon for programmers in the denial phase to secretly purchase a copy of Charles Petzold’s Programming Windows 3.1.

Phase 3: Anger
The anger phase usually begins within the first two weeks of running Windows, or within the first two hours of programming Windows, whichever comes first. At first, P3’s attempt to recreate as much of their former environment under Windows as possible, searching for ported versions of their favorite editor, shell, etc. This only fuels their anger, as invariably, they are unable to debug programs interactively from within their editor, or the mouse has the incorrect number of buttons. As P3’s transition to mainstream Windows applications and development environments. they often find that their productivity increases, and their anger subsides.

Phase 4: Remorse
This phase officially begins when a P3 sits down at their former OS and no longer instinctively remembers the key-binding for closing a window or copying text. P4’s have usually abandoned the one true operating system for dead, and no longer use it, even at home. P4’s can often be heard beginning sentences with "FooOS was a great OS..."

Phase 5: Acceptance
Rather than pick up a torch and join the angry mob of P3’s as they storm Castle Bill, P5’s have a somewhat different attitude towards Microsoft. To a P5, Microsoft is remarkably similar to the federal income tax. Both are unlikely to go away in the near future. Both provide an infrastructure that, while imperfect, allows one to live a prosperous life. Both require non-trivial attention to avoid disastrous consequences. P5’s are seen as turncoats by P2’s and P3’s, while P4’s look to P5’s as role models. P1’s remain blissfully ignorant of the entire experience and lead happy, productive lives.

Thanks to Dan W. (an amazingly well adjusted P5) for showing me the way.


 
I'm not saying .NET is better but...
无论如何争论.NET 和Java,我始终感到这是非常有趣的一件事。
以前和Java的语言一直限于语言的争论,再高级一点开始着重架构方面的争论。
但当我看到下面的文章有些感到快乐,这是Java? ――Julian S. Taylor 写的The Java Problem
有感-101个Java比.NET好的理由

.NET Tools HOME
Copyright 2003 ccBoy EMail:new2001@msn.com