This column crafts an XML document to hold the mouse environment simulation data and shows how to incorporate an XML file into the program using a DataSet.
Stanley B. Lippman
MSDN Magazine October 2007
View Complete Post
This month begins the design of the actual mouse class for EEK!
MSDN Magazine December 2007
Stanley B. Lippman explores the use of C++/CLI as a pure Microsoft .NET Framework-compliant language.
MSDN Magazine August 2007
Stanley Lippman begins a look at using C++/CLI as a purely .NET-compliant language.
MSDN Magazine June 2007
In this installment, Stanley Lippman continues to port his ISO-C++ Text Query Language application to the Microsoft .NET Framework and C++/CLI.
MSDN Magazine April 2007
This month Stanley Lippman begins translating the Text Query Language Query class hierarchy from C++ to the .NET Common Type System.
MSDN Magazine February 2007
Stanley Lippman moves Text Query Language to the Microsoft .NET Framework using the C++/CLI language extensions in Visual C++ 2005.
MSDN Magazine December 2006
This month Stanley Lippman introduces the support for regular expressions in the .NET Framework.
MSDN Magazine November 2006
Last time Stan Lippman did not consider the visibility of types and nondeterministic finalization in writing his TQL wrapper code. This month he rewrites the code.
MSDN Magazine August 2006
This month, we are changing the column name from Pure C++ to Netting C++ to better reflect our focus on MicrosoftÃÂ® . NET programming using C++/CLI, the . NET extensions to Visual C++ÃÂ® that are supported in Visual StudioÃÂ® 2005.
MSDN Magazine June 2006
I made a simple MDX query to get remaining work, completed work of all work items per revision number
[Work Item].[System_Id].[System_Id] *
Apologies if the question has been asked before but I've done a search and wasn't able to find an answer.
Our web application (hosted in IIS) exposes a WCF web service which takes an XML document as an argument, that document should confirm to a (public) XSD schema already defined in our application.
Current the contract looks as follows
void LoadData(string identifier, byte xmlData)
We've got a MEX (meta-data exchange) endpoint set up so that clients can use something like svcutil.exe or WcfTestClient to discover the service details.
<Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">http://tempurg.org/WebServices/LoadService</Action>
<identifier d4p1:nil="true" xmlns:d4p1="http://www.w3.org/2001/XMLSchema-instance" />
However, this doesn't give the client a clue as to what the XML document (byte) should look like/conform to. What app