This month Juval Lowy tackles questions such as when to keep proxies and services in memory for better state management in long-running workflows.
MSDN Magazine October 2008
View Complete Post
This month's column describes how to use WCF for communication between a workflow and a host application in Windows Workflow Foundation 3. This knowledge should help developers with their efforts using WF3 and prepare them for WF4, where WCF is the only abstraction over queues (referred to as "bookmarks" in WF4) that ships with the framework.
MSDN Magazine November 2009
Managing state and error recovery using transactions is the topic of this month's installment of Foundations.
MSDN Magazine January 2009
With the NET Framework 3.5, Windows Workflow Foundation can now truly be integrated with Windows Communication Foundation. This column describes how the integration works and how to make use of it effectively.
MSDN Magazine Launch 2008
MSDN Magazine March 2007
ASP.NET provides many different ways to persist data between user requests. You can use the Application object, cookies, hidden fields, the Session or Cache objects, and lots of other methods. Deciding when to use each of these can sometimes be difficult. This article will introduce the aforementioned techniques and present some guidelines on when to use them. Although many of these techniques existed in classic ASP, best practices for when to use them have changed with the introduction of the .NET Framework. To persist data in ASP.NET, you'll have to adjust what you learned previously about handling state in ASP.
MSDN Magazine April 2003
Running a Web farm means managing session state across servers. Since session state can't be shared across a Web farm with Internet Information Services 5.0, a custom solution is required. One such solution using a tool called the session manager is described here. The article begins with a description of the SQL Server database used to store state information, the stored procedures used to update it, and the retrieval of session data. ASP code drives the session manager tool and the COM and COM+ components that run the stored procedures.
MSDN Magazine October 2000
I'm trying to use two web services with the related wsdl files. I haven't implemented these web services and the wsdls.
In SSIS 2005, as the Http connection I'm using a link f.e. this:
http://mysite/webservices/mywebservice?wsdl. In this manner, in a web service task I can download the first wsdl (it is strange that I specify for the WSDLFile path also the file name before to download the file). For the first wsdl I can select the service
and then the method. I have created a second web service task: then I have use the same http connection and I have download the second wsdl (for the WSDLFile path I have the same case for the 1st wsdl), but I cannot see any services and so any methods.
Well, if I open each single wsdl I can see a certain set of xml elements, but if I open the wsdl from the link
http://mysite/webservices/mywebservice?wsdl=mywebservice.wsdl I can see a merged wsdl file. I hope to have given an idea of the issue. How can I manage these particular WSDLs in
SSIS 2005 (or SSIS 2008), please?
Many thanks for your suggests
I'm trying to do a SQL 2008 cluster installation.I installed one node and now I'm trying to add a failover cluster node.in the "add Node Rules" I get following message:---------------------------Rule Check Result---------------------------Rule "SQL Server Database Services feature state" failed.
The SQL Server Database Services feature failed when it was initially installed. The feature must be removed before the current scenario can proceed.---------------------------OK ---------------------------Can anyone help me?