I made a small change to the sbSiteUser.cs to shell a batch script to add a new user to my VSFTP site on a separate linux server using plink and adduer.sh within the .bat.  The code would only run when someone registers a new user id.

I've tested and debugged the small additional code using the latest download from TortoiseHg.  Everything works fine in VS2010, but as SOON as I copy the .dll into the bin directory on the web site, 2.3.9.3, the mojo error page is displayed instead of the normal home page.

Do I have to redeploy the entire set of projects just to update a single .dll onto the latest stable distribution, (.zip)?  Or is there somewhere I can find what the issue is?  Should I also update the log4net.dll? (I noticed that there was a problem with the version being out of sync in the refrence right off the bat that needed to be corrected.... 12.10 vs. 12.11 I believe)

Thanks,

Carl

And, just recompiling and replacing the log4net.dll and starting the http://mojohomepage.com/setup/default.aspx gives the same error as I had before:

We're sorry but a server error has occurred while trying to process your request.

The error has been logged and will be reviewed by our staff as soon as possible. It is possible that the error was just a momentary hiccup and you may wish to use the back button and try again or go back to the home page.

Thanks Joe, It would be a very small project indeed.  I'll check out the link on how to do that and still use all of the user information typed into the registration page as well as having it envoked using the Create Account button.  The main point is I needed the verified username and password and for this information to be provided just after the account was created in the SQL database.  I could run my own query of the table outside, but prefer to have this code run just AFTER the user id and password are registered in the database.

Here are the 7 lines of code that gets run in the AddUser method just before return newID; within the DBSiteUser class defined in the dbSiteUser.cs file.

System.Diagnostics.Process proc = new System.Diagnostics.Process();

proc.EnableRaisingEvents = false;

proc.StartInfo.FileName = "batch_path_and_batch_file_name";

proc.StartInfo.Arguments = loginName +" " + password;  //These are the two variables needed from the code above

proc.StartInfo.CreateNoWindow =true;

proc.StartInfo.UseShellExecute = false;

proc.Start();