I've forked the repository so I can make a small mod to the FAQ template, which actually requires a code change of some javascript injected by the Scriptloader.

I didn't see a tag for 2.3.7.6, so I may not be at the right revision.  I also don't know how assembly versioning works for the most part.

When I made the necessary mod and built the module, then dropped mojoportal.Web.controls.dll into an existing install of 2.3.7.6, I got an error when trying to load any page.  The error says there's a mismatch in the dll version in the assembly manifest file.  I didn't get the full text of the actual error.

Any pointers on what I need to do to match the existing version?

Also, will the 2.3.7.6 source get tagged?

Thanks,

Ted

Joe,

Im trying to get an easier process for custom control development working, using a similar development setup as custom controls for Umbraco.

The goal is to be able to start from File>New Website, reference the Mojoportal.*.dlls, modify the web.config and be able to build and debug (using attach to process) your custom control without having to compile the whole MP source each time.

I keep running into DLL reference problems with the last 2 builds of the Deployment Files packages I've tried (2.3.7.0 and 2.3.7.6). In both cases, the build number (version) of the deployed version of mojoportal.business.dll is lower than the build number referenced by mojoportal.web.dll. This probably works for a deployed site, but breaks any builds when referencing the DLL's in Visual Studio.

Visual Studio Error Message:

"The project currently contains references to more than one version of mojoPortal.Business, a direct reference to version 1.0.4378.27229 and an indirect reference (through 'mojoPortal.Web.SiteUtils.GetCurrentSiteUser') to version 1.0.4381.23460. Change the direct reference to use version 1.0.4381.23460 (or higher) of mojoPortal.Business."

To fix this, I have had to do what Im trying to avoid, ie download the full source, compile the updated business.dll and copy that over the one in the deploy package, and reference the updated one.

Is there a setting somewhere that I'm missing that will fix this behaviour, is there something you can set when building the deploy files, or is the business.dll just being missed in your post build event?

With the next release, can you package the final versions of the VS projects that are referenced by mojoportal.web?

Steve.