update of workflow / activity implementation, what happen topersisted instances?

  • Thread starter Thread starter newsgroup.poster
  • Start date Start date
N

newsgroup.poster

I'm managing an existing application, the source code is laid such as
(in multiple solutions):
- business model entities dll
- workflow activities dll
- workflow implementation dll (which contains a single state machine
workflow)
- a web application
- a web service managing workflow instances

the problem is that the source was gaven to me in a "stale state",
what I mean is business model, workflow activities and web application
where modified to encapsulate things in a nicer manner, but the
workflow implementation wasn't updated.

now I need to update the "in production" application, and I have two
issues:

- the workflow designer isn't available because both activities within
it and logic is out of sync with the current version of dependencies
source code
- If I manage the first issue (hopefully the workflow is a simple
one), I don't have any clue on what will happen to persisted workflows
(persisted in mssql db) if I update the current deployed workflow.

Anyone can give me clue on wether or not I'm stepping into a disaster
about the second issue? If this is a disaster, what is are the steps
to follow to avoid it?

Also, I find intriguing there isn't even wwf newsgroup around?

Thanks for your support.

Gauthier Segay
 
Hello (e-mail address removed),

Nothing happens, your existed persisted WF just throw an exception and won't
work.
The only reason of this is that WF doesn't support versioning - whenever
u change the WF u lost support of persisted WFs

Everything you can do, is ends up with the different version of WF and maintain
them manually.

---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
 
Thanks for your precise answer, that all I'm worried about. Now I need
to reverse engineer the "released" workflow and find some "not so
nice" workaround.

I'm not expert with worfklow foundation, but this look like a serious
limitation in the use I intend to make of them.

Best regards,

Gauthier Segay

Hello (e-mail address removed),

Nothing happens, your existed persisted WF just throw an exception and won't
work.
The only reason of this is that WF doesn't support versioning - whenever
u change the WF u lost support of persisted WFs

Everything you can do, is ends up with the different version of WF and maintain
them manually.

---
WBR,
Michael  Nemtsev [.NET/C# MVP] :: blog:http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
I'm managing an existing application, the source code is laid such as
(in multiple solutions):
- business model entities dll
- workflow activities dll
- workflow implementation dll (which contains a single state machine
workflow)
- a web application
- a web service managing workflow instances
the problem is that the source was gaven to me in a "stale state",
what I mean is business model, workflow activities and web application
where modified to encapsulate things in a nicer manner, but the
workflow implementation wasn't updated.
Click to expand...
now I need to update the "in production" application, and I have two
issues:
Click to expand...
- the workflow designer isn't available because both activities within
it and logic is out of sync with the current version of dependencies
source code
- If I manage the first issue (hopefully the workflow is a simple
one), I don't have any clue on what will happen to persisted workflows
(persisted in mssql db) if I update the current deployed workflow.
Anyone can give me clue on wether or not I'm stepping into a disaster
about the second issue? If this is a disaster, what is are the steps
to follow to avoid it?
Click to expand...
Also, I find intriguing there isn't even wwf newsgroup around?
Click to expand...
Thanks for your support.
Click to expand...
Gauthier Segay
Click to expand...
Click to expand...
 
Hello (e-mail address removed),

Read there about some implementations of versioning http://www.sitechno.com/Blog/WorkflowVersioningOfLongRunningProcessesSucksHereIsMyTakeOnIt.aspx


---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

Thanks for your precise answer, that all I'm worried about. Now I need
to reverse engineer the "released" workflow and find some "not so
nice" workaround.

I'm not expert with worfklow foundation, but this look like a serious
limitation in the use I intend to make of them.

Best regards,

Gauthier Segay

Hello (e-mail address removed),

Nothing happens, your existed persisted WF just throw an exception
and won't
work.
The only reason of this is that WF doesn't support versioning -
whenever
u change the WF u lost support of persisted WFs
Everything you can do, is ends up with the different version of WF
and maintain them manually.

---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog:http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo
I'm managing an existing application, the source code is laid such
as
(in multiple solutions):
- business model entities dll
- workflow activities dll
- workflow implementation dll (which contains a single state machine
workflow)
- a web application
- a web service managing workflow instances
the problem is that the source was gaven to me in a "stale state",
what I mean is business model, workflow activities and web
application
where modified to encapsulate things in a nicer manner, but the
workflow implementation wasn't updated.
now I need to update the "in production" application, and I have two
issues:

- the workflow designer isn't available because both activities
within
it and logic is out of sync with the current version of dependencies
source code
- If I manage the first issue (hopefully the workflow is a simple
one), I don't have any clue on what will happen to persisted
workflows
(persisted in mssql db) if I update the current deployed workflow.
Anyone can give me clue on wether or not I'm stepping into a
disaster
about the second issue? If this is a disaster, what is are the steps
to follow to avoid it?
Also, I find intriguing there isn't even wwf newsgroup around?

Thanks for your support.

Gauthier Segay
Click to expand...
Click to expand...
Click to expand...
 
Back
Top