Only thing I might suggest is make sure you have Page.EnableViewstate = true; in page load.

Not having any idea what your code is doing I have no way to diagnose it.

I suggest set some break points and step through the code and see at what point it loses the new values.

I don't find myself using DetailsView often but see no problem with using it and sure I could get it working if I needed it.

If you're using Mono it could be a Mono bug as well.

Best,

Joe

Please try encapsulating it in a UserControl and try that in a non mojoportal page so that you are comparing apples to apples.

It could be a difference between using it in a UserControl vs a Page rather than a mojoPortal issue other than that a mojoPortal module is going to be a UserControl.

For example be careful of using ajax page methods, they only work in a page not in a UserControl unless the page that the usercontrol is on has the method.

Hope it helps,

Joe

Possibly its a difference between a UserControl declared on a page or a UserControl added dynamically during the page load event of the page, try adding your UserControl to the page with code like

Control c = Page.LoadControl("~/pathtoyour.ascx";

pnlFoo.Controls.Add(c);

<asp:Panel id="pnlFoo" runat="server" would live on the page and you would load the control during page load.

Do some searching on the issues with events for dynamcially loaded controls in ASP.NET.

Hope it helps,

Joe

Hi Dale,

being able to step through the code with the debugger is something you should get comfortable with so I would look at this as an opportunity. Visual studio makes it very easy. Set break points in your page load, page init and other events, open Web.config file in VS (this is just to make sure it starts at the home page and doesn't try to launch your custom code first) then press the play button to launch the debugger. When the site comes up navigate to the page where your custom feature is and it should stop execution at the first breakpoint it encounters, then you can step through the code using the F11 key and inspect variables as the code executes to see where and when their values are changing.

Hope it helps,

Joe