Assembly reference is missing after upgrade to hotfix 3 MBPM 9.2
Hi All,
after upgrading to hotfix 3 my project is missing some references. It cannot find the WCF namespace. I have looked in designer folder and the Metastorm.Common.Wcf.dll is there. I do not know what to search for now.
Appreciate any suggestions.
Here is the error from the Designer:
Error 2010-11-22 10:01:39 Solution36.CBG ManageOrder The type or namespace name 'WCF' does not exist in the namespace 'Metastorm.Runtime.Models.CBG' (are you missing an assembly reference?) 11 36
Comments
-
I have done some more tests. I can add a new webservice connection but when I create a server side script I cannot make a reference to my webservice connection.
I can not find the Metastorm.Runtime.Models."MyProject".WCF namespace. Anoyone who knows anything about the WCF assembly?
Best regards,
Magnus
0 -
Did you ever get a response/resolution to the missing WCF namespace? If so, what was the answer?
Thank you.
0 -
No, unfortunately not. It's a bug and it should be solved in version 9.1.
Best regards,
0 -
In most cases validation error "The type or namespace name 'WCF' does not exist in the namespace..." appears because of Server Script error, but Designer does not provide "real" error message.
If you see this message try to remove some server scripts code blocks until validation error disapears.
0 -
Hi,
I'm new to Metastorm and not sure which version I'm running exactly at this moment, but I'm trying to create a simple implementation with a webservice and am facing a similar error-message.
For this I'm looking at the example-projects in the ScriptedBusinessObjects-solution.
In my own server-side script I can create a using to the namespace Metastorm.Runtime.Models.Project1.WCF.TestWebService, but as soon as I want to instantiate an object like I would normally do when calling a WCF-service, (in this case use the ITestService-interface) I get the exception:
Error 10/26/2011 11:05:43 AM The type or namespace name 'WCF' does not exist in the namespace 'Metastorm.Runtime.Models.Project1' (are you missing an assembly reference?) 16 41
Removing the creation of the instance and the code is validated perfectly.
So the namespace is available, also in the intellisence, so it makes no sence to me.
Thanks in advance for any help.
0 -
The version of Metastorm displayed in the designer is: 9.1.0.1861
0 -
In my experience errors such as this are usually caused through another and unrelated error in a script and Neon's earlier post is a good way of tracking this kind of error down. Server-side scripts in Metastorm are prone to displaying all sorts of unrelated and meaningless errors and it takes a methodical approach to find the real culprit. I have seen 900 odd errors being generated from a single and simple error.
The other thing to check with web services is that you have checked the f(x) box for the methods you wish to use, and if you refresh the web service you'll need to re-check them.
0
Categories
- All Categories
- 123 Developer Announcements
- 54 Articles
- 154 General Questions
- 149 Thrust Services
- 57 Developer Hackathon
- 37 Thrust Studio
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 918 Core Messaging
- 84 Digital Asset Management
- 9.4K Documentum
- 33 eDOCS
- 190 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 10 XM Fax
- Follow Categories