I came across a firebug error, "SyntaxError: syntax error " which took me a half an hour to crack, so hopefully I can help you not waste half an hour yourself!
The bug looks like this:
I googled and found out that it might be caused by a script-tag not having a src-attribute. But all my scripts have that! So... I ran it through fiddler, and lo and behold, it turns out the page couldn't even load my script - because I was doing an old-fashioned asp.net solution and I hadn't included the scripts-directory in my locations, doh!!:
Once I did so, case was closed. So the bug was between the keyboard and monitor...
torsdag den 29. november 2012
tirsdag den 20. november 2012
I'm looking into Microsoft Windows Workflow solutions - a really powerful tool, once you get the hang of it (it's a steep learning curve).
Testing a workflow is the easiest if you simply host the workflow within Visual Studio's own development web server. But I've found a debugging issue if you use a flowchart workflow as opposed to a sequential workflow.
In my case I was trying to step into a custom activity (a codeActivity), but no matter how I tried it, my breakpoints would not be hit. If I ran a sequential workflow, no problem, the breakpoints got hit.
The 'solution' was to simply start two instances of Visual Studio, load the solution into both and for the first one set the workflow project as the start-up project (and fire it up), and for the second one set the other project that's hitting the service (a console-application, in my case) and fire that one up. Having its own seperate managed instance ensured the workflow projects breakpoints were hit.
Another solution would be to add a 'Debugger.Break();'-statement, which would then, when hit, offer you a choice of debugging the solution. But it's far easier to just seperate the projects with two Visual Studio sessions.