Hi Anette

In the mojoPortal source code project there is a mojoPortal.Features.Business project.  Look in there and you will find a folder called ContactForm.  In that folder is a file called ContactFormMessage.cs.  It is this forms class reference your project can't find.

I would copy this file to your clone features Components folder and rename it MyCloneFormMessage.cs or whatever you call your project and then change the reference name to it's ContactFormMessage class in your files on a line that looks like this...
Line 108 - ContactFormMessage contact = new ContactFormMessage();

That should lead you in the right direction for the first error.

Your clone project should have it's own App_GlobalResources folder with it's own MyCloneFormResources.resx file in it.  This file should be a copy of mojoPortal.Features.UI\App_GlobalResources\ContactFormResources.resx

If you rename the reference file and/or the reference names in it, then and all references to ContactFormResources (lots of them) should be changed to whatever you name your projects resource file. Also, your resource file must be targeted in your features setup folders config files.

That should lead you in the right direction for the second error error.

For the log4net error...

In the source code in the mojoPortal.Web project there is a dll called log4net.dll in the bin folder.  Create a reference to that dll in your feature.

Hope this helps.

Every developer will clone a project slightly different than the next based on the developers experience and the complexity of the changes being made to the cloned feature.  My advice to you probably differs from others but it has worked for me.  Database changes will definitely take your cloning to a much higher level of complexity.

Good luck and have fun

Rick Hubka

Hi Anette

Since you are new to mojo and C#, the easiest way to get you up and going quickly is to give you my complete working clone the ContactForm-feature.

Just unzip it and add this project file to your solution and you'll have a working copy.  I did the clone all in one project.  From there you can either use mine as an example to copy from or change the file names and do a big search and replace on the word "GarageWizard".

Here is the clone zip file on a mojoPortal Website I'm working on.  It's big 16 Meg file because the bin file has all the dlls the clone needs for mojo 2.3.6.7

Download Clone of ContactForm-feature here *** updated.

Good Luck

If anyone else wants it feel free to take it before it's gone.

BTW.  It's complete and compiles clean and install tested.

Rick Hubka

I can't be sure, but it looks like your mojoPortal Web solution can not find the dll's from your custom feature.

In Visual Studio, right click on your project file and click properties.
Then on the properties page click the "Build Events" tab.  In the "post-build event command line" you should have code similar to this (below) which will copy your files and dll's to your features folder in the mojoPortal Web project.  This folder must also be the same folder referenced in your setup config file.

xcopy /s /y "$(ProjectDir)bin\GarageWizard.UI.dll" "$(SolutionDir)Web\bin\"
xcopy /s /y "$(ProjectDir)GarageWizard\*.aspx" "$(SolutionDir)Web\GarageWizard\"
xcopy /s /y "$(ProjectDir)GarageWizard\*.ashx" "$(SolutionDir)Web\GarageWizard\"
xcopy /s /y "$(ProjectDir)GarageWizard\*.ascx" "$(SolutionDir)Web\GarageWizard\"
xcopy /s /y "$(ProjectDir)App_GlobalResources\*.resx" "$(SolutionDir)Web\App_GlobalResources\"
xcopy /s /y "$(TargetPath)" "$(SolutionDir)Web\bin\"
xcopy /s /y "$(ProjectDir)Setup\*" "$(SolutionDir)Web\Setup\"

This is covered in one of Joe's Developer videos.

I hope this helps???????
 

Hi Anette

I updated my Download Clone of ContactForm-feature file in my post above.  I tested it and it did not work.  I needed to fix a couple of words in the resource file and the setup config file.  I just tested it and it installs fine on a new page now as an exact clone.

Download it again and add this clone project to your main mojo solution.  Compile it so the post-build script does it's thing.  Then in your VS mojoPortal.Web project in the setup folder right click on Default.aspx and set it as the start page and run the solution.  As the script runs you will see a line called Garage Wizard.

Then in your website add a new page and add the Garage Wizard feature to it.  Then check it out.  It's a copy of the Contact form.

In your feature make sure feature name in the setup config file and the feature name in the resource file are correct.  That was my error and why it did not install correctly at first.

Now you have a working/tested clone project to compare.

When building a new mojoPortal feature module I have found out the hard way...  At first, don't build anything into it until it installs and works basically empty.  Take baby steps at first and just do a new feature that says "Hello world!" or in the case of a clone, don't add anything to it until it works as a simple clone first.  Don't code for hours and add 10 new things.  Instead, add 3 new things and run it every 20 minutes.  Same goes for adding database scripts.  Don't script and add 10 tables and 20 stored procedures at once.  In my scripts I have one script file for tables, one for stored procedures, one for functions, etc.  This is the best way to avoid compound/multi errors which are exponentially more difficult to find.

On your second and third feature then you can take bigger steps.

Good luck.