Difficulty using a new version of a library.

Apperson_Rory

I'm using version 9.0.3.0 of the designer.  I have a project which has been successfully referencing a library I deployed a while ago that contained a single script class in a single namespace. 

 

I did some refactoring today and created a second class with the same namespace in that library and deployed it.  I'm having an incredibly difficult time getting my project to use the new version of the library.  I'm seeing all sorts of quirky things going on. 

 

I've tried simply right-clicking on the library under "Referenced Libraries" and updating, but the script inside my project seems to still be looking at the old version of the library even though the properties on the referenced library now say the new version.  Then, when I save and close out of the project and come back in, suddenly the project's code cannot even see the library code's namespace anymore.

 

I've tried going to the repository and to the library and using "Add this library to current project" and/or "Retrieve latest version" but  neither of those work either: I have similar difficulties as stated above.

 

Does anyone know of a difinitive way, using the version of BPM that I'm running, to properly implement a new version of a library?  I don't want to have to install the latest version of the designer because I know you have to keep it in sync with the back end and, in my experience deploying new versions of the Metastorm back-end, that could mean 20+ hours on the phone with the help desk (no exaggeration -- I kept track of  my time for my boss when we tried to install SP3).

 

Any thoughts would be much appreciated.

 

-Rory

 

 

Prakash__Kanchan

You might have to clear your designer cache

 

/awd/forums/questions/3402857

Apperson_Rory

Interesting.  Thanks for that.  I opened up a ticket with the help desk, and they gave me a (no-so-great) work-around, but this wasn't mentioned.  I'll keep this in mind next time I see this.