When downloading Visual Studio Professional 2013, you have the option of downloading 32-bit and 32-bit web installer. What's the difference?
The web installer installs a small stub that then downloads the rest of the program. So you end up with Visual Studio installed but not a installer file (so nothing you could copy to another machine to install).
The web installer though may be quicker as it only downloads what you need based on your selection
Related
My SW project depends on Visual C++ Redistributable for Visual Studio 2015.
If the Redistributable is not installed on a target machine, I would like to download it from the Internet and install it during installation of my project.
Is it possible to do using Wix installer?
I prefer not to use merge modules and include the Redistributable to the my application installer.
Thanks
Yes, using a bundle. See http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/install_dotnet.html for how it's done with .NET. For VC redistributables, you'd need to define your own ExePackage for vcredist_x86.exe or vcredist_x64.exe.
I have Visual Studio 2008, 2010, and WIX37.msi (WIX 3.7) installed on my machine.
However, I am unable to see WIX project type in Visual studio 2008/2010.
Do I need to install additional tool/plugin?
I have Visual Studio 2008 and Visual Studio 2010 installed on my machine and I installed WiX v3.7 RTM from Codeplex. Things work okay for me. There is a known issue in VS2008 that requires you to set an MSBuild property called RunWixToolsOutOfProc to true. This occurred because parts of WiX v3.7 were incorrectly built against the NETFX4.0 and VS2008 runs on NETFX2.0.
Install v3.0 of WiX Toolset, to make it work with Visual Studio 2008. You can get it here: http://wix.codeplex.com/releases/view/44406
I don't know why it's not documented on their site but apparently you can't install the latest version (3.10 at the moment) and make it work with VS2008.
I developed the project in visual studio 2010. That exe file is not supported for other PC's.
which dotnetframework to be installed? other than dotnetframework is there any other requirements needed?
Are you sure it's not the CPU type you specified during compiling (x86 vs x64 CPU). If you compiled in 64-bit and a user only has a 32-bit processor (x86), your code won't run.
The .Net Framework should work on any PC-based system, but be sure to include it in your deployment or setup package. (you can provide Excel, .NET Framework, and many other packages with your package.)
You should also try to find out what error messages your users are receiving -- which will point you in the right direction.
I have already using Visual Studio 2010 for my project. Now I have to work with a Visual Basic 2006 legacy application. Can I install VB 2006 Enterprise Edition on my system?
Will this affect Visual Studio 2010?
Yes. Visual Studio 2010 and Visual Studio 6 will happily install side-by-side.
You can run multiple versions of Visual Studio on the same machine. I currently have VS2003, VS2005, VS2008 and VS2010 installed and am using all of them.
Where you may get into problems is with something like hooking up the older ones to TFS. This can be done, as I have VS2003 and VS2008 connected to TFS2010, but my VS2005 won't work as it whinges about the provider for some reason.
Another area to watch out for is IIS. As you have already installed VS2010, IIS may be defaulting to .Net 4.0 so if you start deploying .Net 2.0 apps then the websites may not work without some adjustment of things like app pools.
But if you are just using them independently of each other then you should be fine. If you're really paranoid, consider creating a VM and installing the old VS on it.
EDIT
I see from your edited post that you were talking about VB6. This also can be installed alongside any of the later versions of Visual Studio.
Is there a reference on creating a Visual Studio 2010 Installer project for a WinForms application that uses SQL 2012 LocalDb?
I'm not aware of any good reference, but it is pretty easy. The ClickOnce packages are compatible between Visual Studio 2010 and 2012, so all you'd need to do is to install Visual Studio 2012 somewhere to get the LocalDB bootstrapper (free VS 2012 Express for Desktop) and copy SqlLocalDB2012 folder from C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\Packages to C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages (depending on your Windows installation the location could be slightly different, but should be easy to find).
Now the caveat is that to connect from .NET to LocalDB you need .NET 4.0.2 or later. I don't think there is a bootstrapper for .NET 4.0.2 anywhere. So you will either need to implement it yourself, or target .NET 4.5. You should be able to copy the .NET 4.5 bootstrapper from VS 2012 just like you can copy the LocalDB one.