Wix (VS installer) - missing editors toolbar - visual-studio-2010

Wix 3.10 is installed on my PC. extension to visual studio 2015.
I created a setup project based on Wix (which works).
On a setup project, usually there are some icons, setup tools (file system, registry, UI, costume actions...), but they are currently missing.
You can see these icons on any tutorial for Wix (like: https://www.youtube.com/watch?v=CoFPyIbcqN8)
How can I add them?

You can see these icons on any tutorial for Wix
That's not correct. The icons described in the video are from Add-In Express's Designer for WiX Toolset. To add the icons, visit their website and install their product.

Related

What do I need to do to program an MFC/STL program in Visual Studio?

I've installed Visual Studio on my private PC, the version is "Microsoft Visual Studio Community 2019", version 16.1.6.
In order to prepare a job interview, I'd like to do some basic MFC/AFX programming, starting by the basic CMapStringToString example from the Microsoft website.
This, however, seems not to work, as I don't have access to the mentioned file afxcoll.h. Indeed: there is no file, called afx*.h on my PC.
Is this a limitation of my free downloaded Visual Studio installation, or is there any add-in, add-on, extension or whatever I can install in order to work with CMapStringToString objects?
Thanks in advance
You need to explicitly install MFC support in Visual Studio - which you can do on Community editions:
Open Visual Studio Installer from your Start Menu
Click the Modify button
Select the Individual Components tab
Scroll down to SDKs, Libraries and frameworks
Check the various MFC/ATL options for various platforms

Installer for Visual Studio 2010

I need to create a setup for installing my project. I meant to try both WIX both native visual studio installer, but i don't know how, when i go to new project there isn't such option. I figured out that WIX don't add templates on 2010, but why there isn't one for visual studio installer?
I would also like to know if there are any other simple installers worth trouble?
Visual Studio 2010 was the last version to support Visual Studio Installer (.vdproj) projects. Many teams use WiX Toolset instead. [UPDATE: There is now a VS extension that provides Visual Studio Installer support to later versions.]
WiX Toolset is a Visual Studio extension. Express versions don't allow extensions so that might be a reason you don't see templates. Another reason is that for the WiX installer to register templates, Visual Studio 2010 must be installed first. You can try repairing the WiX installation.
Another IDE for WiX is SharpDevelop. (It's free.)
Both Visual Studio Installer and WiX Toolset create Windows Installer packages. It's important to understand what Windows Installer does. If you are trying them to compare them, you might be interested in this related question.
NSIS is another technology entirely. It gives complete control over what's put the target system, including whether to have an uninstaller at all. Many projects use it as a bundler for Windows Installer packages. (But, note that WiX now has a bundler [called burn].)

Create MSI or setup project with Visual Studio 2012

I create a small application and I would like to create one MSI file.
In Visual Studio 2010 you have this project type under:
Other Project Types -> Setup and Deployment -> Visual studio Installer -> Setup Project
But the only thing you got in Visual Studio 2012 is "Enable InstallShield Limited Edition".
You can change the .NET Framework, but nothing changes.
Why is it not there any more? And how can I get it back? Is there a new way to do this?
Please see:
Visual Studio setup projects (vdproj) will not ship with future versions of VS
Windows Installer Deployment
It was announced 1 1/2 years ago that the project types were being killed. Alternatives are:
Use A VS2008/2010 Solution to build your installer
Switch to another tool such as InstallShield or Windows Installer XML
To create setup projects in Visual Studio 2012 with InstallShield Limited Edition, watch this video.
The InstallShield limited edition that cannot install services.
"ISLE is by far the worst installer option and the upgraded, read -
paid for, version is cumbersome to use at best and impossible in most
situations. InnoSetup, Nullsoft, Advanced, WiX, or just about any
other installer is better. If you did a survey you would see that
nobody is using ISLE. I don't know why you guys continue to associate
with InstallShield. It damages your credibility. Any developer worth
half his weight in salt knows ISLE is worthless and when you stand
behind it we have to question Microsoft's judgment."
By Edward Miller (comments in Visual Studio Installer Projects Extension).
The WiX Toolset, which, while powerful is exceeding user-unfriendly and has a steep learning curve. There is even a downloadable template for installing Windows services (ref. VS2012: Installer for Windows services?).
For Visual Studio 2013, see blog post Creating installers with Visual Studio.
Have you tried the "Publish" method? You just right click on the project file in the solution explorer and select "Publish" from the pop-up menu. This creates an installer in a few very simple steps.
You can do more configuration of the installer from the Publish tab in the project properties window.
NB: This method only works for WPF & Windows Forms apps.
Microsoft has listened to the cry for supporting installers (MSI) in Visual Studio and released the Visual Studio Installer Projects Extension. You can now create installers in Visual Studio 2013; download the extension here from the visualstudiogallery.
ISLE (InstallShield Limited Edition) is the "replacement" of the Visual Studio Setup and Deploy project, but many users think Microsoft took wrong step with removing .vdproj support from Visual Studio 2012 (and later ones) and supporting third-party company software.
Many people asked for returning it back (Bring back the basic setup and deployment project type Visual Studio Installer), but Microsoft is deaf to our voices... really sad.
As WiX is really complicated, I think it is worth to try some free installation systems - NSIS or Inno Setup. Both are scriptable and easy to learn - but powerful as original SADP.
I have created a really nice Visual Studio extension for NSIS and Inno Setup with many features (intellisense, syntax highlighting, navigation bars, compilation directly from Visual Studio, etc.). You can try it at www.visual-installer.com (sorry for self promo :)
Download Inno Setup (jrsoftware.org/isdl.php) or NSIS (nsis.sourceforge.net/Download) and install V&I (unsigned-softworks.sk/visual-installer/downloads.html).
All installers are simple Next/Next/Next...
In Visual Studio, select menu File -> New -> Project, choose NSISProject or Inno Setup, and a new project will be created (with full sources).
There is some progress for Visual studio 2013 developers :-D woot woot! See blog post Visual Studio Installer Projects Extension.
Link and information were retrieved from Brian Harry's blog post Creating installers with Visual Studio.
Have a look at the article Visual Studio Installer Deployment. It will surely help you.
You can choose the correct version of .NET framework on the page.
So for you, make it .NET 4.5. I guess that would be there for Visual Studio 2012.
I think that Deploying an Office Solution by Using ClickOnce (MSDN) can be useful.
After creating an Outlook plugin for Office 2010 the problem was to install it on the customer's computer, without using ISLE or other complex tools (or expensive).
The solution was to use the publish instrument of the Visual Studio project, as described in the link. Just two things to be done before the setup will work:
Install the PIA (Primary Interop Assembly) of Office 2010
Install the VSTO 2010 runtime

Restrictions on installing extensions or add-ins in Visual Studio 2010 Express

I installed MSVC++ 2010 Express and trying to figure which extensions (vsix) are available to install. There are some extensions in the Extension Manager (section Online Gallery). All of them from Visual Studio Gallery. To be sure I installed some extension. It, therefore, cannot be said that the express editions of Visual Studio do not support installing Extensions or Add-Ins. At first I decided that Visual Studio Gallery is the place for allowed extensions. I downloaded from there PowerConsole extension and tried to install it. However, I got message box with following text:
Visual Studio Extension Installer
This extension is not installable on any currently installed products.
The question is, What are exact limitations for installing extensions in Visual Studio 2010 Express?
Take a look at this article.
In summary from above article:
The Express SKUs only support installation of extensions that are classified as Templates (or Template Wizards) and Controls.
The Express SKUs do not support tool extensions. Which is anything that doesn't fall into one of the other
categories (Template or Control).
VSIX files are marked, via the manifest, as to which applications they are compatible and can be installed.

Default icons for Windows applications?

Does Visual Studio or MSDN provides a default set of icons for desktop applications, i.e. icons for common actions, GUI elements, data types, etc?
For instance, I have a button that the user clicks on to select a file, it would be nice if I could use Windows' standard folder icon.
For Visual Studio 2012 and 2013:
The icons are not in the program folder any more.
You can download the Visual Studio Image Library which contains most of the icons at http://www.microsoft.com/en-us/download/details.aspx?id=35825
It contains many icons from Visual Studio, Office,...
You should be able to find the icons in a zip file named "VS2008ImageLibrary.zip" located here:
%Program Files%\Microsoft Visual Studio 9.0\Common7\VS2008ImageLibrary\1033
check out http://www.famfamfam.com/lab/icons/ very nice and exhaustive icon sets. as far as I can tell they are free.
There is an image library packaged with Visual Studio. Do a search for icon files in the Visual Studio install directory to reveal its location. It may or may not be there, or will be in different locations, depending on the version of VS you have installed.
If memory serves the Express editions come without this feature, but all other versions since at least Visual Studio .NET do.

Resources