Dot-Net, or Not Yet?

原创 2000年12月31日 12:37:00
Dot-Net, or Not Yet?

Yesterday, I was talking with one of VCDJ's frequent contributors, brainstorming about the next article he ought to write. "How about something on C#?" I asked.

"Uhh," he replied, "the fact is I haven't written a single line of C# code yet."

"OK, no sweat," I said. "Want to do a piece on Managed Code?"

"Haven't gotten to that yet."

"Fine. Interested in writing about using C++ within the .NET framework?"

"Look," he finally blurted. "I'm not even thinking about .NET yet. I've got to concern myself with writing code for products that have got to ship now. Alpha and betaware are just going to have to wait."

You've probably got a lot in common with this author. That is, like him, you've got a lot of demands on your time, and almost all of them have to do with getting your product out the door. And while your employer (whether that employer is a company or yourself) realizes you've got to stay on top of new developments, that gets ?shall we say, deprioritized in the face of looming code-complete dates.

This learn-what's-coming-up-but-use-what-you've-got dilemma is hardly new to developers. It's pretty well accepted, however, that VS.NET will cause the biggest waves in the development community since ?since ?sheesh, since ever. You can't wait 'til it ships to learn about it—there's too much there. So whatcha gonna do? Here's my advice:

Talk to your boss. Grab the last few issues of this magazine and march into your boss's office. Spread the covers on the desk, point out that they all have something to do with .NET, and explain that .NET isn't just about the way you write code, it's about fundamental changes in the way applications work, as well as how they work together. Now—before it's time to start writing code to this new paradigm—is the time to think about how your applications fit into this framework.

Make it clear that both your job satisfaction and the company's relevance are on the line. Get a budget for books. Get time allocated for studying. Get the company to send you to conferences (check out Essentially, do whatever it takes to get some time and money set aside for learning about .NET. You and the company are going to have to climb the .NET curve. Start now, or you won't have momentum when it matters.

Get the preview. The technology preview (available now) is a free download at Get comfortable with it.

Read this magazine. I've already mentioned that the last few covers of VCDJ have emphasized .NET. That's not going to stop any time soon. And while VCDJ shouldn't be your only source of .NET knowledge, it's a mighty fine place to start. Our .NET coverage is comprehensive, without being overwhelming. Don't worry, though, we are not—repeat, not—abandoning VS6. We'll continue covering VC++ 6 as long as you keep using it.

Experiment. True to VCDJ heritage, our .NET articles focus on how-to. Starting in this issue—and continuing through January—we're walking you through creating an e-commerce site using C# and other .NET technologies. Follow the steps, then play around with the project, adding features of your own. Let me know what you come up with: e-mail

Decide what matters to you. You know your business best. There may well be parts of VS.NET or Microsoft's .NET strategy you can safely ignore. Consider how—and whether—these new technologies might affect you and your company, then focus on learning what you need to. You'll get to the other stuff when you have time. One additional thought along this line, though: Just because you don't need to know C# in your current job doesn't mean you won't need to know it in your next. Stay up-to-date; you'll be glad you did.

Don't freak out. It'll be months before VS.NET ships; you've still got time to get your arms around it. Learn a little at a time. Before long, as you're writing your VC++ code for today's projects, you'll see how you'd do the same thing—but better—in VS.NET. And once again, you're ahead of the curve. Nice going.

Dot-Net, or Not Yet?

  • zgqtxwd
  • zgqtxwd
  • 2008年04月24日 13:49
  • 97

Android Studio升级到0.5.2后,打开非常慢,报错”Project is not yet initialized.”

Android Studio升级到0.5.2后,重开工程项目,报错”Project is not yet initialized.” Posted on 2014 年 3 月 28 日 ...
  • u012910985
  • u012910985
  • 2014年04月04日 09:08
  • 3564

ceph部署monitor时出现"monitor is not yet in quorum..."问题解决方法

问题描述如下: 解决方法: 是因为在部署之前的步骤中,需要关闭防火墙,在每个节点上都需要执行:                        systemctl  stop firewalld  ...
  • 2017年07月28日 17:32
  • 1479

Mac 运行dubbo demo报 WARN support.AbstractZookeeperClient: [DUBBO] Zookeeper is not connected yet!

运行duubbo-demo的provider时 [DUBBO] Timeout! zookeeper server can not be connected in : 30000ms!, dub...
  • yunyoulei1
  • yunyoulei1
  • 2018年01月14日 00:59
  • 379

YARN(YetAnother Resource Negotiator)

YARN(YetAnother Resource Negotiator) YARN:针对MapReduce在扩展性和多框架支持方面的不足(扩展性受限、单点故障、难以支持MR之外的计算),提出了全新的...
  • suixinsuoyuwjm
  • suixinsuoyuwjm
  • 2014年04月05日 13:58
  • 1960

currval of sequence "follow_id_seq" is not yet defined in this session

postgresql上使用select currval('follow_id_seq'); 报错: currval of sequence "follow_id_seq" is not yet d...
  • dipolar
  • dipolar
  • 2016年04月01日 11:17
  • 800


学习使用Junit4,既然使用最新版本了,就不要再考虑之前是如何使用的了,之前有听过junit但一直没有使用,现在开始学习使用junit4! 介绍就不说了,就是一个方便大家测试的插件! 现在使用Mye...
  • qqHJQS
  • qqHJQS
  • 2014年12月28日 21:42
  • 3541


今天工作时,遇到了ServerNotRunningYetException错误。其症状是进入hbase shell是正常,但是执行任何指令时会抛出这个错误。 查看log时并没有报错信息。开始我以为是...
  • zw0283
  • zw0283
  • 2016年10月19日 18:17
  • 1723

Oracle/PLSQL ORA-08002: sequence NAME.CURRVAL is not yet defined in this session

錯誤原文 - sequence NAME.CURRVAL is not yet defined in this session錯誤原因 - 要執行CURRVAL 指令前未執行NEXTVAL 的最後一個...
  • hb308102796
  • hb308102796
  • 2010年07月21日 10:41
  • 4015

Android Studio 启动速度很慢的问题[android studio Project is not yet initialized]

Android Sudtio在开发效率方面,就我自己的使用感觉而言,的确比eclipse高了不少,再加上Mac上面的...
  • lihei12345
  • lihei12345
  • 2014年04月16日 16:21
  • 7081
您举报文章:Dot-Net, or Not Yet?