Microsoft KB Archive/835452

Knowledge Base

BUG: Merge modules do not appear in the Detected Dependencies folder of a Setup project for a smart device application

Article ID: 835452

Article Last Modified on 3/19/2007

---

APPLIES TO

• Microsoft Visual Studio .NET 2003 Professional Edition
• Microsoft Visual Studio .NET 2003 Enterprise Architect
• Microsoft Visual Studio .NET 2003 Enterprise Developer
• Microsoft Visual Studio .NET 2003 Academic Edition

---

SYMPTOMS

In Microsoft Visual Studio .NET 2003, when you create a Setup project for a smart device application, Microsoft .NET Compact Framework merge modules or any other merge modules that your application requires do not appear in the Detected Dependencies folder in Solution Explorer. Instead, the Detected Dependencies folder contains certain common .NET Compact Framework assemblies like System.Data.dll and System.dll.

CAUSE

The target device for a smart device application Setup project is either a Pocket PC device or a Microsoft Windows CE device. However, these devices do not support Microsoft Windows Installer. Therefore, the merge modules that your application requires do not work on these devices and Visual Studio .NET does not list these merge modules in the Detected Dependencies folder. Instead, Visual Studio .NET lists the .NET Compact Framework assemblies that your smart device application uses.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Steps to reproduce the behavior

1. Create a Smart Device Application project. To do this, follow these steps:
   1. Start Visual Studio .NET 2003.
   2. On the File menu, point to New, and then click New Project. The New Project dialog box appears.
   3. Under Project Types, click Visual Basic Projects, and under Templates, click Smart Device Application.
   4. In the Name box, type MyApp, and then click OK. The Smart Device Application Wizard - MyApp dialog box appears.
   5. Under What platform do you want to target?, click Windows CE.
   6. Under What project type do you want to create?, click Windows Application, and then click OK.
   7. On the Build menu, click Build MyApp.
2. Add a Setup project to your solution. To do this, follow these steps:
   1. In Solution Explorer, right-click the MyApp solution, point to Add, and then click New Project. The Add New Project dialog box appears.
   2. Under Project Types, click Setup and Deployment Projects.
   3. Under Templates, click Setup Wizard, and then click OK. The Setup Wizard (1 of 5) dialog box appears.
   4. Click Next.
   5. Under Do you want to create a setup program to install an application?, click Create a setup for a Windows application, and then click Next.
   6. Under Which project output groups do you want to include?, click to select the Primary output from MyApp check box, and then click Next.
   7. Click Next, and then click Finish. You notice the behavior that is described in the "Symptoms" section of this article.

REFERENCES

For more information, visit the following Microsoft Developer Network (MSDN) Web sites:

http://msdn2.microsoft.com/en-us/library/ms837860.aspx

http://msdn2.microsoft.com/en-us/library/aa369820.aspx

Keywords: kbvs2005swept kbvs2005doesnotapply kbdeployment kbsetup kbbug KB835452

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.