All geek questions in one place

Problems setting up Windows Setup. Convert from VS.NET from 2008 to 2010.

I am trying to convert a solution from VS.NET 2008 in 2010. The solution includes a Windows service project and an installation project that installs a Windows service. I am having trouble compiling an installation project. I tried to start this from scratch several times, following the tutorial here in the section under the heading To create an installation project for your service .

When I just follow these steps and build the project, I get this error:

Unable to build custom action named 'Primary output from <name> (Release x86)', InstallerClass property is only valid for assemblies.

(where is the name of my windows service project). Finding this error calls this page on MSDN, which tells me to set InstallerClass to False . I do this for each of 4 user actions. After making changes and creating, I get the following error:

 Unable to build custom action named 'Primary output from <name> (Release x86)' from project output group 'Primary output' because the project output group does not have a key file.

Googling for this, I only get hit . Do not even click on the link, the full text: "Delete the user action and replace it with a special action that points to the project output group in which there is a key file."

What does it mean? Can someone help me figure out what I'm doing wrong here?

+1
source share
3 answers

It seems like the problem was that I set InstallerClass to False . Apparently, I did not create a Windows service for the x86 target. I got a hint for this discussion. I changed all projects to the target platform and left InstallerClass to True for each of the user actions in the installation file and now builds.

+3
source

This is kind of old, but just ran into this error: Migrating vs2008 to vs2010, the installation project did not give an error in one specific configuration, but did it in 2 other configurations that included the installation project. It was discovered that at the initial creation, someone added the primary output from a specific configuration (Not "(Active)"). Therefore, when another configuration was configured, the installation will throw this error. (This problem probably arose before switching to vs2010.)
To fix:

  • Copy the names of custom actions and CustomActionData strings (just the text is easily recreated)
  • Delete custom actions
  • Delete primary output and content files (this was a web setup project)
  • Add back to primary and content by selecting (active) configuration
  • Add custom actions

Now he builds everything without errors.

+3
source

Restore the project, the installer class class individually, and then rebuild the installer project.

-1
source

Source: https://habr.com/ru/post/1385549/

More articles:


All Articles