.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
MarieAdela
Imran Ghani
Post New Web Links

Workflow in two sides : SQL Persistence in the WCF Service side + Workflow logic in the client side

Posted By:      Posted Date: October 11, 2010    Points: 0   Category :WPF
 

Hi,

I'm new in Windows Workflow Foundation 3.5, and I red some documentation.

Now, I would like to know if an architecture is possible in my case :

- WCF service with SQL Service access : put in it the Workflow SQL Persistence. I know that this part can be ok alone.

- Client side (ASP.Net) : put in it the Workflow logic. Ex : know when we are in a given state, and display icons and text related to this state, and know what is the next available step.

Is this architecture possible, and how to manage it in a few words ?

Thanks.




View Complete Post


More Related Resource Links

Extreme ASP.NET: Client-Side Web Service Calls with AJAX Extensions

  

Microsoft AJAX Library and the ASP.NET 2.0 AJAX Extensions provide a number of compelling features ranging from client-side data binding, to DHTML animations and behaviors. Learn all about them here.

Fritz Onion

MSDN Magazine January 2007


Windows Workflow Persistence Service using Oracle Database

  

Hi,

We are using windows state machine workflow. We need to use Oracle for persisteing and tracking workflow instances. Can anyone provide custom services for Oracle?

We have even tried WFTools but not able to connect to Oracle database. Please provide the same code if anyone has tried.

 

 

 

 


SharePoint Workflow : Failed to Start when a document is added to library from server-side object mo

  

When I add a document using my server-side object model code, I get an exception "The type or namespace name 'Office' does not exist in the namespace 'Microsoft'" in the server logs and in the library I can see the Workflow status as "Failed to Start".

...

myLibrary.Files.Add(...);

myLibrary.Update();

...

Interestingly, when I add a document to the same library from sharepoint site portal, it works just fine, the workflow kicks off with the state : in-progress.

Also, I modified the task form for the Approval workflow template from SharePoint Designer using infopath.(Not sure if that be a problem as adding from portal works fine.)

What am I missing out here??

 Details of the exception:

09/29/2010 18:11:19.15  w3wp.exe (0x2508)                        0x2710 SharePoint Foundation          Workflow Infrastructure        98d8 Unexpected Microsoft.SharePoint.SPException: <Error><CompilerError Line="0" Column="20" Text="The type or namespace name 'Office' does not exist in the namespace 'Microsoft' (a

WCF session client service reference "State" is not updated when the server side has closed

  

I am using vb.net (Visual Studio 2008 with framework 3.5). I have a server that exposes several services requiring sessions. I am using wsHttpBinding for all. One of my requirements is to allow non-dot net third parties to access these services. When a client connects to a service and then some time later the server goes away, the state of the connection is still reporting "open".

Currently I have implemented a "ping" function on the server. My client calls this function every 5 to 10 seconds and if the server does shutdown, I get alerted with an exception error. This works, but I was wondering if there is a way where I don't have to call my ping function?

I don't want to use a dual connection binding and I was hoping to use the connection state variable? But, I don't know how to get it to update by itself. The client user application could just wait until it goes to invoke a service method, but I was wondering if there was another way.

Thanks in advance!!

 


WCF durable service - retrieve token id on the client side problem

  

Hi,

I've created WCF durable service (service class marked as DurableService) with SQL persistent provider. The client invokes the service method marked as DurableOperation(CanCreateInstance:=True), after this - service successfully creates entry in the InstanceData table in sql database. Inside the service I can access the token id by using

OperationContext.Current.IncomingMessageProperties.Item("newDurableInstanceIdProperty")



 

If I understand the concept of WCF durable services, client could get this token and use it later to recreate the service state. Here I have:

Dim proxyActionParserService As New ActionParserService.ActionParserWorkerServiceClient



Dim contextManager As IContextManager = proxyActionParserService.InnerChannel.GetProperty(Of IContextManager)()



which one is the good practice to consume WCF/Web Service in client side ?

  

Hi

There are so many method to consume webservice/WCF in client side, like using Jquery and Ajax Scriptmanger. Which one is good practice to implement in

project and why ? could you share your opinion ?

 

Thank you


Use jQuery and ASP.NET AJAX to build a client side Repeater

  
By sending only data to the client, you can profoundly reduce the size of what you send and see a substantial increase in performance. You also allow yourself the ability to easily add features like light-weight sorting and paging on the client. This can not only improve your users' experience, but reduce server load and bandwidth requirements.

Client Side Gridview Pagination using JQuery

  
I would like to show how to use Client Side Gridview Pagination using Jquery Table Pagination Plugin by using Ryan Zielke.

Use jQuery and ASP.NET AJAX to build a client side Repeater

  
By sending only data to the client, you can profoundly reduce the size of what you send and see a substantial increase in performance. You also allow yourself the ability to easily add features like light-weight sorting and paging on the client. This can not only improve your users' experience, but reduce server load and bandwidth requirements.

To that end, I'm going to walk you through these four steps to effectively implementing a client side Repeater, using ASP.NET AJAX and jQuery:

Use jQuery and ASP.NET AJAX to build a client side Repeater

  
By sending only data to the client, you can profoundly reduce the size of what you send and see a substantial increase in performance. You also allow yourself the ability to easily add features like light-weight sorting and paging on the client. This can not only improve your users' experience, but reduce server load and bandwidth requirements.

Adding Client-Side Confirmation When Deleting

  
The JavaScript confirm(string) function displays its string input parameter as the text inside a modal dialog box that comes equipped with two buttons - OK and Cancel (see Figure 1). The confirm(string) function returns a Boolean value depending on what button is clicked (true, if the user clicks OK, and false if they click Cancel).

Cutting Edge: ASP.NET AJAX and Client-side Templates.

  

AJAX is meant to go beyond mere partial page rendering. Find out where Dino Esposito thinks dynamic pages are headed in the future with ASP.NET AJAX.

Dino Esposito

MSDN Magazine June 2008


Cutting Edge: The Client Side of ASP.NET Pages

  

This month Dino Esposito dissects the client-side source code generated by ASP.NET pages.

Dino Esposito

MSDN Magazine December 2006


Web Service Workflows: Deploy Distributed Business Processes With Windows Workflow And Web Services

  

Due to the distributed nature of a business process it makes sense for a workflow to be deployed as a distributed application. See how Windows Workflow and Web Services hold the key.

Israel Hilerio

MSDN Magazine October 2006


Cutting Edge: ASP. NET Client-side Hosting with Cassini

  

In the September and October 2000 issues of MSDN® Magazine I discussed how to build a client-side environment for ASP applications; that is, a serverless environment to run ASP pages (see Cutting Edge: A Client-side Environment for ASP Pages and Cutting Edge: A Client-side Environment for ASP Pages-Part 2).

Dino Esposito

MSDN Magazine January 2003


Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend