Dave,
>I did make the change to the mmBaseForm, but had a hard time getting the updated project to be refernced by my project. Do you have to run SN.EXE to get to work? I did so and finally got it working on my system, but now how to get the change to the other developers? I tried including the updated project in SourceSafe and have the other guys include the project from SS, but that did not work for some reason.
Yes, you do need to run SN.EXE -- check out the MM .NET Dev Guide topic "Recompiling MM .NET Assemblies" for details.
>Now, when I build my solution, I get the following error which I cannot get passed. Please advise.
>The command "Copy "C:\Program Files\Mere Mortals .NET Framework 2005\Mere Mortals Framework Windows Forms\bin\Debug\Mere Mortals Framework Windows Forms 2005.*" "C:\Program Files\Mere Mortals .NET Framework 2005\Mere Mortals Framework Windows Forms\"
>"C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\..\..\SDK\v2.0\bin\GACUTIL" -I "C:\Program Files\Mere Mortals .NET Framework 2005\Mere Mortals Framework Windows Forms\Mere Mortals Framework Windows Forms 2005.dll" /f" exited with code 1.
These are Visual Studio Post-Build events that copy the assembly to a different folder and then automatically registers the new assembly into the GAC. For details, check out the MM .NET Dev Guide topic "How can VS automatically add assemblies to the GAC?". You may want to run these commands from a Visual Studio DOS prompt to see which one is giving you grief.
Best Regards,
Kevin McNeish
Eight-Time .NET MVP
VFP and iOS Author, Speaker & Trainer
Oak Leaf Enterprises, Inc.
Chief Architect, MM Framework
http://www.oakleafsd.com