查岗

[nalnait]

.......

[王向飞]

没看懂楼上发的东西

[csuxp2008]

水帖？

[nalnait]

................

[namhyuk]

Silverlight Screencasts and Training VideosTwitter Search MonitorImprove graphics performance using CacheMode

...

...

[xhtmldivcss]

这是有关异步方法调用的小儿科例子Asynchronous Method Invocation（异步方法调用）Introduction

In our daily life, we often come across a situation where we need to invoke a method in a new thread. We generally create a new thread directly and use it. Well, it is not actually recommended to create a Thread as and when required. So we use ThreadPool to have a better use of available threads and also configure it our self.

Thus we require a considerable amount of code to just call a method in another thread. Delegates comes with methods like BeginInvoke which is used to call a method Asynchronously and with proper usage of ThreadPool. We will be discussing that to you with the most simple example.

Synchronous Call

Delegates are generally used to hold method definition and to call it whenever it is required. We can use delobj.Invoke(params) or delobj(params) to invoke a delegate. In the sample application we create a method which simply adds up two numbers. To do this we have created :

private delegate int AddOperationDelegate(int x, int y);

private void button3_Click(object sender, EventArgs e)
{
    AddOperationDelegate del = new AddOperationDelegate(add);

    lblResult.Text = "Synchronous work Started !";

    lblResult.Update(); //This is necessary to repaint the window before calling Thread.Sleep

    int res = del.Invoke(10, 20); // or del(10, 20);

    MessageBox.Show(string.Format("Result generated : {0}", res));
}

In the method Add we just wrote :

private int add(int x, int y)
{
    Thread.Sleep(4000); //Makes the thread to sleep, to make you understand it creates a new thread.
    return x + y;
}

Thus you can see the delegate AddOperationDelegate(int x, int y) is called synchronously using del.Invoke(). The method add is called during this operation and the output will be shown using the message box. If you try the sample application you should notice, that after you click on the Synchronous button, the window gets hanged and you cannot do any operation.
This is actually happening because the current thread is blocked using Thread.Sleep which is invoked inside the add method to halt the application for 4 seconds. This might be a long running process.

Asynchronous Call

To eliminate this issue we might take the help of BeginInvoke and EndInvoke, which actually creates a new thread and invoke the method from there. To do this let us look how the Asynchronous button looks like :

private void btnAsynchronous_Click(object sender, EventArgs e)
{
    AddOperationDelegate del = new AddOperationDelegate(add);

    IAsyncResult res = del.BeginInvoke(10, 20, new AsyncCallback(InvokeMessage), null);

    lblResult.Text = "Asynchronous work Started !";
}
private void InvokeMessage(IAsyncResult ar)
{
    AddOperationDelegate aod = (ar as AsyncResult).AsyncDelegate as AddOperationDelegate;
    int result = aod.EndInvoke(ar);
    MessageBox.Show(string.Format("Result generated : {0}", result));
}

In the above code you can see I have called BeginInvoke instead of normal Invoke. BeginInvoke actually creates a new thread from the ThreadPool and calls the method. If it is a multicast delegate, it will call that many Threads and call them. The AsyncCallBack is called when the thread execution is complete and the result can be obtained.

We have passed InvokeMessage to get the result. We simply cast the object into AsyncDelegate into our own delegate object and use EndInvoke to get the result back.

Conclusion

Thus we can see, it is very easy to make use of BeginInvoke and EndInvoke with delegates to create a new thread from ThreadPool, and we don't require to create the thread ourself.

[adodotnet]

Introduction into ADO .NET Data Services/RIA Services

This article is not that complex and will not give you any re-usable code in any shape way or form, but what it will hopefully do is give you a gentle introduction in how to get started with 2 of Microsofts newer data access offerings:


• WCF Data Services, formerly ADO .NET Data Services, formerly Astoria
• RIA Data Services (the new kid on the block)
formerly ['fɔ:məli] adv. 以前；原来This is not an advanced article for people that may have used these 2 data access areas for some time, rather it is a general overview of what can be done with these 2 different data access technologies and how you might go about doing some simple CRUD operations with them.Pre-Requisites

I wrote the attached demo code using Visual Studio 2010 BETA 2 / Silverlight 4 / RIA Services Preview, so the following are all considered to be pre-requistites

• Visual Studio 2010 RC
• ADO .NET Data Services 1.5 CTP1
• RIA Services Preview

And since both the ADO .NET Data Services code and RIA Services code makes use of SQL data, SQL server is also a pre-requisite.


ADO .NET Data ServicesWhat's It All About

ADO.NET Data Services were previously called "Astoria", and put plainly are used to expose data as resources (JSON/ATOM) using REST. As such the data is exposed as resources, and can be fetched using standard HTTP urls. It is also possible to delete, update and insert new data using REST. The RESTful resources are exposed using WCF under the covers, though looking at a typical ADO .NET Data Service you may not think so.

Since WCF is used as the actual service implementation, all the core logic that fetches data from the database is run on an application server, so can be behind a firewall, which helps maintain that nice 3 levels of physical secure seperation that we may all be used to.

I think this diagram explains it fairly well, where you can imagine the Database is on one box, the Data Access Layer (the ADO .NET Data Service) is on another physical box, and a Client app (such as Silverlight) may be running on yet another different box (basically the clients PC).




By exposing the relational data using REST we are able to use standard HTTP requests, and make use of various URLs to access the resources. We are also able to use standard HTTP verbs such as PUT/POST to update the resources, which in the end may translate into updating a row of relational data in the relational database (if you are actually using a relational database to expose the data in the first place, which you may not be).

But before we get into that, we need to understand how to create a ADO .NET Data Service. So lets go through that shall we.

STEP1

Is to define a Entity Model for the data, this is as easy (well for the demo app it is anyway), as creating a new Entity Model, and following the wizard through to completion, using your own SQL Server database connection string, and pointing to the WCFDataServicesDemoApp database you set up using the setup scripts provided, and discussed above.


STEP 2

Once we have a Entity Model we can then create a new ADO .NET Data Service to expose the relational data as resources. Again this is easy all we need to do is add a new item as shown below.



Once you have done that, you will have a new <YOUR_SERVICE_NAME>.svc item in your solution with the following boilerplate code in it.

using System;
using System.Collections.Generic;
using System.Data.Services;
using System.Data.Services.Common;
using System.Linq;
using System.ServiceModel.Web;
using System.Web;

namespace WCFDataServicesDemoApp.Web
{
    public class WebDataService1 : 
        DataService< /* TODO: put your data source class name here */ >
    {
        // This method is called only once to initialize service-wide policies.
        public static void InitializeService(DataServiceConfiguration config)
        {
            // TODO: set rules to indicate which entity sets and service 
            // operations are visible, updatable, etc.
            // Examples:
            // config.SetEntitySetAccessRule("MyEntityset", 
            //    EntitySetRights.AllRead);
            // config.SetServiceOperationAccessRule("MyServiceOperation", 
            //    ServiceOperationRights.All);
            config.DataServiceBehavior.MaxProtocolVersion = 
                DataServiceProtocolVersion.V2;
        }
    }
}

Believe it not you are nearly there with creating a baic ADO .NET Service. All you have to do it add the generic argument, which is the type of the EntityModel you created earlier, and decide which of your EnitySets you want to expose and what rights you want them to have. So for the demo app (which is an insanely trivial example) this looks like this:

using System;
using System.Collections.Generic;
using System.Data.Services;
using System.Data.Services.Common;
using System.Linq;
using System.ServiceModel.Web;
using System.Web;

namespace WCFDataServicesDemoApp.Web
{
    public class WCFDataService : DataService<DemoAppEntities>
    {
        // This method is called only once to 
	//initialize service-wide policies.
        public static void InitializeService(
		DataServiceConfiguration config)
        {
            config.SetEntitySetAccessRule("*", 
                EntitySetRights.All);
            config.DataServiceBehavior.MaxProtocolVersion = 
                DataServiceProtocolVersion.V2;
        }


        // Define a change interceptor for the Address entity set.
        [ChangeInterceptor("Addresses")]
        public void OnChangeAddresses(Address address, 
            UpdateOperations operations)
        {
            if (operations == UpdateOperations.Add ||
               operations == UpdateOperations.Change)
            {

                if (String.IsNullOrEmpty(address.City) ||
                    String.IsNullOrEmpty(address.Line1) ||
                    String.IsNullOrEmpty(address.PostCode))
                {
                    throw new DataServiceException(400,
                       "Can not save Address with empty City/Line1/PostCode");
                }
            }
        }

    }
}

Do not worry too much about the OnChangeAddresses() method, I will get to that later. So with this in place we should be able to test this service out in the browser, so we can do that using a number of urls, lets see some:

http://localhost:1183/WCFDataService.svc/

Yields this:

   <?xml version="1.0" encoding="utf-8" standalone="yes" ?> 
 <service xml:base="http://localhost:1183/WCFDataService.svc/" 
   xmlns:atom="http://www.w3.org/2005/Atom" 
   xmlns:app="http://www.w3.org/2007/app" xmlns="http://www.w3.org/2007/app">
 <workspace>
  <atom:title>Default</atom:title> 
 <collection href="Addresses">
  <atom:title>Addresses</atom:title> 
  </collection>
 <collection href="Customers">
  <atom:title>Customers</atom:title> 
  </collection>
  </workspace>
  </service>

....


原文地址

[adultsite]

VS2010七种武器成就开发大事

　　从VS 6到VS 2003，再到VS2005，再到VS2008，再到现在使用的Visual Studio 2010，从5月份BETA1测试到10月BETA2公开下载，这一次的Visual Studio 2010带来了许多令人振奋的新功能，包括提供更高的程序开发效率、更精简的程序代码、更佳的安全性能。可以说，Visual Studio 2010将是今年来的集大成者，必将成为开发者手中的利器。

　　就以古龙大侠的《七种兵器》为代表，说说Visual Studio 2010的几点开发特性吧：

　　长生剑:F#编程语言

　　剑是百刃中使用最多的兵器，纤柔又锋利，从战国时期的“鱼肠剑”到清朝七剑豪侠，是成大事的必要利器。VS 2010有一把锋利的剑——F#编程语言。它中集合了一个是微软研究院、剑桥和微软开发部联合进行的高级开发的高效.NET、混合了函数语言和物件导向程序编制语言，适用于并行编程、算法、技术和探索性开发可以高效且带有互操作性的来解决宽泛的软件问题。

　　Visual Studio 2010中已正式包含 Visual F#，作为一种常规的开发工具发布。 作为.NET Framework 家族的新成员，F# 提供类型安全、性能，以及类似脚本语言的工作能力，所有这些都是 .NET 环境的一部分。

　　F#为Visual Studio 2010带来了很大的改观。因为替代了局部程序中的元组，工作变得简单了。在异步编程和强类型对于浮点编码方面也提供的不错的解决方式。可以说F#是Visual Studio 2010中结合了众多优点的编程语言。

　　霸王枪:云计算开发服务平台

　　枪在百刃中霸道而难于驾驭，枪是历代大将军手中所向披靡、纵横天下的首选兵器。之所以说VS2010是前无古人的利器，是因为它支持云计算。VS2010中集合了Azure云计算开发服务平台，不但可以提供基础网络服务，更为开发者提供了Windows Live、Office Live，使之通过在Azure服务平台上开放API，来实现与异构平台和交流互动。

　　首先说Azure，这是VS2010 提供的云计算开发服务平台，而这个Azure 服务平台是什么的呢?就是是一个托管服务套件，它包括虚拟计算，可扩展存储以及自动化服务管理系统等。这些工具将会用来为微软的服务提供支持，其中包括MSN，Xbox Live，以及Office Online等等，实现服务的网络化。

　　再说说Azure的关键基础——Windows Azure，这可是Azure“云计算”基础，提供计算、存储、管理的功能，运行在微软遍布全球的数据中心架构之中，是咱们步入“云计算”时代的捷径。

　　碧玉刀:支持多家数据库

　　古龙大侠小说中，用碧玉刀是比喻诚实。因为诚实是做人的根本，是团队进取合作的基石。互联网是一个聚合、开放的年代，谁保守谁就落伍，谁开放谁就进步。聚合就需要开诚布公，VS2010不但可以支持微软自己的SQL Server数据库，更能够在IBM DB2以及Oracle数据库下做工作。

　　拳头:多窗口显示器支持

　　七种武器中，拳头也许是最不引人注意的武器，但却最有效、最直接，也最可靠。对于开发人员来说，多窗口显示器支持是一个实实在在的功能，因为现在越来越多的程序员开始拥有两台甚至多台显示器，极大地方便了开发工作。正是为了适应这种趋势，Visual Studio 2010添加了对多显示器的支持。


　　在多显示器环境下，我们可以把VS2010中的多个窗口布置在不同的屏幕上。比如我们可以将代码编辑器放置在主显示器中，将输出窗口，类图窗口，代码定义窗口等等提供辅助信息的窗口放置在副显示器中，这样我们就可以在主窗口中编辑代码，同时有需要的时候，可以及时地从辅助窗口中得到一些有用的辅助信息。可以想象，多显示器可以极大的提高我们的开发效率。

　　多情环:对并行计算的支持

　　多情环是一对闪闪发光的银环，环上有13道刻痕。它是一种很奇特的武器，它富于人情色彩，它不是最犀利的武器，但却是最勾魂的武器，它表现出来的有些温情和勾魂。那就是对开发者来说非常幸福的事情——对并行编程的支持。

　　• Visual Studio IDE对并行计算开发的大量支持。比如，Visual Studio 2010的调试器知道代码的并行特性，并且能够在调试程序的不同执行单元的时候，表现应用程序的状态。

　　• 非托管的C++库和编译器对并行计算的支持

　　• .NET Framework 4.0对并行计算的大量支持，包括PLINQ、并行语言语句等等

　　另外，Visual Studio 2010还提供了一个“并行性能分析器”，它可以帮助我们分析应用程序的性能瓶颈，找到需要并行处理和可以进行并行处理的地方，并以图形化的形式表现出来。这样，“并行性能分析器”配合着Visual Studio 2010，我们就可以轻松地实现应用程序的并行化。

　　离别钩:C++王者归来

　　离别钩是一对特殊的钩，使用它的要诀是：心神合一，招招不离一个“情”字。当初开始学习编程时，相信大家都学过c++吧，随着时间的推移，c++昔日的霸气已经不在，以至于作为Visual C++程序员，大家心里都很憋屈!大家都在问，Visual C++的前途在哪里?坚持C++还有没有意义?

　　现在有答案了，微软并没有忘记c++，在Visual Studio 2010中我们找到了答案，找到了C++的未来，作为下一代开发工具，当然不会错过对新的C++标准C++0x的支持。除了随着之前发布的Visual C++ Feature Pack而引入的TR1包含的部分特性外，还引入了4个重要的C++新特性。号称C++0x的“四大天王”。这些新特性的引入，C++必然会王者归来。

　　孔雀翎:基于WPF的体验和UI设计

　　孔雀翎在七种武器中是最美的，VS2010当然这种美并不是它多么的绚烂，而美丽完全在于它简约，简约而不简单是对它做好的诠释，微软VS2010中的界面变化是令人耳目一新的，从以前的Windows Forms(Windows窗体)发展到Windows Presentation Foundation(WPF)布局，也使得Windows界面媲美Mac程序的酷炫不再是遥不可及的奢望。

　　WPF同样被人调侃地称之为“我佩服”。作为WPF微软新一代图形系统，其运行在.NET Framework 3.0架构下，为用户界面、2D/3D 图形、文档和媒体提供了统一的描述和操作方法，此版本将用户体验从2D提升到3D。基于DirectX 9/10技术的WPF不仅带来了前所未有的3D界面，而且其图形向量渲染引擎也大大改进了传统的2D界面，比如Vista中的半透明效果的窗体等都得益于WPF。通过WFP提供的功能，程序员们开发界面将变得异常简单，而且可以同最新的Windows7相互协调，使用户以新的体验。

　　Visual Studio 2010作为微软着力打造的下一代开发工具平台，跟她的前任Visual Studio 2008相比，它拥有着无数诱人的特性，同时也寄托着无数人的期望。篇幅有限，先为大家介绍到这里吧，相信大家对Visual Studio 2010的成功还是抱有很大希望。

[nanhe0065]

下载地址： http://www.itpub.net/thread-1274491-1-6.html

[hyuknam]

微软全球资深副总裁张亚勤为您解密创新

读《变革中的思索》有感

利用将近一周的时间，迫不及待的将张亚勤博士的《变革中的思索》读完。其中有些内容反反复复看了好几遍，似乎每重复一次都有不同的收获，即使现在搁下了手中的书，但仍然有一种余音绕梁的感觉。这本书收集了作者生活中的一些杂记，如演讲访谈等。内容从技术到管理还有生活中的片段，每一处都透露着不同的“思索”。当今时代名人出书的很多，但我遇到的像这么实用而又真实的却很少。

书中的每一页每一个细节，在我的眼里都是那么的不同。尤其看第一部分“解码创新”，我是多么的渴望如果这些内容我知道的时间不是现在，而是在当时那该有多好。近年来云计算被渲染的风风火火，更巧的是前一段时间我曾经搜寻关于讲云计算的书籍。目前市面上的书就那么几本，书少的让人感觉到深奥而新颖，当看了这里的“云计算三部曲”，我一下似乎明白了好多，这种引领的方式让迷茫的人醒悟。张博士对创新，对技术的分析，书中收录的最早的追朔到2000年，而如今8年多了，世界发生了很大的变化，时代在变革，而这一切都温和了他当时的分析。因而我试图的幻想，如果当时我就聆听了这些……

“中国知造，慧及全球”，每一处都是那么的令人振奋。当读到对“四大发明”以及对古代科技的分析，以及和现在的现状的比较，无处不透露着高度而又常人不可迄及的理性。张亚勤博士把四大发明的阶段，以及当今阶段的创新做比较，使我深深的领悟了时代的变化，以及时代中的不同，在不同中如何才能持续的创新呢？书中给出我们一个简洁而又明了的答案——在变革中思索。在我心目，在大多数人心目中张亚勤博士是一个无比成功的人，是天才，但在“管理心得”中我则更看到的是他的谦虚和以及精益求精学习态度。令我印象很深刻还有书中那副书架图，在那个书架上几本书清晰可见，尽管这或许是一个有意与无意的片段，但我觉得透过这一角看到了他更真切的生活。我曾经看过一些把孙子兵法和管理结合的作品，而在这里的“管理心得”中同样可见，除了让人感到亲切而外，更意识到了如何对“经典”在时代变革中的思索。回眸历史，有好多好动的事令人感慨和惊讶，但感概和惊讶都没有用，有用的是在今天该如何，如何利用它，好多人迷茫，我也不例外，幸好我看到了张亚勤博士对经典的“思索”。

市面上关于介绍微软的书很多，而读到这里的所提及的微软，让人感觉却是那么的不同。亚勤博士是用微软作为一种载体，给我们传递一种理念，一种跨国公司的理念，一种成功的理念……“心灵的记忆”，看似朴实而生活的话的章节，而无处不透视着“变革的思索”无论“与基辛格博士的重逢”还是“放飞的母爱”，都让人无处不感到那是一种不同的境界，更是一种追求生活真谛的态度。

读这本书就像和张亚勤博士的一次心灵的交谈，谈话内容在心中萦绕，当然那几个公式是也记忆犹新（例如IT=IP+IQ）,这些都让人感到张亚勤博士不但是一位卓越的科技人员，而更是一位生活中的智者。大多数人认为张亚勤博士是天才，他的成功是不具有可复制性的，而我更觉得，这本书则是亚勤博士用雄鹰的视野，告诉大多数人应该走的路。

[貓哥是個傳說]

Introduction into ADO .NET Data Services/RIA Services
--------
哇，好強大。。。。。。。

[sql_db]

接分

[nalnait]

⊙﹏⊙b汗 都是广告

[--小F--]

看见了 就多少接点分

[SQL77]

[andysun88]

jf

[alfred_2006]

在岗，到的晚点！！！！

[sajiao]

帮我回答问题嘛。。。。。

[windowsmousetest]

HO~

[sych888]

JF............................

[昵称很不好取]