How we can disable repair / remove option in visual studio (2008) installer. I just want install & uninstall options only. Is it possible to hide that window from installer?
I have tried this with orca; but no yield.
Then I tried to set custom action condition, that too didn't work.
Still my installer shows the Repair/Remove dialog if it is already installed.
For Visual Studio Installer, I found just one way of doing it: create a custom action at the Install step. In that custom action write code to create the following registry values:
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID-THAT-CORRESPONDS-TO-YOUR-PRODUCTCODE}
Values:
NoRepair = dword:00000001
NoModify = dword:00000001
That's it. After inserting these values in the registry the "Repair" button disappears from the Add/Remove Programs screen. No custom action conditions required.
Note: for a 32-bit software running on the Win64 platform the registry path is:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\...
Related
I have install Windows 8.1 and after that I install Visual Studio Express 2013, which includes Update 2 RC.So when I run any application then it gives me the error
"File 'Windows.props' not found"
I don't know why it is happening. I search a lot about this error but can't find any solution.Please help me I have spend two days to find this solution.
Edit
Also there is not Emulator in the Device list.I think error is due to this once.I have download the 8.1 Emulator but cant find in the VS 2013 Emulator list.
Some basic checks you need to perform to get anywhere close to a resolution.
The Windows.props file is a build file that's used by MSBuild.exe when it builds a Windows Phone app. The normal install path is C:\Program Files (x86)\Windows Phone Kits\8.1\References\CommonConfiguration\Neutral\Windows.props. Use Windows Explorer to check if the file is present.
Then there is a line in the main .targets file that includes it. It tries to locate the file in the $(TargetPlatformWinMDLocation) directory. You can see the value of this macro by increasing the build verbosity. Tools + Options, Projects and Solutions, Build and Run. Change the "MSBuild project build output verbosity" setting to Detailed. Use Build + Rebuild on your project. Scroll back the Output window and locate the lines that resemble this:
1>TargetPlatformSdkMetadataLocation = C:\Program Files (x86)\Windows Phone Kits\8.1\References\CommonConfiguration\Neutral
1>TargetPlatformSdkPath = C:\Program Files (x86)\Windows Phone Kits\8.1\
1>TargetPlatformSdkRootOverride =
1>TargetPlatformVersion = 8.1
1>TargetPlatformWinMDLocation = C:\Program Files (x86)\Windows Phone Kits\8.1\References\CommonConfiguration\Neutral
Tell us if you see anything different.
This path is read from the registry. Startup Regedit.exe and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\WindowsPhone\v8.1\Install Path as well as HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\WindowsPhoneApp\v8.1\Install Path.
Verify that you see a value listed in those keys with the name "Install Path" and that it contains the value "C:\Program Files (x86)\Microsoft SDKs\WindowsPhoneApp\v8.1\".
Extracts from msdn discussion:
check for the existence of a SYSTEM level environment variable called windowsSDKDir and try removing it.
For this Follow these steps:
Press Windows Key + X and select System.
In the System dialog click on "Advanced system settings" then click "Environment Variables" on the advanced tab.
Then look for the environment variable I mentioned
try removing it
If this not works for you ,you must re-install, Windows Software Development Kit (SDK) for Windows 8.1 this must solve your problem.
The issue seems to be bound to the VS2013 Update4. I had no issues before, but after this, I needed to Install the Windows Software Development Kit for Windows 8.1 as Ludwo suggested.
I used function 'Repair' in control panel -> programs and functions -> Windows Software Development Kit for Windows 8.1 ->Change and solved this problem.
In my case I had to install Windows Software Development Kit (SDK) for Windows 8.1 (Not Windows Phone SDK!) to fix it. I have VS2013 update 4
have you checked for the existence of a SYSTEM level environment variable called windowsSDKDir? and try removing it?(make a note of its value first in case you need to re-instate it at some point). For some this appears to have been causing the error. It is not clear at this stage what creates this.
I'm trying to use extra modules with nodeJS and netbeans, however when I try to search for the modules on netbeans it seems to simply hangup forever.
Any idea what is going on? I already had the modules installed with npm install and command line, then I right click libraries on netbeans and the search hangs.
The installed modules are mysql & aws-sdk, and I'm using windows 7, 64 bits. Also on the Tools > Options > General > Proxy definitions, there is a "Test Connnection" button. If I click on it, I get a green check saying connection is OK.
Thanks
Check if the option which you have selected is 'No Proxy', for some reason for me it was pre-selected the option 'Use System Proxy Settings' and then when i updated it failed. Once i changed it to 'No Proxy', the update installation worked.
In Netbeans, Go into Tools-> Options -> Miscellaneous -> Node.js and see that you have configured the settings properly.
see this for more info, it is a plugin for NodeJS projects: http://timboudreau.com/blog/NetBeans_Tools_for_Node_js/read
I would like to install Umbraco 6.1.x, but my host suffers from this issue: http://issues.umbraco.org/issue/U4-1632
Basically, I can't install 6 due to an incompatibility with MySQL on Linux and Umbraco 6, but I read that I can upgrade from 4.x.x and then upgrade to 6. The question is, how do I do that? I.e. what files do I need to upload and edit such that the database remains, but all umbraco files are version 6?
Yes, according to the bug report you can install a Umbraco v4.11.x and then upgrade this to v6.1.x and this should work fine.
The downloads are all available here: http://our.umbraco.org/download
However, the easiest way to get Umbraco set up is to use NuGet in Visual Studio. So you could run the following line from the NuGet console:
Install-Package UmbracoCms -Version 4.11.10
You'll have to use the console for this because if you use the Package manager, it will just install the latest Umbraco package version.
Next, load your site in a browser and configure the database settings. Then upgrade using NuGet again. I find the easiest way to do this is to open the NuGet package manager in Visual Studio, select "Updates", find the Umbraco package and click "Update". This will automatically update all the files for you.
You will then need to load up the site again, at which point it will prompt you to upgrade, and you can just follow the steps in the wizard.
I'm following the instructions from here to build MonoDevelop on Mac OS X: Building MonoDevelop on OS X
I can build MonoDevelop just fine. I'd like to also build the MonoMac add in and use it.
The document says:
"To include addins from extras, manually copy their build directories
into the MonoDevelop.app directory, e.g.
cp -r ../../../extras/MonoDevelop.AspNet.Mvc/build/*
MonoDevelop.app/Contents/MacOS/lib/monodevelop/AddIns/MonoDevelop.AspNet.Mvc/"
However, I have no build directory under /extras/MonoDevelop.MonoMac.
I tried to follow this step to build extras:
"To include additional addins from extras in the build, instead of
using the Mac profile, use configure --select to select addins. This
will write the default profile. Next, replace the line in
profiles/default that begins with "main" with the one from
profiles/mac, then run configure again using the default profile."
But it does not give me the option to build the MonoMac extra.
Next, I try to compile the monodevelop.mdw. Again, I can build the main solution (MonoDevelop), but the extras fails with over 1000 errors.
Finally, I tried to take my existing monomac and macdev plugins and copy them into my master monodevelop.app bundle. But this breaks add solution/project dialog whenever I try to select a MonoMac project - it fails to load the Monodevelop.ide DLL.
Any advice on where I am going wrong would be appreciated.
I was not able to make this work following the directions on the MonoDevelop site. Even manually adding the extras/MonoDevelop.MonoMac extra to the profile did not work.
In the end, I build MonoDevelop from source, using the mac profile.
Then I got the latest MonoMac pieces, and build them from source. I used
make update
to install into my installed copy of MonoDevelop.
Then, I manually copied the following packages from my installed MonoDevelop to my newly compiled version from master:
MacPlatform.dll
MonoDevelop.iPhone
MonoDevelop.MacDev
MonoDevelop.MonoMac
Xamarin.Ide
Any everything now works :)
I'm creating installer using InstallShield 2010 (basic MSI) that is having two features.
First feature consists of:
main .NET application compiled as x86,
some native x86 third party dlls which are used by main application (x64 versions are unavailable).
Second feature contains single component which is an extension for MS Reporting Services compiled as AnyCPU.
During UI sequence I'm using InstallScript custom action to enumerate all available Reporting Services instances from both x86 and x64 registry trees.
The user is prompted to select on which instance he wants to deploy our extension.
Based on selected instance I'm quering registry for actual location of Reporting Services in file system which is usually something like "C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services" and storing this value in a MSI Property.
Then by using Set Directory action I'm setting destination directory of a component (our extension) to the value of that MSI Property.
Everything is installing perfectly fine unless you've trying to install it for x64 Reporting Services in that case extension files are installed to wrong location. Even thou MSI Property is set to correct path "C:\Program Files\MicroSoft..." (I've checked msi log) it looks like system is automatically redirecting to "Program Files (x86)".
Is there any possible solution to overcome this issue?
If you need to install to the 64-bit ProgramFiles folder, use a 64-bit MSI.
Finally solved this issue myself without creating 64bit MSI by using InstallScript custom actions.
First custom action to install:
Manually copy required files to desired location (InstallScript can access x64 Program Files)
Save this location in registry as a key component for this feature to use during uninstall
Second custom action to uninstall:
Read installed location from registry (do not use System Search to get this value due to it'll be auto translated by WindowsInstaller to "ProgramFiles (x86)")
Delete files
You can change the INSTALLDIR property to ProgramFile64 rather then ProgramFiles, this will help you to install on desired path, since you application is 32-bit so the path will be C:\ProgramFiles(x86)\Your Company Name\Your Product Name along with this have you made your components as 64-bit compatible?