Unable to create 64bit msi installer using VS 2010 - windows

I want to create a 64 bit msi installer using VS 2010.
I try to create a project by clicking on
Other Project Types->Setup and Deployment->Visual Studio Installer->SetUp Project.
But project does not allow Target platform to be edited, it is blank by default.
I want to create msi installer for 32 as well as 64 bit.

Visual Studio Setup and Deployment (VDPROJ) projects don't support creating x64 installers. This is one of the many reasons why Microsoft killed that technology in VS2012.
The replacement tool is InstallShield 2013 Limited Edition and it does support 64bit installations.
If you want to stay on VS 2010 then you'd need to consider using InstallShield 2013 Professional and/or Windows Installer XML (WiX).

Related

Can I use existing Visual Studio 2017 Workloads (from Community Edition) on a Visual Studio 2017 Professional Edition?

I've upgraded to Visual Studio 2017 Professional - to replace my existing Community Edition installation. I'm currently on the go, and have only limited data via my phone.
I was wondering if there is a way to migrate my existing workloads (ie VSTO, .NET Desktop Development, Universal Windows Platform Development, ASP.NET and Web Development, etc... that you select at installation) from my 2017 Community Edition installation, or if they are incompatible and I will have to download everything once again.
My existing Community Edition Installation is V15.0.
My new Professional Installation is V15.7.1.
I know it is easy to bring up the installer to get these packages when I once again have real internet access, but in my current situation, I won't have that real internet access for a while and need to utilise those development workloads in the meantime - is there a way to migrate these packages?
Thanks.
there is a way but I can't guarantee for you the stability of the new installation.
copy the content of folder yourDisk:\Program Files (x86)\Microsoft Visual Studio\2017\Community to
yourDisk:\Program Files (x86)\Microsoft Visual Studio\2017\Professional
Be careful when copying dlls do not merge some existing files if they match in name and don't match in version or in size (you should compare dll with binary comparaison.

how to make standalone visual studio application which can run on any system without having visual studio

I made an application using VS 2010 and want to run that application on other system which don't have VS 2010.
How can i make my app independent of dependency from VS 2010,so that it can run on any system without installing VS 2010.
If this is a managed application then you need only the appropriate .NET framework version on the target machine (and of course any other dependencies your app may have).
If this is a native application then you need the VC++ 2010 Redistributable package. You need however the redistributable that matches your VS 2010 version (RTM or with SP1) and the project target architecture (x86, x86, IA64). Here are the links for the VC++ 2010 redistributables:
x86
VS 2010 RTM
VS 2010 with SP1
x64
VS 2010 RTM
VS 2010 with SP1
IA64
VS 2010 RTM
VS 2010 with SP1
You need to create an installer for it. The installer will install the .NET framework and any other requirements you may have.
I googled 'creating installer in visual studio 2010' and got some encouraging results.
Examples from results:
https://www.youtube.com/watch?v=IEgE51Lcpg0
http://msdn.microsoft.com/en-us/library/t71a733d.aspx
http://msdn.microsoft.com/en-us/library/ee942965%28v=vs.100%29.aspx
Search for ClickOnce in case the application needs to run for noon Admin users (installs to local user folders).

InstallShield 2008 Pro with Visual Studio 2012

I'm having an old version of InstallShield 2008 Pro which work perfect with my Visual Studio 2008 Pro 32bit application deployment.
I'm moving towards Visual Studio 2012 with porting application to x64.
I could not find much information on InstallShield 2008 from the flexira website. With next to 0 experience in InstallShield I have a couple of questions regarding the deployment -
Is InstallShield 2008 is sufficient to cater Visual Studio 2012 with x64 upgarde.
Do I need to upgrade to InstallShield 2012 or better off looking at open/free project like WiX.
Any other comments are welcome in this regard.
For supported InstallShield integration with Visual Studio 2012, you will need InstallShield 2012 Spring or later. Integration nets you the use of project output groups; if you are willing to do without those, you can use InstallShield outside of Visual Studio, and the primary concern is which versions of Windows you need to support and how cleanly.

Open .ISM with InstallShield Limited Edition

Environment: TFS 2010 + VisualStudio 2010 + InstallShield Limited Edition.
I am sorry to be novice about InstallShield.
I have a InstallShield project with .ISM extension. Is it possible to load it in InstallShield Limited Edition. I tried but it is not recognizing the .ISM extension.
I tried to create New InstallShield project using InstallShield Limited Edition. It generates .ISL and .ISPROJ extensions instead of .ISM.
What is .ISM (IF InstallShield is creating .ISL and .ISPROJ project
files)?
How can I work on .ISM InstallShield setup (project) , using
InstallShield Limited Edition (if possible)?
My minimum requirement is to look into the existing setup , even if not enabled to build and generate an MSI.
Thanks and Regards
Sumeet Nandan Garg.
InstallShield limited edition cannot import, open, or build projects created in a paid edition of InstallShield. In order to get a better idea what is in that project, you might try evaluating the Professional or Premier edition of InstallShield. If you find that you need anything beyond the capability set of the Limited Edition, you will likely need to purchase the Professional or Premier edition.

Which one to use, Visual Studio Installer or Inno Setup?

I asked some questions about Inno Setup and .NET Framework installation. Now I am thinking whether is it better to use Visual Studio Installer or Inno Setup?
Which of the two do you think is better and more functional for this type of problem, and in general which is better to use for installer creation?
In general, Inno Setup is easier and more reliable, but if you must ship an MSI, use Visual Studio. See here for installing .NET with Inno.
Visual Studio Installer is retiring in 2010 so for future use it is not suitable. Also there is a tool called InstallShied Limited Edition in VS 2010 for creating installers (based on some other technology).
If you want to create installers directly in Visual Studio try this extension called Visual & Installer: http://visualstudiogallery.msdn.microsoft.com/5e57fe9a-ae5d-4740-a1c3-7a8e278e105b
It supports Inno Setup and NSIS (Nullsoft Installer, both are free and open sourced) and VS 2012 and VS 2012 are already supported so it looks fine.

Resources