Hi Kevin,
The MergeModuleProperties is a category shown on the Properties window. Here is a link from Crystal Decisions that discusses the files needed to deploy apps that use CR for .NET:
http://support.crystaldecisions.com/communityCS/TechnicalPapers/crnet_deployment.pdfIf you look on page 4 of the pdf file, you will see a picture of the properties sheet with the MergeModuleProperties category displayed.
>This is a question for Cathi, as she was able to help out someone from Thread 670821 [but if anyone else has the answer, feel free to respond].
>
>I was having difficulty deploying Crystal .NET on a user's machine, and specifically was getting 'Cannot find KeyCodeV2.DLL...'
>
>I did a search and found thread 670821. It looked like it would resolve it...except that when I pull in the merge modules in my setup project, I don't see a section in the property window for "MergeModuleProperties". It doesn't appear in the property sheet for REGWIZ.MSM, nor does it appear for any of the other five merge modules [database_access, database_access_enu, managed, regwiz, VC_CRT, nor VC_STL]. So I can't see where I can paste in the Crystal License Key.
>
>The only properties I can see for REGWIZ.MSM are Condition, Exclude, Folder, Hidden, PackageAs, Permanent, ReadOnly, Register, SharedLegacyFile, SourcePath, System, TargetName, Transitive, and Vital.
>
>[I do have a fully registered version of Visual Studio.NET and my copy of CR.NET is registered...I have a registration number and product code, etc. I wasn't the one who installed VS.NET on my computer, it was someone in our IT group,so I don't know if there could have been an installation step that was missed months ago.]
>
>Thanks,
>Kevin
-----------------------------------------
Cathi Gero, CPA
Prenia Software & Consulting Services
Microsoft C# / .NET MVP
Mere Mortals for .NET MVP
cgero@prenia.comwww.prenia.comWeblog: blogs.prenia.com/cathi