Work Life - like park life, but paid better - All Comments

re: Setting a CollapsiblePanelExtender state from CodeBehind

ZeroCool — Wed, 05 Mar 2008 09:44:45 GMT

But when I create and add multiple CollapsiblePanelExtender controls, it will always throw an exception says that there're multiple controls with the same ID '_ClientState', how to solve this problem? SOS!

re: Setting a CollapsiblePanelExtender state from CodeBehind

Thu, 21 Feb 2008 21:11:56 GMT

I LOVE YOU! YOU SAVED MY DAY!

re: Using multiple Task forms in a single workflow

Raghav — Wed, 20 Feb 2008 10:24:09 GMT

What's alternative to work with multiple Task form with aspx

re: Forcing a Partial Postback from JavaScript

Luke Smith — Fri, 08 Feb 2008 20:12:31 GMT

I'm suprised the functionality isn't built into the MS Ajax framework itself, it seems like an obvious thing for people to want to do. I've needed it once or twice and discovered this solution.

One thing I also hate is having to put javascript in the page itself, but also hate having to hardcode ctl00_blah_blah_mycontrol in an external javascript file (just incase it changes at some point). I experimented with a creating a jsx page a while back, where the jsx page was parsed on request to the page and you could put things like <%= MyControl.ClientID %> in it. Maybe i should dig it out and post it on my blog.

re: Building a WSP with Infopath Forms

Martin — Tue, 18 Dec 2007 19:19:49 GMT

The xsn files were missing from the feature directory.

Entries like

in <ElementManifests> of feature.xml fixed it.

Martin

re: Building a WSP with Infopath Forms

Martin — Tue, 18 Dec 2007 19:02:28 GMT

Hello Tom,

I'm trying to deploy a workflow to a live server in a wsp file.

My workflow works on the development server.

Once deployed, the task forms apparently can't be found (they don't have any code behind - they just use rules)

The wsp file is structured like this...

The assembly and manifest.xml are in the root

It has the forms (all task) feature.xml and workflow.xml in a sub directory that is the name of the feature.

The feature directory under the 12 hive initially contained just the feature.xml and the workflow.xml

I manually extracted the xsn files from the wsp and put them in the feature dir as well.

Still when I click on a task created by the workflow, Forms Services gives me the message "The form has been closed".

In the sharepoint log, I get a message from Forms Server saying the specified form cannot be found.

The feature.xml has a property setting like this

Just to reiterate - this works on my development server.

Any suggestions much appreciated.

Thanks

Maritn