AX 2009 Enterprise Portal Error The type or namespace name “Portal” does not exist in namespace ‘Microsoft.Dynamics’

These days, I’m working on developing some new Enterprise Portal pages for GRN/ Packing slip Posting through EP. Suddenly i found a problem while building my EP Web control page.

“The type or namespace name ‘Portal’ does not exist in the namespace ‘Microsoft.Dynamics’ (are you missing an assembly reference?) ” on some of my custom developed pages.

Soultion : I had to Generate the proxies again and build the pages again.

How to Generate Proxies.

To generate the proxy open the form : Tools > Development Tools > Web development > Proxies > Generate)

In most cases the proxies directory will look like this: C:\inetpub\wwwroot\wss\VirtualDirectories\80\App_Code\Proxies

In the last you need to use the Generate Proxy option from Visual studio EP project to add the generated proxies to the project and Build the project to successfully build solution.

Debug Enterprise Portal Code in Microsoft Dynamics AX

1. Log in to the server that is running the AOS.
2. Open the Microsoft Dynamics AX Server Configuration utility. To openStart > Control Panel > Administrative Tools > Microsoft Dynamics AX 2009 Server Configuration.
3. Create a new configuration that allows debugging.
3.a. Click Manage then Create configuration. Give a name to the new configuration in the Create Configuration window then click OK.
3.b. On the Application Object Server tab, select Enable breakpoints to debug code X++ code running on this server. Click on Apply button.
4. Click on OK button to close the configuration window. You will get a message that indicates AOS is going to be restarted.
5. Actually debugger works on the server where IIS is running and Enterprise Portal is hosted. I used a single system and all the things are on the same system. If you are accessing a system remotely using Terminal Services then from the Start menu click Run. Type mstsc /console in theOpen text box and click OK This opens a console session in Terminal Services. Console session is required to debug Ax EP
6. The World Wide Web Publish Service should be enabled.6.a. Open the Services window for the system. To open it Start > Control Panel > Administrative Tools > Services.
6.b. Right-click the World Wide Web Publishing Service and click Properties.
6.c. Click the Log On tab.6.d. Select Allow service to interact with desktop as shown below.
6.e. Click on OK button to close the properties window.
7. Open the web.config file located in:\Inetpub\wwwroot\wss\VirtualDirectories\\, here the port number of the Enterprise Portal site. If you forgot the port then there is a way to check it out. Open Ax client then Administration main menu > Setup > Internet > Enterprise Portal > Web sites, here you can see the port. 8. Now do the following:
8.a. Find out the compilation element then set the debug attribute to true.8.b. Save the changes.
9. Reset IIS by typing the iisreset command at the command-line window or type iisreset in Start > Run > Open text box then click on OK button.
10. Open the Microsoft Dynamics AX Configuration utility. To open it Start > Control Panel > Administrative Tools > Microsoft Dynamics AX 2009 Configuration.
11. Set the Application Object Server Instance drop-down menu to Business Connector (non-interactive use only).
12. Create a new configuration to allow debugging.12.a. Click on Manage button then click Create configuration. In the Create Configuration window, name the new configuration then click OK button.12.b. On the Developer tab, select Enable user breakpoints to debug code in the Business Connector and Enable global breakpoints to debug code running in the Business Connector or client then click on Apply button.
13. Click on OK button to close the configuration window.
14. Open the Microsoft Dynamics AX client.
15. On the Tools menu, click Options to display the Options window.
16. On the Development tab, select When Breakpoint from the Debug mode list box, and then click Apply. This enables debugging mode on the client.
17. Close the Options window.
18. Open the Microsoft Dynamics AX client.
19. Now decide the element you want to debug. Lets say you want to debug a class method. Open the method in code editor and write breakpointswhere you want to set a breakpoint.
20. Open the Debugger window manually. To open debugger manually click on Tools > Development Tools > Debugger.
21. Now execute the web form where the method has been invoked. It should work. On my system it is working perfectly.

You will find this information on other blogs to but i am placeing here so if you come to my blog and dont go information less. Following links are good in explaining this too.

You would also needs a hotfix if you working on Windows 2008 with dyanamics ax 2009, for Ax 2012 you wont needs this.

Microsoft Dynamics AX 2012 Videos

Video1 – Developer Tools
– Stresses the importance of Models
– API’s
– Interoperability with .Net
– 3 yrs spent by Microsoft for the new Development Tools
Video 2 – Services and AIF
– Heavy investment in Services
– Mobile applications can plug in to the service model
– 90 webservices
– Simplified and Powerful Integration

Video 3 – Reporting
– Integration with Excel

Video 4 – Office Integration
– Collabration across Office, AX and Visual Studio
– Demo (Budget)

Video 5 – Usability
– End-User Simplicity
– Recruited people from the industry to test the usability scenarios
– Field Surveys
– Demo AR Customers/SO’s (Fact boxes)
– Consolidate Commands into Flexible Activity based Ribbons (Similar Look and feel as Excel, Word)
– Fast tabs
– “Go to Main Table” replaced by hyperlink lookups (cool feature)

Video 6 – Enterprise Portal
– Rich UI
– Travel Expense Demo
– Microsoft internal adoption (aka DogFooding)
– ISV’s interested to build on new add’ons for EP

Video 7 – Performance
20 x times faster than 2009
– Managed X++
– Leverages Virtualization
– Leverages AppFabric

Video 8 – Programmability
-Improvements in X++ Language
-Improvements in Language Performance
-Visual IDE and MorphX IDE
-Marrying C# and X++
-X++ managed language
-AOT in VS.Net

Video 9 – Security
-Improved Administration Experience for setting up Security
-Flexible Authentication (Leverages Claim Based Authentication from Sharepoint)

Video 10 – Simplicity
– Experiences for Developers, Administrators and End Users made simple
– For Developers – Goal to enrich .net and x++ developers experience
– Installation experience for Developer improved (Single Click Experience)
– Simplicity for System Administrators
– Good Feedback from Partner and Customer Channel

Video 11 – Processes and Workflow
-Graphical workflow Editor for Business Users and Application Developers
-Leverages Wofklow Foundation of .Net 4.0
-Flexible Work Item Queues
-60 Workflow Types out of the box

Video 12 – Organizational Model
-Model for External and Internal Reporting
-Policy Frameworks

%d bloggers like this: