I have a bunch of programs set up as prerequisites in the VS bootstrapper. Recently, everytime I build on my machine and try to run setup.exe, I get an error ".....msi has either changed or been corrupted since the package was originally published". I know this isn't a problem with the setup or the msi files because I done the exact same thing on another development machine and copied the output to my machine and it's worked. I figure it must be something within the visual studio - bootstrapper connection. Anybody have any ideas?
Have you tried checking the log file ActivityLog.xml. It's under AppData\Roaming\Microsoft\VisualStudio\10.0
You need to run Visual Studio this way "Devenv /log"
Related
Im getting below error when im going to rebuild my setup project in visual studio 2015.Please advice to resolve this:
The message means that the install of Visual Studio 2010 Shell (Integrated) is broken, so Windows is attempting to repair it. Also, it looks like it was installed from the internet, which resulted in the setup being performed from a temp folder that has since been deleted. It is always better to download the setup (such as the MSI file) and save it somewhere. It is also possible that the C:\Windows\installer folder has been damaged or has had files deleted because normally the repair would be performed from there, which might have been happening for a long time but you wouldn't have noticed until the cached MSI file was removed from /windows/installer.
The fix is to get hold of the exact same MSI file that was used to install VS 2010 Shell MSI file and save it somewhere, and browse to it when this happens again.
The cause might be a conflict between VS 2010 and VS 2015, or some removed or changed shared files. The application event log will have an MsiInstaller entry that says what is missing.
We are in the process of upgrading our TFS 2013 server to TFS 2015. In that regard I have run into an issue when trying to perform an application build on a build agent with the new version, using our XAML template build script (which was created in TFS 2013).
Most of our solutions use the above-mentioned template when we build them. The solutions (sadly, still) use setup projects (.vdproj) to generate an MSI package for the application. To build the setup project, and produce an MSI, for a given application; we call the devenv.exe (in our case, it points to Visual Studio 2013) in our template build script:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe /Build "Release|Any CPU" "d:\<path_to_solution>\solution.sln" /Out c:\temp\out.log
However, on our new build agent no MSI is produced, and calling devenv.exe yields neither any output, nor any error messages. If I try to call devenv.com, however, it starts building, but still no MSI is being produced.
When things start to build using devenv.com It seems like it is completely disregarding the setup project (I have checked the build configurations, and the setup project is checked for build on the "Release|Any CPU" configuration).
I have looked at build logs, build process activity logs, and I have also tried to perform the steps manually on the build agent, but I haven't been able to find anything that could point me in the direction as to what might be causing the issue.
Does anyone have an idea what could be the reason for this? Could it be an issue with TFS Build 2015? The only difference between the old setup, and the new - as far as I can tell - is the following:
VS 2013 was installed on C: rather than D: on the new build agent, i.e. the path to devenv would be different, but that should not matter as long as the build script is looking in the right place, and finds it...
We use a different drop location than what we used for the old setup
Appreciate any help and suggestions I can get.
Problem solved, and everything is now building successfully. I did not do a good enough job of looking at the diff between the setup we had on the build agent we used for TFS Build 2013 vs. the one we set up for TFS Build 2015.
Firstly, to be able to build setup projects in VS 2013, one needs to install the Visual Studio 2013 Installer Projects extension on the build agent.
However, there are some bugs with this extension that often causes building setup projects to yield the following error message: "An error occurred while validating. HRESULT = '8000000A'". This error can be fixed by modifying the registry, as described in this SO post.
Building the setup projects using devenv.exe, however, still doesn't work. I have not been able to figure out why, yet.
Use the Vnext build in TFS 2015 to build .vdproj. You just need to add one additional build step i.e "command line" then call devenv.com to build.
Such that,
tool :
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.com
arguments :
HelloWorldTestInstaller\HelloWorldTestInstaller.vdproj /build release
This will help you.
I am creating an MSI package using Visual Studio and I have added in the SQL Express set up, it all works fine, except I would like to automatically open the SQL Express when the application has finished installed.
I did a bit of investigating and saw an option in Visual Studio in the properties window for the Setup named PostBuildEvent. Can I add a custom macro here to boot the SQL Express installer? If so, how would I go about doing this? And if not, does anyone have any suggestions on how I could make this work?
Any help would be GREATLY appreciated, thank you!
The post build event runs on your machine immediately after the build of the MSI file completes. It will run code immediately after Visual Studio is completes building the MSI. It will not run when an end-user installs the application.
To have the installer run code after the end-user installs the application use a Custom Action.
I know there are ways of installing SQL Express from the command line. This link gives an example of that. There is another example in here..
When I make this change in my application:
then when I deploy my application and install it on a computer that does not have that prerequisite I notice that the installer downloads that prerequisite:
If I cancel the installation and then launch the exe file that the installer downloaded then I will see:
If I do not cancel the installer, I believe that the installer then goes ahead and installs SQL Server Express with a technique similar to the one posted by the first two links link 1, link 2.
Where does Visual Studio stores the parameters that are being passed to the exe that it downloads in order to create a silent install? will it be possible to modify those parameters that are being passed to the exe? also I know which file (prerequisites) did visual studio (installer) downloads because I found it on the computer when installing my application but how can I tell from what link does visual studio downloads the prerequisites? I know it depends on the OS version and architecture of the operating system where the application is being installed.
Anyways I am just curious about the last paragraph. In short, I just want to modify the parameters that are being passed to the prerequisites of SQL Server Express 2008. Those parameters should be somewhere in the application that I deployed. Or maybe they get downloaded from Microsoft.
On a 64-bit machine the SQL Server Express bootstrapper is typically located in the following folder:
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\SqlExpress2008\en
Look inside the package.xml file for the command line parameters for the installer.
I have the following error on the build server for code that compiles and passes tests fine locally.
(150): The imported project
"C:\Program
Files\MSBuild\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets"
was not found. Confirm that the path
in the declaration is
correct, and that the file exists on
disk.
I've added the WebApplications folder from my local machine to the appropriate path on the build server but I'm still getting the same error on build.
I believe the recommended approach with TFS2008 was to install VS2008 in it's entirety on the build server. Is this still the case with TFS2010 and VS2010 accordingly? a.k.a Sledgehammer to crack a nut.
Pretty much, especially if you plan on using other features like MSTest. You can try just adding the targets file but you'll probably still have some missing dependencies. You could go through the whole process of fixing the dependencies as you go along but it's probably easier just to install VS 2010 and be done with it.
This blog post seems to describe a way to do what you want without having to install additional software on the build server, if all you need is the .net compilers. It does not cover C++ compiler setup.
I discovered that if you're going to do just "standard" (i realize that's open to interpretation) web apps and non-web apps (e.g. services), you can get away with installing just Visual Studio 2010 Shell, plus Visual Studio 2010 SP1 on the build server. That will get you the missing .targets files.
Since a full VS install is required for advanced features, does anyone know if the build-server-install license cost is waived?