My Inno Setup project is named correct in the IDE:
And the Visual & Installer project settings also match:
As you can see, my installer project is part of several, with Meeting Schedule Assistant being my primary project:
Even though I select my build project:
It compiles correct if I choose to build it. But, notice here:
The MeetSchedAssistInno project is not listed. As a result, when I try to run it I get the following error:
So I am getting confused. Why can't I trigger the setup file to start?
Note: I know I can set in the VI Properties to run the installer:
That way works (but it forces you to build first). But I should be able to simply start the existing installer like normal (or, it prompt me to build if it is out of date).
Launching Setup
There are spaces in your path to .exe file and that is the reason why the Visual Studio complains "The system cannot find the the path specified."
Did you rename the project or Solution? Please check twice whether the paths and real file names are good and without spaces.
Inno Setup project does not register itself among the Startup Project list as the Debugging is at this moment not supported. That is a reason why Visual Studio does not show it with GoogleAuthandSync and OutlookCallIFConsole projects.
You can right click the Inno Setup project and choose Set as StartUp Project to add this project temporarily into the list so the F5 will work
(Alternatively you can right click the project Debug -> Start new instance. Again: this is not real debugging, just launching the .exe).
Conditional Startup
Inno Setup supports:
Build
Build and Run
This can also be achieved with Visual and Installer by having two configurations. For example:
Then, set the Run installer option in the properties as required:
This way you can choose build, or build and run, by simply choosing the appropriate configuration.
Related
I'm attempting to setup an old project on a new computer using Rider with TFS. I'm already using TFS with the same repository on an old computer with Rider, however, I've noticed that on my new computer, TFS is no longer an option for version control. I have the plugin, I can go to version control under settings and view settings for TFS, but when I attempt to enable version control for the project, TFS is not an option. Similarly, I can't checkout from TFS.
Also, the settings screen for TFS is very different on my new computer's install, giving me only the options to delete and update configurations, but no way to add one (so I can't actually do anything). Any ideas about what's gone wrong here?
Have tested installing riderRS-171.4456.199.exe (Windows), the TFS Integration plugin has been bundled with Rider and enabled VCS-TFVC successfully. Seems you are using TFVC version control(check out), please follow below requirements:
You must have the TF command line tool installed to be able to
use TFVC features. The minimum version supported by the plugin is
14.0.3. To install the tool, download the latest "TEE-CLC-14...zip" file and extract it to a known location. After extracting the files,
you must accept the license agreement. To do so, open a Command
Prompt/Terminal window, navigate to the extracted directory, and run
tf eula. After reading the EULA, enter y enter code hereto accept
it. NOTE: If you forget to do this, the plugin may fail to load
with a RuntimeException.
For the tool to be detected by the plugin, you must set the location of the executable in the Settings/Preferences menu by following these instructions:
Go to RD Settings Version Control -TFVC
In the Path to tf executable text field, navigate to the location of
the tf executable.
Click Test to test that the executable has been found and is working
as expected.
Click Apply then OK to save and exit.
More details please refer this tutorial.
Also try to setup a new created project or select another project when you are using Rider with TFS. To narrow down if the issue is related to that special project.
When setting up Project Rider TFS config I am getting below error. But path seems to be valid.
I have tested installing riderRS-171.4456.199.exe (Windows), the TFS Integration plugin has been bundled with Rider and enabled VCS-TFVC successfully.
However, the command line tool is not using the tf.exe under VS.
You must have the TF command line tool installed to be able to
use TFVC features. The minimum version supported by the plugin is
14.0.3. To install the tool, download the latest "TEE-CLC-14...zip" file and extract it to a known location. After extracting the files,
you must accept the license agreement. To do so, open a Command
Prompt/Terminal window, navigate to the extracted directory, and run
tf eula. After reading the EULA, enter y enter code hereto accept
it. NOTE: If you forget to do this, the plugin may fail to load
with a RuntimeException.
For the tool to be detected by the plugin, you must set the location of the executable in the Settings/Preferences menu by following these instructions:
Go to RD Settings Version Control -TFVC
In the Path to tf executable text field, navigate to the location of
the tf executable.
Click Test to test that the executable has been found and is working
as expected.
Click Apply then OK to save and exit.
Besides, if you intend to use the tf tools from the command line, you may want to add this folder to your PATH environment variable as well.
More details please refer this tutorial.
I have a solution with multiple projects, from which one is a web application of that I want to create deployment package. When publishing with Visual Studio, it publishes and deploys without any problems.
Due to some requirements, however, I need to publish it with command line and this is where I am having problems. Publishing alone works fine even in command line, but when I try to deploy package created in command line I get this error:
A value for the 'setAclUser' setting must be specified when the
'setAcl' provider is used with a physical path.
My msbuild command looks like this:
msbuild Solution.sln /p:DeployOnBuild=true /p:PublishProfile=Debug
One differences I noticed are that when publishing solution, PackageTemp folder is created in different projects and so when deploying it is printing different paths to cmd. With VS publish they look something like
"Default Web Site/MySite/..."
but with command line publish they look like this
"C:\MySolution\Project(only a library project, not the one I want to
publish)\obj\Debug\Package\PackageTemp..."
Thanks for any help
Edit: Created .zip packages are almost the same, except for archive.xml which has some different values and I suspect this to be the problem, but unfortunately I can't make any sense of what does this file actually represent.
We had a working build for our solution, but when we added a new project, it stopped working. The build runs "successfully" and the log shows: Run MSBuild for Project -> Built [my solution] for target(s) publish (same for all projects), but it doesn't actually build anything.
The problem seems to be in the build configuration. My build process definition is set to build for my custom configuration (ForMSBuild | Any CPU), but something is wrong with the way TFB is interpreting that definition (I need that custom configuration because I copy some .dlls to a designated folder to include in a publish process in order to be available for a ClickOnce install).
At one point, only the new .dlls added to the solution weren't building (even though they were listed in the Configuration Manager with the Build check box checked). So I re-created my custom configuration, ensured that all my .dlls were checked to Build under (ForMSBuild | Any CPU), and now none build. I have opened the source on the build machine directly in Visual Studio (2012) and verified the settings for my custom configuration.
Edit the Build Definition, in the Process tab click the ellipsis next to Solutions To Build, go to the Configurations tab and ensure TFS Build is set to build the configuration you want it to:
It turns out that I actually had the main startup project not checked to build. Really stupid mistake, but I sure wish MSBuild hadn't spit out all those incorrect messages.
I've been reading and experimenting for days. I bought the latest "Inside the Microsoft Build Engine - Using MSBUild and Team Foundation Build". I've been trying to figure things out by looking at the build targets.
I was quickly able to get a package to be built on the build server, but I want to be able to specify the installation folder, so it doesn't go into wwwroot. I read that I would have to switch the project over from using cassini to the local IIS server. Went through all of that.
The args I'm passing to msbuild through the definition:
/p:DeployOnBuild=true /p:DeployTarget=Package /p:MSDeployPublishMethod=InProc /p:CreatePackageOnPublish=True /p:MsDeployServiceUrl=localhost
I've got SO MANY questions, but I'll start simply. If anyone can provide guidance I'd be super thankful.
If the named application doesn't exist on the build server (which it shouldn't!) the package creation fails. If I add a shell app named accordingly the package is built.
Even if I hack my way past #1 when I try to deploy using Web.deploy.cmd, it fails:
Error: Using a 64-bit source and a 32-bit destination with provider appHostConfig is not supported.
Note that the build server is 64-bit and THIS target server (development) is 32-bit. I have the build configuration building against "any cpu". Oh, and I'm invoking the deployment FROM the 32-bit machine, so there's only the 32-bit msdeploy.exe available.
In the appropriate BuildDefinition under "Process", expand the "Advanced" section and set the value of "MSBuild Arguments" to "/p:DeployOnBuild=True".
That will make your WebDeploy Package built according to your settings in the project properties.
I write 2 articles about how to create Web Package and auto deploy it to a Web Server, I think it maybe useful for you.
Auto Deploy your Website for QA with Team Build click here
How to run remote deploy with MS Deploy? click here