Hello, the skinning area was the closest forum for what I'm experiencing.

We have an open source, simple Report Grid with which a user can select what controls he wants (drop down, text area, hyper link, etc.) and DNN programmatically creates the controls.  In other words, it's not laid out in ASP.Net pages (.ascx controls) but ends up being generated through the skinning engine (? do I have that right?) on the fly.

This won't render in 6.2.2 and I have the area nailed down that is failing.  What I need are the BASICS on how to write such modules in 6.2.2.  From what I see, the skinning technology has changed enough to where the assumptions made for this module just don't fly now.

I've used IE developer tools to zero in on where the control is working for both the working version (on a DNN 4.9.0 site) and on the new site.  I copied and pasted the script over to make 2 html files -- workingmodule.html and brokenmodule.html.  It is WAY too much code to paste in here.

From these it's easy to see the skin engine is creating the div wrapper for the module, in our case dnn_ctr536, for both controls but nothing else is happening.

I've utilized the existing Exception code in the VB to read how the controls are being programmatically made, etc.

This is WAY too complex however.  I know that what I need is how to write programatically driven apps for 6.2.2.  Or, someone who can look at the generated html, look at the vb code and say "you need to do this ..." etc.

Is there a way to upload the code?  The module is open source.  Or, if learning the new way to write these apps is relatively simple, how about enough links to just get me going to where I can figure out the rest?

Thanks!

Mike

Not yet, I was hoping with the skinning experience I do have that for a module generating 3 controls (1 drop down and 2 text boxes) that I could just get a hint or 2.

Then again, my skinning work was only done to support any code behind I was working with.  But I have the gist of it enough, I'm sure, where with a couple KB articles I could just get this module up and working.

It's the Dna2 Report Grid.  I can't find their website anymore, not a good sign.  Of course, we have the source code so this is just as good.

Has the module presentation layer coding changed so significantly where a couple KB articles won't do the trick?  If so, then some continuing education videos are needed.  Which would be the fastest track for getting this module up and working in 6.2.2?

I have DNN 4.x, 5.x skinning knowledge and have had to, as required, mod a skin here and there.  With my EXT JS coding experience I'm hoping for a short learning curve.

Thanks, Sebastian!

Best,

Mike

And you were correct.  I hit my post prior to yours as the answer by accident.  It is YOUR post that is the answer.

I didn't mention I had to use old style debugging since it wasn't obvious why I could not get VS 2008 to debug.

That error was .net 4.0 running in the IIS 7 app pool.  This was changed to .net 2.0 and not too surprisingly debugging worked.

This accomplished, it was an SQL error and now the module works perfectly.

For anyone still using VS 2008 / XP (hey, I'm looking at a new computer finally, OK? :)) watch out for that one.  It took a seasoned DNN developer and myself over an hour to chase that one down when we knew we were looking for something very not rocket science.

Thanks for all the input, though.