Problems with Microsoft.Dynamics.Framework.Portal

[Woodfarm]

Hi!

We are having problems using the Microsoft.Dynamics.Framework.Portal from
dynamics ax 2009

In all the classes where the call Microsoft.Dynamics.Framework.Portal... is
used there is a compiler error "syntax error".

From Dynamics ax it is possibel to se the following methods:

Microsoft.Dynamics.Framework.Collections
Microsoft.Dynamics.Framework.Deployment
Microsoft.Dynamics.Framework.Expression
Microsoft.Dynamics.Framework.Metadata
Microsoft.Dynamics.Framework.ResourceMgr
Microsoft.Dynamics.Framework.Workflow

but not .Portal

the line with fails is

Microsoft.Dynamics.Framework.Portal.UI.WebControls.AxBoundField boundField;

[Luegisdorf]

Hi Woodfarm

Have encountered similar problems (AX 2009 RU3) and solved it when
installing the Business Connector on the machine where the compile is
running. After, all compiles well.

Regards
Patrick

Post by Woodfarm
Hi!
We are having problems using the Microsoft.Dynamics.Framework.Portal from
dynamics ax 2009
In all the classes where the call Microsoft.Dynamics.Framework.Portal... is
used there is a compiler error "syntax error".
Microsoft.Dynamics.Framework.Collections
Microsoft.Dynamics.Framework.Deployment
Microsoft.Dynamics.Framework.Expression
Microsoft.Dynamics.Framework.Metadata
Microsoft.Dynamics.Framework.ResourceMgr
Microsoft.Dynamics.Framework.Workflow
but not .Portal
the line with fails is
Microsoft.Dynamics.Framework.Portal.UI.WebControls.AxBoundField boundField;

[Anders Nielsen]

Hello there.

Since last week we have experienced the same problem.

We cant compile code that uses
Microsoft.Dynamics.Framework.Workflow.Portal and
Microsoft.Dynamics.Framework.Workflow.BusinessConnector

The problem seems to have surfaced out of nowhere, since we didnt have the
problem a week ago.

I have tried reinstalling the Business connector on the AOS server but it
didnt help.

Does anybody have any ideas of what could be the problem ?

[Bill Thompson]

Hello,
Remember that the compile is CLIENT based, so the client where the compile
is being done is where the .NET BC should be installed. Compiles are always
done at the client tier, so the business connector needs to be installed on
the same tier to get this to work.

Bill 'Luther' Thompson
Microsoft Online Support Engineer - MBS Dynamics AX Developer Support

=============================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Post by Anders Nielsen
Hello there.
Since last week we have experienced the same problem.
We cant compile code that uses
Microsoft.Dynamics.Framework.Workflow.Portal and
Microsoft.Dynamics.Framework.Workflow.BusinessConnector
The problem seems to have surfaced out of nowhere, since we didnt have the
problem a week ago.
I have tried reinstalling the Business connector on the AOS server but it
didnt help.
Does anybody have any ideas of what could be the problem ?

[Anders Nielsen]

Post by Bill Thompson
Hello,
Remember that the compile is CLIENT based, so the client where the compile
is being done is where the .NET BC should be installed. Compiles are always
done at the client tier, so the business connector needs to be installed on
the same tier to get this to work.

Im not sure I understand this, are you saying that some of the code in the
AOT only is supposed to compile on certain computers ?

I have tried setting up a test environment with AOS, client,
BusinessConnector and EnterprisePortal on the same box. A full compile gives
no errors in a client started here. But if I install the client on a desktop
and does a full compile i get the errors for instance classes
"InventDimASPWebControlAdapter" and "SysDevelopmentProxy".

This supports that the compile gives errors on some computers.

Could you please elaborate on this subject I am a bit confused.

Thanks
-Anders Nielsen

[Luegisdorf]

Hi Anders

All elements in AOT are compiled always on the Client Tier. In your case,
your Desktop Client is missing some DLL-Assemblies. Since this news group
thread has not bring on top what components exactly has to be installed to
ensure a Client can compile the whole Application without errors, I suggest
to compile with a Client which is installed on the machine where the AOS is
installed too (the same Situation like your test environment).

Or you can try to install more AX components and retry compilation, may be
you find out what the missing parts are. If so, please let us know!

Best regards
Patrick

Post by Anders Nielsen

Post by Bill Thompson
Hello,
Remember that the compile is CLIENT based, so the client where the compile
is being done is where the .NET BC should be installed. Compiles are always
done at the client tier, so the business connector needs to be installed on
the same tier to get this to work.

Im not sure I understand this, are you saying that some of the code in the
AOT only is supposed to compile on certain computers ?
I have tried setting up a test environment with AOS, client,
BusinessConnector and EnterprisePortal on the same box. A full compile gives
no errors in a client started here. But if I install the client on a desktop
and does a full compile i get the errors for instance classes
"InventDimASPWebControlAdapter" and "SysDevelopmentProxy".
This supports that the compile gives errors on some computers.
Could you please elaborate on this subject I am a bit confused.
Thanks
-Anders Nielsen

[i***@gmail.com]

Post by Luegisdorf
Hi Anders
All elements in AOT are compiled always on the Client Tier. In your case,
your Desktop Client is missing some DLL-Assemblies. Since this news group
thread has not bring on top what components exactly has to be installed to
ensure a Client can compile the whole Application without errors, I suggest
to compile with a Client which is installed on the machine where the AOS is
installed too (the same Situation like your test environment).
Or you can try to install more AX components and retry compilation, may be
you find out what the missing parts are. If so, please let us know!
Best regards
Patrick

Post by Anders Nielsen

Post by Bill Thompson
Hello,
Remember that the compile is CLIENT based, so the client where the compile
is being done is where the .NET BC should be installed. Compiles are always
done at the client tier, so the business connector needs to be installed on
the same tier to get this to work.

Im not sure I understand this, are you saying that some of the code in the
AOT only is supposed to compile on certain computers ?
I have tried setting up a test environment with AOS, client,
BusinessConnector and EnterprisePortal on the same box. A full compile gives
no errors in a client started here. But if I install the client on a desktop
and does a full compile i get the errors for instance classes
"InventDimASPWebControlAdapter" and "SysDevelopmentProxy".
This supports that the compile gives errors on some computers.
Could you please elaborate on this subject I am a bit confused.
Thanks
-Anders Nielsen

Hi Anders,

in .Net business connector where you have installed please compile all class if found error open class and do cross re fence "InventDimASPWebControlAdapter" and "SysDevelopmentProxy". error will go after going .

[Luegisdorf]

In a funny way, I can compile the whole application while my collegue has
errors in SysReportLibraryExport.

I haven't figured out what's difference between his client installation and
mine. We both have installed BC and running the client with RU3. I guess I
had once installed some AX Server components (may be
Reporting-Services-Components, or an even a AOS itself), but I cannot
remember exactly.

But it looks like the class describben above ist the only element which
makes some troubles at last.

Post by Anders Nielsen
Hello there.
Since last week we have experienced the same problem.
We cant compile code that uses
Microsoft.Dynamics.Framework.Workflow.Portal and
Microsoft.Dynamics.Framework.Workflow.BusinessConnector
The problem seems to have surfaced out of nowhere, since we didnt have the
problem a week ago.
I have tried reinstalling the Business connector on the AOS server but it
didnt help.
Does anybody have any ideas of what could be the problem ?