How has debugging improved from Workflows 3.5 to Workflows 4.0.
View Complete Post
Trying to remote debug ASP website from VS2010 Pro to Windows Server 2003 machine. Specifically, trying to debug a Web Service, but breakpoint says, "The breakpoint will not currently be hit. No symbols have been loaded for this document." This happens for all compiled code though. I have read this is due to missing PDB files and the work around is to manually copy them, as noted here. Problem is, I cannot find any PDB files for my project, except referenced libraries, which I can remote debug.
This is beyond frustrating. I migrated my code from VS2008 .Net3.5 to VS2010 .Net4.0 to take advantage of the inherent multithreading framework. Debugging works when using local host and was stable until deployment to test server.
Thanks in advance,
I'm new to HttpHandlers. I am writing an HttpHandler that reads uploaded files directly from the request stream to provide progress that can be queried using an AJAX request. For large files, this seems to be faster than having ASP.NET load the file contents into Request.Files and then streaming the file from there to wherever it goes (Linq to SQL into a VARBINARY column in an SQL Server database.)
My HttpHandler works perfectly when I'm debugging using the Visual Studio Development Server, but doesn't work otherwise. The application pool for this application in IIS 7 is set to run in Classic Mode, and the Handler Mappings screen in IIS says that I must manage managed handlers in system.web/httpHandlers.
I set up in my applications Web.config file.
<add verb="GET,POST" path="*.upload" type="Namespace.For.UploadHandler, AssemblyForUploadHandler"/>
It works great, so long as I don't debug with the "Use Local IIS Web server" option.
What else do I need to do to get this to work?
I'm finished with a part of my ASHX handler and need to test it against the software that'll be calling it using HTTP POST. The software required an https url so I created an internally hosted site in IIS and published the project there.
Question now is how do I do any debugging on the script to see what data is coming out of it before the data goes back into the software that's calling it? Do I set something on the project itself to be able to step into the published DLL?
The .NET Framework 4 makes it easier than ever to implement WCF services using WF. We'll demonstrate just how easy it is by modeling a long-running, durable and instrumented workflow based on a real-world business case without having to write any code.
MSDN Magazine May 2010
Justin Marks shows how to use the IntelliTrace feature coming with Visual Studio 2010 Ultimate, which gives developers powerful new debugging tools to "turn up the dial" and collect the complete execution history of an application, get deeper levels of information and quickly find bugs.
MSDN Magazine April 2010
In this article, the author covers the new features in SharePoint 2010 geared for workflow developers and thenÃÂ walks the readerÃÂ through a couple of new user scenarios.
MSDN Magazine November 2009
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.
In Visual C++ 10 and the Microsoft .NET Framework 4, Microsoft is introducing new libraries and runtimes to significantly ease the process of expressing parallelism in your code base, together with new tool support for performance analysis and debugging of parallel applications. In this article, you will learn about debugging support in Visual Studio 2010, much of which is focused on task-based programming models.
Stephen Toub, Daniel Moth
MSDN Magazine September 2009
Design patterns provide a common, repeatable approach to solving software development tasks, and many different patterns can describe how to accomplish a certain goal in code. When developers begin working with Windows Workflow Foundation (WF), they often ask about how to accomplish common tasks with the technology. This month's column discusses several design patterns used in WF.
MSDN Magazine August 2009
Integrating workflow into ASP.NET applications means communicating with activities via a workflow queue and hosting the runtime in the global application class. We'll show you how.
MSDN Magazine January 2009
The heart of Windows Workflow Foundation is its declarative programming model. Here are some best practices to consider when using WF to realize software solutions in the real world.
MSDN Magazine December 2008
This month we explain how pseudo variables and format specifiers provide a wealth of information for use in debugging.
Matt Milner addresses reader requests for information about safely sharing a persistence database across applications and using lesser-known parts of the framework such as ChannelManagerService.
MSDN Magazine August 2008
When building workflows, you must consider the developer experience, available tools, long-term maintenance, and future versioning.
MSDN Magazine May 2008
This month, a better design-time experience for Web apps, Scott Guthrie's blog, extending Extend Lutz Roeder's Reflector, and more.
MSDN Magazine March 2008
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