When I developed my first module, 80% of my time was spent on configuration of the environment, and a little, a very little on producing the actual code. This weekend once more, all time was spent on figuring out the right configuration. This time, I set myself some higher goal, and I am not yet sure that I can achieve what I am trying.

After having bought the sources from Mauricio, I have set myself to provide some serious maintenance to dslocalizator. I have 3 issues to go after and the source needs some adaptation for DNN 5. I suspect some of my issues will vanish if I can do that conversion successfully.

I have tried different scenarios for my project. I have one setup that is the exact copy of my server with the same database and the same path to the file system as on the server. Ideal for testing what upgrades would do to my live site. I switch from live to development by commenting in or out a line in etc\hosts. I succeeded in compiling the extension, in attaching to a browser process and executing breakpoints. Of the 102 original warnings about obsolete or depreciated functions, I have now 92 left through some obvious corrections.

This has shown me that I will have to do a lot of research to get some of the issues ironed out, so I went to look for the ideal environment. I was hoping that by installing the sources on a clean DNN installation from the source code, I might be able to step into the underlying source code and learn the proper way to format my request. I still have to figure out how to attach those help files to the application, I would not want to miss out on those.

I've setup a dnn instance in localhost/website. I succeeded in compiling the solution in VS  I was not yet able to install the site, there is still something wrong with the connection to the database. I will have to go a few more times through that part of the setup procedure to bring it to a good end.

My hope is that by installing dslocalizator on top of a source code generated website in debug mode, I will be able to step into the core procedures and see what happens from a debug session of the extension.

My agreement with Mauricio is that the solution will be freely downloadable from tiendaboliviana while the sources will be his, to sell on snowcovered if he choses to do so.

I have some nice improvements in my head I would like to work on. 

Like so much on DNN, it fails in its UI. I believe you must again think of the different roles in the process of building a website and bring the admin functions back to the pages on which they are applied. Sebastian, I might ask you for one link on your control panel for dslocalizator, because the control panel is where page localizations have to happen,  Module localizations should be included in the action menus.

One of the first improvements would be to move the host section of his dslocalizator module to a different module for inclusion in the host section instead of admin section.

I also believe the solution would grow in value if it provided an easy migration solution to (and maybe also from?) the core ML solution and make co-existence possible.

Back at work, another setup of the dnn source code. Where do we start? Yes, edit the sln file.

---

____________________________________
The one-eyed in the land of the blind.

Marc,

In regards to installing source package of DotNetNuke, have you seem my recent Wiki addition:

http://www.dotnetnuke.com/Resources/W...

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

I succeeded the installation. I solved the puzzle, I still wonder which option is the correct one

• It is so by design (nah, cannot)
• It is a glitch in this version of the sources
• It is the result of my own ignorance

I've been setting up the source installation tens of times. Since it failed each time (except once), I've tried all kinds of variations on the process, like pre=compiling the libraries from their own vbproj file (as separate application) - which created a new solution file (this cannot be the correct way)

I did notice 2 things: When I checked the Library's Reference property pages inside the dnn solution, all references were there, pointing to the correct dll files. But after opening the library's vbproject, references to the support projects (CountryListBox and DotNetNuke.Syndication) were missing and the source file displayed errors. The library compiled correctly when the references were re-added.

As a result, less errors in the main application. Further research revealed that the reference to the DotNetNuke.dll was missing in the references for DotNetNuke.Web.

But it could not be the purpose of the installation to create solution files for those 2 components - and yet, there remained 9 stubborn errors that did not want to go away. The solution file part got solved when I discovered that I could save the property pages without recompiling and thus saving a slm file.

The 9 last errors were solved by checking the property pages of the syndication component and the taxonomy module.

I will do this a couple of times over again to come figure out the best strategy (first edit the property pages of syndication, then build countrylistbox and syndication. Then edit the property pages of the library etc etc)

Maybe this is a complicated work-around for something I missed?

---

____________________________________
The one-eyed in the land of the blind.