nobody can be an expert in all things technical. Find something that you enjoy doing (that statement alone should be a bullet point), and become an expert in that thing. You don''t have to specialize to the point that you''re a niche player, but you can limit your scope such that you can be known as an authority in your chosen area.

系統(tǒng)維修流程圖解。

A problem I see over and over again on the ASP.NET forums is the following:
In a login page, if the user and password have been validated, the page developer wants to redirect to the default page. To do this, he writes the following code:
Session["Login"] = true;
Response.Redirect("~/default.aspx");
Well, this doesn‘t work. Can you see why? Yes, it‘s because of the way Redi

-- Set the eventsdeclare @on bitset @on = 1exec sp_trace_setevent @TraceID, 14, 1, @onexec sp_trace_setevent @TraceID, 14, 9, @onexec sp_trace_setevent @TraceID, 14, 6, @onexec sp_trace_setevent @TraceID, 14, 10, @onexec sp_trace_setevent @TraceID, 14, 14, @onexec sp_trace_setevent @TraceID, 14, 11, @onexec sp_trace_setevent @TraceID, 14, 12, @on.

CreateDate,lvc.The apply statement comes in 2 flavors: CROSS APPLY and OUTER APPLY. CROSS APPLY will return All records in the outer query that have a matching record returned by the inner function\query (Similar to an Inner Join).OUTER APPLY will return all records in the outer query whether they have a matching record in the inner function\query or not (Similar to an Outer Join).

import javax.swing.table.clearButton.addActionListener(new ActionListener() { public void actionPerformed(ActionEvent e) { actionClear();public static void main(String[] args) { DownloadManager manager = new DownloadManager();}}class Download extends Observable implements Runnable { private static final int MAX_BUFFER_SIZE = 1024;public Download(URL url) { this.url = url;

如果我們要把一個OrderResponseContext 對象插入到當前Operation Context的Outgoing Message Headers中，我們可以通過下面的代碼來實現(xiàn)：OrderResponseContext context = new OrderResponseContext();MessageHeader<OrderResponseContext> header = new MessageHeader<OrderResponseContext>( context);OperationContext.Current.OutgoingMessageHeaders.Add(header.GetUntypedHeader("name", "namespace"));

在MSMQ中，Message始終以O(shè)ne-way的方式進行發(fā)送，所以MSMQ具有天生的異步特性。在WCF中，MSMQ提供的數(shù)據(jù)傳輸功能被封裝在一個Binding中，提供WCF Endpoint之間、以及Endpoint和現(xiàn)有的基于MSMQ的Application進行通信的實現(xiàn)。在一般的情況下，MSMQ通過Message Queue Transaction實現(xiàn)對Transaction的原生的支持，借助Message Queue Transaction，可以把基于一個或多個Message Queue的相關(guān)操作納入同一個Transaction中。

在Service Contract中設(shè)置了Callback Contract，Callback Contract定義在Interface Artech.DuplexWCF.Contract. ICallback中：using System;using System.Collections.Generic;using System.Text;using System.ServiceModel;namespace Artech.DuplexWCF.Contract{ [ServiceContract] public interface ICallback { [OperationContract(IsOneWay = true)] void DisplayResult(double result); }}

1． Service Contract- Artech.ExceptionHandling.Contract.><configuration> <system.serviceModel> <client> <endpoint address=http://localhost:8888/Calculator binding="basicHttpBinding" contract="Artech.ExceptionHandling.Contract.ICalculator" name="defualtEndpoint" /> </client> </system.

><configuration> <system.serviceModel> <services> <service name="Artech.ExceptionHandling.Service.CalculatorService"> <endpoint binding="wsHttpBinding" contract="Artech.ExceptionHandling.Contract.ICalculator" address="http://localhost:8888/Calculator" /> </serv

WCF與Web Service不同的是，當我們定義了服務(wù)契約的操作時，不管是通過ChannelFactory創(chuàng)建服務(wù)代理對象，還是通過SvcUtil的默認方式生成服務(wù)代理對象，客戶端在調(diào)用這些代理對象時，都無法直接實現(xiàn)異步方式的調(diào)用。那么，客戶端究竟應(yīng)該如何執(zhí)行異步調(diào)用呢？}在調(diào)用異步方法時，由于對BeginTransferDocument()和EndTransferDocument()方法的調(diào)用可能會在不同的方法體中，因而我將服務(wù)代理對象定義為private字段。

WCF中的Session.如果通過以下的方式定義ServiceContract使之不支持Session，或者使用不支持Session的Binding（順便說一下，Session的支持是通過建立Sessionful Channel來實現(xiàn)的，但是并不是所有的Binding都支持Session，比如BasicHttpBinding就不支持Session），WCF實際上會為每個Service調(diào)用創(chuàng)建一個Service Instance，這實質(zhì)上就是PerCall的Instance Context Mode，但我為什么會說默認的是PerSession呢？

IFullWhetherForecast>, Artech.><configuration> <system.serviceModel> <client> <endpoint address="http://localhost/Artech.InheritanceHierarchy/FullWhetherForecastService.svc" binding="wsHttpBinding" bindingConfiguration="" contract="Artech.InheritanceHierarchy.Client.IFullWhetherForecast&quo

我們現(xiàn)在的Sample就是由兩個Request/Response MEP組成的Duplex MEP。從上圖中我們可以很清楚地看出真?zhèn)€Message Exchange過程，Client調(diào)用Duplex Calculator Service，Message先從Client傳遞到Service，Service執(zhí)行Add操作，得到運算結(jié)果之后，從當前的OperationContext獲得Callback對象，發(fā)送一個Callback 請求道Client（通過在Client注冊的Callback Channel：http://localhost:6666/myClient）。

Service{ [ServiceContract] public interface ICalculator { [OperationContract(Name = "AddWithTwoOperands")] double Add(double x, double y);OperationContractAttribute(Action="http://tempuri.org/ICalculator/AddWithThreeOperands", ReplyAction="http://tempuri.org/ICalculator/AddWithThreeOperandsResponse")] double AddWithThreeOperands(double x, d

Serialization 是通過Serializer來完成的，在WCF中，我們有3種不同的Serializer——DataContractSerializer（定義在System.RunTime.Serializtion namespace中）、XMLSerializer（定義在System.XML.Serialization namespace）和NetDataContractSerializer (定義在System.XML.Serialization namespace) 。private string _producingArea;所有運用了DataMemberAttribute的成員均被序列化到XML中——private string ProducingArea。

這個Project引用Artech.WCFService.Contract和Artech. Project WCFService.Service。這個Project引用Artech.WCFService.Contract、Artech.WCFService.Service和System.ServiceModel DLL。在這個例子中，當Artech.WCFService.Client調(diào)用Host在Artech.WCFService.Hosting中的DuplexCalculatorService（定義在 Artech.WCFService.Service中），Artech.WCFService.Client是Client，而Server端的執(zhí)行環(huán)境是Artech.WCFService.Hosting。

然后他會根據(jù)定義在Service中的Endpoint定義為calculatorSerivceHost添加相應(yīng)的Endpoint。<client> <endpoint address="http://localhost/WCFService/SessionfulCalculatorService.svc" binding="wsHttpBinding" bindingConfiguration="" contract="Artech.WCFService.Contract.ISessionfulCalculator" ><headers> <role>admin</role>

這個Project引用Artech.WCFService.Contract、Artech.WCFService.Service和System.ServiceModel DLL。//Create a Binding for Endpoint.<Endpoint Address="" Binding ="basicHttpBinding" contract="Artech.WCFService.Contract.ICalculator"></Endpoint><Endpoint Address="http://localhost：8080/WCFService/CalculatorService " Binding="basicHttpBinding" contra