This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- error -6225 Resolving Project output when building from the command line
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 04, 2016
09:49 PM
error -6225 Resolving Project output when building from the command line
Using InstallShield Limited Edition with VS2015. The solution has two setup projects.
The setup projects build fine when Visual Studio is run in interactive mode.
But this is for a build server, so Visual Studio is run from the command line. The command line is 'devenv.com "mySolution.sln" /Rebuild Release'.
This gives error : "-6225: Resolving Visual Studio .NET project output... "
Nothing but the Primary Output is included in each setup.
The solution structure is quite regular:
MySolutionDir\mySolution.sln
MySolutionDir\MyProject1\MyProject1.csproj
MySolutionDir\MyProject2\MyProject2.csproj
MySolutionDir\SetupProject1\SetupProject1.isproj
MySolutionDir\SetupProject2\SetupProject2.isproj
The build server needs to be able to build as well, please help.
The setup projects build fine when Visual Studio is run in interactive mode.
But this is for a build server, so Visual Studio is run from the command line. The command line is 'devenv.com "mySolution.sln" /Rebuild Release'.
This gives error : "-6225: Resolving Visual Studio .NET project output... "
Nothing but the Primary Output is included in each setup.
The solution structure is quite regular:
MySolutionDir\mySolution.sln
MySolutionDir\MyProject1\MyProject1.csproj
MySolutionDir\MyProject2\MyProject2.csproj
MySolutionDir\SetupProject1\SetupProject1.isproj
MySolutionDir\SetupProject2\SetupProject2.isproj
The build server needs to be able to build as well, please help.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 05, 2016
12:00 AM
Update, the build works using MSBuild -- from the command line. When run by a service (the build server), the license is not recognised (-7159: The product license has expired or has not yet been initialized).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 06, 2016
12:41 AM
Yet another update, the build works when being the build server user and running the build interactively, from the command line, even if the build server user does not have administrative rights.
But when that same user runs the build as a service, like a build server, in the background, the license exception occurs.
When then that user gets administrative rights, the license problem goes away.
This is not ideal: The build server has to have administrative rights on the machine it runs on.
But when that same user runs the build as a service, like a build server, in the background, the license exception occurs.
When then that user gets administrative rights, the license problem goes away.
This is not ideal: The build server has to have administrative rights on the machine it runs on.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)