MSDN Magazine October 2003
View Complete Post
The T-SQL language in the upcoming version of SQL Server will provide more power and flexibility than previous versions. Additions and enhancements include error handling with the TRY/CATCH construct, SNAPSHOT isolation, and WAITFOR enhancements. Also important are the BULK rowset provider, common table expressions, recursive queries, PIVOT and UNPIVOT operators, and much more. This article introduces these features so readers will be ready for the next version of SQL Server.
MSDN Magazine February 2004
The next version of SQL Server, code-named "Yukon," will offer enhanced support for user-defined types (UDTs). Because UDTs can be managed by the CLR, you can represent a wide variety of data structures to create types not possible with previous versions of SQL Server. With UDTs you can more precisely control the kind of data your type accepts, resulting in better data management. This article explores UDTs in "Yukon" and covers their design and implementation.
Peter W. DeBetta
MSDN Magazine December 2003
The growth of interconnected computers in recent years has pushed security concerns to the forefront of development and application design. The Microsoft effort, dubbed the Secure Windows Initiative (SWI), focuses on securing new and legacy code.
MSDN Magazine March 2003
Don Box has long been the preeminent expert on COM, as well as one of the creators of the SOAP protocol. He has written numerous books and articles including Essential COM (Addison-Wesley, 1997) and Essential .
MSDN Magazine December 2002
MSDN Magazine February 2002
I have created my first Custom asp.net server control.But i think such projects probably contains AssemblyInfo file.But i am missing that. When i created project that file was not added.
I am working on VS 2008 Team System Edition,with VB.NET language.How to get that file ?
I keep getting a HTTP 400 exception whenver I try to send a large message.
My service contains a messageContract that consists of 3 int32s and 1 stream (Regular stream, not memorystream or any other derrivative of stream)
When I send a messageContract that has the 3 ints and 48837 bytes on the stream, the sending and recieving work. When I set it to 48838 bytes, however, I get the following error:
System.ServiceModel.ProtocolException was caught
Message=The remote server returned an unexpected response: (400) Bad Request.
Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory factory, WebException responseException, ChannelBinding channelBinding)
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)