Tech-IS Home   Forum Home   Search   Login   Register  
OxyGen Code  > WCF related  > The name 'bPagingInfo' does not exist in the current context  
 
Display using:  
Previous Thread :: Next Thread 
 Author Thread: The name 'bPagingInfo' does not exist in the current context
rs727 is not online. Last active: 11/2/2011 5:34:13 PM rs727
Top 25 Poster
Joined: 03 Oct 2011
Total Posts: 4
 
The name 'bPagingInfo' does not exist in the current context
Posted: 18 Oct 2011 10:41 AM
Error: The name 'bPagingInfo' does not exist in the current context ...WCF\Generated\ServiceInterface.cs MyApp.Wcf

Everything compiles fine execept the wcf project -- I can see alll stored procs and entities so this is a bit perplexing.
Arinze is not online. Last active: 6/6/2014 1:59:48 PM Arinze
Top 25 Poster
Forum Moderator
Joined: 02 Feb 2008
Total Posts: 165
 
Re: The name 'bPagingInfo' does not exist in the current context
Posted: 18 Oct 2011 09:04 PM
i haven't been able to reproduce your error, i may need more info.

are you running version 3.6.9?

how is your wcf configured:

'rest' or 'standard' ?

'rcp' or 'messaging' ?

for standard wcf (rpc _style,) an operation that involves paging, should look like the following:


public departmentqueryresult getalldepartment(paginginfo paginginfo)
{
list serviceresponse;
xccx.business.paginginfo bpaginginfo = servicemapper.convert(paginginfo);

list businessresult;
xccx.business.humanresources.humanresourcesservice businessservice = new xccx.business.humanresources.humanresourcesservice();

businessresult = businessservice.getalldepartment(bpaginginfo);
serviceresponse = businessresult.convertall(p => servicemapper.convert(p));

departmentqueryresult responseinstance = servicemapper.convert(serviceresponse, bpaginginfo);
return responseinstance;
}



you can see how 'bpaginginfo' is used in the operation

OxyGen Code Generator, the Architected RAD Tool for .NET
rs727 is not online. Last active: 11/2/2011 5:34:13 PM rs727
Top 25 Poster
Joined: 03 Oct 2011
Total Posts: 4
 
Re: The name 'bPagingInfo' does not exist in the current context
Posted: 27 Oct 2011 11:45 AM
The error appears only if you choose to implement "Intercepts" Also, the if (!Intercept.... condition will create the context error with vs2008 and oxygen v3.6.9.0
Arinze is not online. Last active: 6/6/2014 1:59:48 PM Arinze
Top 25 Poster
Forum Moderator
Joined: 02 Feb 2008
Total Posts: 165
 
Re: The name 'bPagingInfo' does not exist in the current context
Posted: 27 Oct 2011 05:01 PM
hi rs 727,
Thanks for tracking it down.

You have the option of not implementing intercepts at the WCF level, is that a feasible solution for you?

We will get an updated version out ASAP


OxyGen Code Generator, the Architected RAD Tool for .NET
Arinze is not online. Last active: 6/6/2014 1:59:48 PM Arinze
Top 25 Poster
Forum Moderator
Joined: 02 Feb 2008
Total Posts: 165
 
Re: The name 'bPagingInfo' does not exist in the current context
Posted: 07 Nov 2011 11:39 PM

Hi guys,

this issue has been fixed in version 3.6.12

Please download the latest version of OxyGen Code.

Note: If you are switching from context based code to non-context based code, you may have to delete the files in the 'Durable' folder.

Leave a question if you have any.

Thanks


OxyGen Code Generator, the Architected RAD Tool for .NET
Previous Thread :: Next Thread 
Page 1 of 1
 
Tech-IS Forums  > OxyGen Code  > WCF related  > The name 'bPagingInfo' does not exist in the current context