.NET 4 SDK Does not install Bootstrapper directory - .net-4.0

I have a problem on our Jenkins CI server.
I've install Windows 7 .NET 4 SDK on it but for some reason it did not install the Bootstrapper directory.
In my local machine I have Program Files\Microsoft SDKs\Windows\V7.0a\Bootstrapper but on the server machine it have Windows\V7.1 but it does not have the Bootstrapper directory.
Any ideas?
Thank you,
Ido.

I've finally solve this problem by simply coping the files from my machines to the CI server.
It's not ideal but it works.

Related

How to Install Tomcat 6.0 without MSI installer

I want to Install Tomcat Apache 6.0 in Windows 7. When I download from the site in the zip format and extracted as folder.
Query:
How to install tomcat apache server from this folder, Since it doesn't have MSI installer.
You don't need to install and you can startup Tomcat by bin/startup.bat.

how install glimpse nuget package on IIS server

Package is installed on local machines with a reference to packages folder added in project. Now If I publish it on server, it is causing problem as glimpse is not installed on server. Please guide what is the best way to install it on server.
Glimpse just needs its DLL's to be in the bin folder on the server.
Some deployment techniques (like on Azure Websites) leverage NuGet package restore to download dependencies and build your site right on the server. With these techniques you don't have to do anything.
For simpler techniques, like xcopy or FTP of files, just make sure to include the DLL's - they are already being copied to the bin when you build your site.

change clickonce install path

I deployed a project via ClickOnce cause I like the update features, but after install on some systems its hard to find.
On windows Vista and Windows 7, you will find the ClickOnce cache here: c:\users\username\AppData\Local\Apps\2.0\obfuscatedfoldername\obfuscatedfoldername
On Windows XP, you will find it here: C:\Documents and Settings\username\LocalSettings\Apps\2.0\obfuscatedfoldername\obfuscatedfoldername
Is it possible to change the path of an application installed via ClickOnce? I've looked in the publish settings and don't see a way to change the default path. Am I missing something?
No, that's beyond the scope of a ClickOnce install.
Why don't you distribute your updates through the ClickOnce system?

Apache Server Install No .msi installer

I am trying to install apache server from this Link using the NetWare Binary: httpd_2.4.3-netware-bin.zip link to be precise, I was looking at the internet for a good guide Not using the .msi installer becouse there is no .msi installer at the folder i unzip after i downloaded the zip file from the link above, And becouse i want to learn how to install not using the .msi installer at all, So if anyone know a way to install the apache server not using the .msi installer i will be very thankful, Thank you all and have a nice day.
Since you are looking for a msi installer, you probably want the win32 version and not the NetWare one. Pick the appropriate one from here: http://ftp.download-by.net/apache//httpd/binaries/win32/
If you want to install without a msi, you still don't want a NetWare version if you are running Windows.
You can read more about the NetWare operating system here: http://en.wikipedia.org/wiki/NetWare
More easy install Xammp you have allinone solution for win 32/64 with php version 5.6.3 embed
with:
Backup and Restore MySQL Databases
Configure FTP Access
Configure Virtual Hosts
Configure Wildcard-Based Subdomains
Deploy an Application Using Git
Get Started Quickly with WordPress
Reset the MySQL Root Password
Send Mail with PHP
Troubleshoot Apache Startup Problems
Simple and cool isn't it ??

Deploying Winforms Application to Client Machines Application Failing on start

This is Edited from the OP. This is a VB .NET 4.0 WinForms application. There is a mysql datasource involved with this project. The target CPU is set to any. Problem: When running this application on any computer that has VS 2010 installed along with the mysql connector it runs flawlessly. When installing on a virgin system(ie. No developer environment installed) but that machine does have .net framework 4.0 installed and a mysql server without the connector installed the application falls immediately. So to fix the issue I install the mysql connector MSI. This immediately fixes the issue on the client system and it runs. The problems is that as you can see below from my Installer setup that the 2 needed DLL files for MYSQL are actually included in the installation package so should not need to be installed separately. So Why is it that using that installer from the images do I need to install the mysql connector? Any Ideas? Below is a screen shot of the References the program uses and from what I believe I do not need to deploy any of those DLL files with my application other than the 2 MYSQL DLL files. So why is this failing?? Below are images showing the project references as well as the Installer Files that are being installed in the applicaiton folder. As shown in the image the 2 mysql dll files are to be put in the application folder. There is also a screen shot showing each dll's properties for in application folder.
You answered your own question.
but that machine does have .net framework 4.0 installed and a mysql server without the connector installed the application falls immediately.
You don't need to install the connector msi package, but you do need to include the two DLL files in the application's directory. Anytime you have some dependency, you need to deploy it with your application.
Edit solution quoted from my comment:
From your update it sounds like you have a version mismatch on the
assemblies, and the references are set to Specific Version = True.
Check the version number of the assemblies on your developer machine
in the output directory, and check the version you are installing on
the client system. (You can just hover over the DLL to read the
version on the ToolTip). You can try to set Specific Version to false
by right clicking your reference and selecting properties, or simply
ensure you deploy the same version of assemblies. Your program is
looking for the versions its compiled against