I am building a setup in VS2012 - installshield.
I have to upgrade the version of my application and create a new installer.
I changed the product version and update the version of my application and setup too. (they where 2.0.2.0 now are 2.0.3.0).
The installation works correctly and the updates seem to work (2.0.2.0 does not exist anymore and 2.0.3.0 is installed) but it happens that myapplication.exe after the msi is launched is erased!
Only if I run the msi another time in repair mode the .exe is added.
I would like that the installation will keep the exe without this boring second step.
I answer my own question.
I naively just forgot to set the compile mode from debug to release; so the compilation worked but I had this side effect.
I am trying to install RXX(VSIX Isntaller) in windows 10 & VS 2012. But it gives error as below
The extension 'Razor(cshtml) pre-processor requires a version of the .NET framework that is not installed.
It is working properly in Win 7 ( .NET Framework 4.5 ). When I tried to install .NET framework 4.5 in Win 10, its no allowing to do the same.
Can anyone suggest anything for this?
Thanks
I expect the VSIX manifest to reference a specific .NET framework version and doesn't specify a range. Since .NET 4.6 replaces 4.5 it may cause these type of issues.
Extract the VSIX using your favorite extraction tool (it's a zip file), edit the manifest file by removing or updating the dependencies specified and zip it back up.
The only way to install the extension was executing the VSIXInstaller.exe as administrator and passing the VSIX file as parameters. To do that, follow this procedure:
Open a CMD window as Administrator
Go to Common, IDE folder of the VS 2015 installation. In my case:
CD C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE
Execute the installer passing the VSIX file as parameter. In my case:
VSIXInstaller.exe c:\AppBuilder.vsix
Finally, the installer will start the installation!
I hope it helps you
Source
In our product we had to disable the "windows installer" service (security-wise).
In Windows 2012 it is not possible to do so with sc.exe, so we had to change the value of the service in the registry
(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msiserver ---> start = 4)
Now, as an upgrade process of our product, we need to install
"VC++ 2013 redist"
Is it possible to install this package without using windows installer?
Or, is it possible to start a "disabled" windows installer service without restarting the machine?
Instead of installing the VC++2013 runtime using Windows Installer you can put the needed files in the directory of your executable:
you can directly install redistributable Visual C++ DLLs in the application local folder, which is the folder that contains the executable application file.
(from Redistributing Visual C++ Files)
I want to make a fresh XPages Extension Library v15 installation. So I want to remove former v14 version completely. But I have not found any description how to make an uninstallation.
Is that not intended ?
Open File / Application / Application Management... and uninstall ExtLib components:
If you installed your ExtLib with an updatesite.nsf then you can uninstall ExtLib with "Disable Features" there alternatively.
Using Visual Studio 2012 Premium on Win 7 x64, I make a new project (an MVC 4 project). When right-clicking on the project, I see no 'Manage NuGet Packages' option. A packages folder exists in the solution directory, as does a package.config file in the project directory. When going to Tools, there is no Manage NuGet Packages option, either. When going to Tools->Extensions and Updates..., the NuGet Package Manager is installed and up to date.
Any idea why my project is unable to manage the NuGet packages for itself?
Here's a screenshot of the menu:
I had a similar problem. The problem was next:
I've installed NuGet Packager instead of NuGet Package Manager (from Extensions and Updates). Once I've installed the last one, it appeared in the context menu. Maybe you faced the same problem.
I had to uninstall the Nuget Package Manager from Extensions and Updates, and then reinstall it. After restarting Visual Studio, the missing menu entries appeared.
My solution came in the form of wiping out all traces of the NuGet Package Manager, including all registry files. Because the registry files have weird names, searching for things like NuGet.Core as well as just about anything in the Program Files\Microsoft Visual Studio\11.0\Common7\IDE\Extensions folder. After clearing those out, restarting the computer, reinstalling NuGet, and then restarting again seemed to clear up the issue.
First of all there are something's you should check
Make sure you are in debug mode
Make sure your not running the debugger
The 'NuGet Package Manager' is installed and not the 'NuGet
Packager'
Your project was created using the VS IDE - to check this, you can
simply create a new solution in VS and see that you are still
missing the 'Manage NuGet Packages' option in the menu.
Now if this issue still appears you can try taking the following steps:
Clean out your Extensions folder.
Extensions folder can be found
under the VS folder \Common7\IDE\Extensions. i.e. if vs2013 in 64
bit, then C:\Program Files (x86)\Microsoft Visual Studio
12.0\Common7\IDE\Extensions
Uninstall the NuGet Package Manager from Extensions and Updates
Restart VS
Install the NuGet Package Manager from Extensions and Updates
Hope this was helpful
Because of reasons, It seems that Nuget Package Manager was not installed on my fresh Visual Studio Professionnal 2013 edition.
Installing it fixed the problem.
You can also check your Extensions folder in [if vs2013 in 64 bit, then C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions]
Each extension has folder in here with manifest file extension.manifest, check these xml files - node "Name" and if found duplicate, remove duplicate folders, restart Visual Studio.
If there is same extension in different folder, VS is confused and will not load it...
In my case the project was running. When stopped, the menu items appeared.