XAF help topic "How to: Change Navigation Control Appearance " contains some 
interesting C# code! 

OK I could not spot the "documentation mistake" you mention but I have a problem related to this help topic. I created the controller as described in the help code but I have no idea how to hook it into the app. There is a similar example in Step4 of getting started (ParserController) but there we have a actionParse which I think we use in the model editor to hook into the rest of the app. My problem is the contructor of NavBarViewChangingController never gets called - how do you do that? Oh - and while we are at it, whats the documentation mistake?

I suppose that you have a wrong idea about how to create Controllers. Perform the steps described in the Step 4 - Create a Custom Controller topic (http://www.devexpress.com/Help/?document=xaf/customdocument2564.htm ) to create a Controller. You'll see that you don't have to "hook the Controller into the application". To learn more about Controllers, refer to the http://www.devexpress.com/?document=xaf/customdocument2621.htm topic.

 

A controller won't be created if it's not public or the module in which it's implemented is not referenced in the application project.

 

If your Controller doesn't work after all, show it to us and we'll try to help you.

Thanks Mary - I had already read those two articles to no avail. Turns out you had already answered my question in another thread:

http://community.devexpress.com/forums/thread/12976.aspx

The problem with the navbar example is that the windowcontroller has to be added to the win project and not the winmodule project since it has references to xtranavbar and xtrautils. i think the example should include that fact otherwise it can be quite frustrating to newbies that like outlook style navbars like myself.

 Thanks for your help.
 

 

Hello Vedat, 

The thread that you've mentioned refers to a previous XAF version (CTP2, to be exact). So, the information given there is out of date. Currently, five projects (not three projects, as earlier) are generated in a solution. The recommended strategy is the following:

Use the application module to implement UI independent features.

Use the Module.Win project to implement Windows Forms specific features.

Use the Module.Web project to implement ASP.NET Web specific features.

 

So, like any Windows Forms UI oriented Controller, the NavBarViewChangingController should be implemented in the Module.Win project. The fact is that references to the DevExpress.XtraNavBar, DexExpress.Utils and other assemblies must be automatically set in the Module.Win project. It's a XAF issue that will be fixed in the next release.