Hi Malkom,

I could not include a vendor branch in Mercurial without making the repository much larger and it is already very large. So we no longer have that since we moved from Novell Forge.

Very few of those dlls are modified versions and I have the source code for those few backed up here locally, most of those dlls are not modified and you can google to find the related source code.

If you have a question about a specific dll then maybe I can say more.

Best,

Joe

• You can get the code for Mono.Data.Sqlite from the mono project. I have it on my to do list to update it at some point when I get a chance.
• I can email you the code for RSS.NET if you like, but I will be removing that from mojoPortal soon, it is currently only used in the Forums RSS feed. In other places we use Argotic Framework (which I have also had to modify to fix over time) or just plain xmltextwriter to render RSS.
• I implemented the simplest solution that met my goals. Help files are text files and can be edited in the browser resource files cannot. Message templates are text files to make it easier to customize them if needed. Resource files are meant only for localization but not customization.

Best,

Joe

Hi Carl,

mojoPortal uses the Web Application project type in which all the C# code is compiled into dlls and source code is not deployed to production. See Getting the Code with Tortoise HG.

Also note that the only smtp settings needed are those in the <appSettings section, it does not use the <system.net.mail section of Web.config

Hope that helps,

Joe

Hi Carl,

If there exists a user.config file in the root, any <appSettings from there will trump what is in Web.config

In fact the user.config file is where you should put custom settings that override the default <appSettings from Web.config

That way when you upgrade it is easier to upgrade to the new Web.config file since most if not all of your custom settings can be in user.config.

Note that after you have created a custom machine key you do need to maintain that in Web.config during upgrades because it should not change. Only the <appSettings section can be used in user.config, nothing else from Web.config can be put there, but it does make it less work to maintain most custom settings by putting them in user.config

I suspect that these settings do exist in user.config and it has localhost so the settings in Web.config are not having any effect. The solution is to update the setting in user.config

Hope that helps,

Joe

Hey Carl,

Thanks for the beer! Much appreciated.

Noticed from your beer order that we are practically neighbors, I'm in Charlotte.

Cheers,

Joe