Today I had to reinstall. I used to have some hotfixes installed for VS2008 but no longer have them and can't remember why they were necessary. I'm expecting any security-related hotfixes to come through Microsoft Update, but I'm interested in VS bug fixes.
Does anyone have a list of hotfixes that they recommend installing for Visual Studio 2008 SP1?
You can find them all here:
http://kbalertz.com/Technology_639.aspx
Look for the ones with a "FIX" prefix.
Update: This is another good source of information about VS2008 updates.
http://code.msdn.microsoft.com/Project/ProjectDirectory.aspx?TagName=Visual%20Studio%202008&ProjectSearchText=Hotfix
Suggested hotfixes (links updated 4/2015):
KB957912 - Update for Visual Studio 2008 SP1 Debugging and Breakpoints
KB958502 - JScript Editor support for “-vsdoc.js” IntelliSense doc. files
KB960075 - VS Dev Environment crash after undocking windows or changing layouts
If connecting to TFS 2010:
KB974558 - Forward Compatibility Update
KB980216 - Error message when running unit tests with Forward Compatibility Update installed
Complete list of VS 2008 hotfixes (including TFS).
I recently rebuilt my machine. After installing Visual Studio 2008 and SP1 I was wondering about the same thing. In the end I used Windows update to check for updates and it found the following updates:
KB2465361
KB971092
KB72222
KB973675
Screen shot:
http://i.stack.imgur.com/yFf8H.png
All the VS2008 hotfixes are posted in the MSDN Code Gallery. You can search for tags "Visual Studio 2008" and "Hotfixes". You should only install the ones for problems you are actually having. Read through them and decide which ones you need. I would sort them by release date and install from older ones first. Also notice that some are included in other updates, such are the WPF designer hotfix included with the Silverlight tools.
I'm using Microsoft Connect - Visual Studio and .NET Framework as a source of updates for:
.NET 2.0+
VS2008
VS2010
I generally go with the ones that are pushed though Microsoft Update.
I thought that you can get bug fixes though Microsoft Update too.
If they don't come down automatically go to the site and look through the "Software, Optional" ones (or in the "Developer Tools" section).
Select Custom at the first screen and then wait a few minutes while it does it's scan.
However, there aren't any showing for me at the moment so I can't say for sure.
Related
I have installed VS2012 Ultimate on a fresh PC. I tried adding the Crystal Reports file in my project but there is no crystal report .crt Item avaliable into Add New Item menu of the VS2012
Is there a version for VS2012? or do I have to install an extra setup file for crystal reports which is redundant since I already have VS2012 installed.
Here it is! - SP 25 works on Visual Studio 2019, SP 21 on Visual Studio 2017
SAP released SAP Crystal Reports, developer version for Microsoft Visual Studio
You can get it here (click "Installation package for Visual Studio IDE")
To integrate “SAP Crystal Reports, developer version for Microsoft Visual Studio” you must run the Install Executable. Running the MSI will not fully integrate Crystal Reports into VS. MSI files by definition are for runtime distribution only.
New In SP25 Release
Visual Studio 2019, Addressed incidents, Win10 1809, Security update
This post is right from SAP on Sep 20, 2012.
In short, they are still working on a release of Crystal Reports that will support VS2012 (including support for Windows 8) It will come in the form of a service pack release that updates the version currently supporting VS2010. At that time they will drop 2010/2012 from the name and simply call it Crystal Reports Developer.
If you want to download that version you can find it here.
Further, service packs etc. when released can be found here.
I would also add that I am currently using Visual Studio 2012. As long as you don't edit existing reports they continue to compile and work fine. Even on Windows 8. When I need to modify a report I can still open the project with VS2010, do my work, save my changes, and then switch back to 2012. It's a little bit of a pain but the ability for VS2010 and VS2012 to co-exist is nice in this regard. I'm also using TFS2012 and so far it hasn't had a problem with me modifying files in 2010 on a "2012" solution.
There is also someone who managed to modify CR for VS.NET 2010 to install on 2012, using MS ORCA in this thread: http://scn.sap.com/thread/3235515 . I couldn't get it to work myself, though.
"SP25 work on Visual Studio 2019" is an exaggeration. It is extremely unreliable and should be avoided at all costs. I currently have to maintain a second development environment with V2015 for report development.
I am missing the edmx designer in VS 2010 SP1 Ultimate in Windows 7 64 bit. I uninstalled VS 2010 using VS2010_Uninstall-RTM.ENU.exe and reinstalled VS 2010 and SP1. When runing VS 2010, I got some messages like "The 'Microsoft.Data.Entity.Design.BootstrapPackage.BootstrapPackage.... package did not load correctly". I also noticed that Microsoft.Data.Entity.Design.Package.dll is missing. Then I did a "ADONETEntityFrameworkTools_enu.msi USING_EXUIH=1 /log "Log.txt" which gave a message "A later version of microsoft Visual Studio 2010 ADO.NET Entity Framework Tools is already installed". I looked at he log file but I couldn't determine the problem. How did it know there's a later version?
The EF tools entry does not show up in the control panel -> programs.
I had the EF June 2011 CTP installed but was uninstalled some time ago.
I also did "msiexec /update [DVD drive letter]:\VS10sp1-KB983509.msp /package {14DD7530-CCD2-3798-B37D-3839ED6A441C}" and got message "This action is only valid for products that are currently installed". This is odd because one installer tells me there's a later version and another installer tells me it's not! (from http://blogs.msdn.com/b/adonet/archive/2011/06/30/announcing-the-microsoft-entity-framework-june-2011-ctp.aspx)
I also did "devenv.exe /installvstemplates" and ran these installers: DACFramework_enu.msi, DACProjectSystemSetup_enu.msi & TSqlLanguageService_enu.msi.
I am out of ideas. How do I get the edmx designer back?
If VS thinks EF tools are already installed, why aren't they working? I couldn't find the SP1 version of ADONETEntityFrameworkTools_enu.msi. I am guessing there are remnants from the CTP. How do I do a thorough cleanup? I used the control panel to remove everything related to VS. My last idea is to use SysInternal's Process Explorer and possibly spend hours digging into this.
Try installing the June CTP again and then try uninstalling it again...
I have around 50 projects in Visual Studio 2005 that I am building a new development machine for and I'd like to slowly move those projects to VS 2008 but also have 2010 available for select new projects.
Can this work? Are there any gotchas for this sort of setup? Any general advice for running multiple versions of Visual Studio on the same system would be greatly appreciated. Specifically related to managing a controlled migration of projects to new versions but being able to selectively keep some on old versions.
I've got 7.1, 8, and 9 installed at the same time (well, and VB part of 6 as well) and I've not really had a problem opening projects file in the wrong version. The Visual Studio Solution files is "associated" with a particular version even if they all have the same extension of .sln, as you can see from its little icon. Microsoft Visual Studio Version Selector seems to handle individual project files (.vcproj) fine as well.
The only thing I've had is the individual source code files not opening up in the latest version like I want, but that's easily fixed with the click of a little button in VS Opions.
Microsoft have this to say:
Visual Studio supports the installation of Visual Studio .NET 2002, 2003, ... on the same computer.
In general, you should install the earliest release of Visual Studio first, and then install subsequent versions of Visual Studio in the order in which they were released.
Make sure when you open up the 2005 files you're doing it in 2005. To open them in another would require a conversion which would render them incompatible with the older compiler set-up. To aid this, structure whatever workspace you're using into 2005, 2008, and 2010 so as to minimize accidental chance of this.
Second, when you double click to open the projects, it will invariably attempt to open them with 2010. You'll have to start with VS#### instead of the solution/project unless you're in the 2010 workspace.
I have VC6, VB6, VS 2008, and VS2010 RC installed on Windows Vista. I cannot double click on the VC6 dsp files without VS2010 opening and asking to perform the conversion. The 2008 C# projects open in 2008 as long as I use the solution file. The 2008 project file opens in 2010 instead of 2008 even though the version selector is the default program. Most of the time I try to remember to open the desired version of Visual Studio and then open the project.
You can mitigate some of these issues by changing the default program associations in the control panel or the registry.
Update: This setup works on Windows 7 x64, with the addition of VS2013.
Yes it can work. I'm not sure if you have to install them in a particular order... but install them in order of the versions... 2005, 2008, 2010. Should be good to go.
I can't speak for 2010, but I have run 2005 and 2008 at the same time on my system without any fuss.
And I made the double-click mistake that wheaties warns about more than once :(
I have VS2005 & VS2008 running without any issues. I have had problems when working with betas, express editions & am assuming you don't have them.
I would say refrain from making too many changes to the setup of these editions, it should be fine.
I also had the same doubt. I work at my company which is still on VS 2008 and I want to personally use the VS 2010 and not risk the 2008. I installed the 2010 and it worked fine with the 2008. Just make sure you note the projects that are in 2005 and open them with the same accordingly.
The reason why it works is simple: if you open your solution file in Notepad, you'll see which version of VS is related to your project.
Does Visual Studio 2010 RC play nicely with Visual Studio 2008?
I am wondering if I need to setup a Virtual Machine to play with VS 2010 or if I can just install it on my Dev machine.
If it messes up VS 2010 then that is sad but ok. If it messed up VS 2008 then I would be in trouble.
Has anyone tried this out? Does it work well? Poorly?
Thanks for any answers.
I've had no problems. Microsoft has designed the last several versions of Visual Studio to be able to co-exist side-by-side.
That said, VS 2010 is an RC, so it is still a pre-release. And even after it goes RTM, it's still a complex product and like any complex software install there can be bugs. I wouldn't expect serious problems, but there's always the fraction of a percent that do run into issues. So I'd still plan to install it on a day when you'd have cycles to deal with potential issues (if nothing else, installing it on my machine that hadn't had OS updates installed in a while required at least 2 reboots).
Yes this works and is a supported scenario. My advice is to install 2008 first then 2010. This is the setup i have on multiple computers.
has worked for me without any issues so far. I would follow JaredPar's advice though, install 2008 first, then 2010.
I never trust the "plays nice with others" claims because I've been bit by it before. They supposedly co-exist, but I still put it in a VM.
See this blog post.
Visual Studio 2010 / .NET Framework 4 RC Ready for General Download
I haven't installed it on my machine but my manager has and after we looked at it we decided it's best not to go there yet for two reasons:
1) We have to go through the whole conversion process again, which after our experience with 1.1 -> 2.0 wasn't very enticing.
2) We caused an error within the first couple minutes of playing around that worked fine on VS2008 leading us to believe it's not quite ready for primetime yet anyways. (It was adding a method in the class diagram that caused VS to crash for some reason).
Just my two cents though.
edit: I just found another great example, fifth one down: http://thedailywtf.com/Articles/Tell-a-programmer.aspx
I've had no problems either. And I didn't with VS2010 beta 2 and VS2008 either.
I have both of them on my machine, so far no problems
I havent go into too much testing with my VS 2008 projects in 2010, but it does look like it works fine with VS 2010 RC.
Also, both versions seem to run fine on my machine. (I have also VS 2003 on my local as well)
Bearing in mind its the Release Candidate version, is should be very reliable in this area.
I've run into an error with IIS and VS2010 -- it's solved by re-running the .NET 3.5 version of aspnet_regiis.
http://social.msdn.microsoft.com/Forums/en-US/vsprereleaseannouncements/thread/44dfcf76-bede-4f96-a556-b219a18b6116
I installed 2010 with 2008 already installed. I had tons of hangs, crashes and general malfunctions. Reinstalling 2008 didn't help until I removed every trace of 2010 from registry.
I've installed 2010 with 2008 on this machine for silverlight development.. I haven't noticed any problems except for file associations all goto the 2010 version rather than what I'd prefer opened in 2008 by default. (2010 to me is much slower than 2008)
I use Visual Studio 2k8 Pro Edition at home and I have loaded it with a lot of important addins customised for my development.
If I get VS2010 Pro Edition, would all of these plugins fail to work? Is this a plugin-related matter or down to Visual Studio itself? E.g. Visual Studio 2010 may just be based on the 2008 version but with enhancements (is it?).
Thanks
You can always download the beta and try them out.
Impossible to say without seeing it in practice. Seriously. We don't know which plug-ins you're using so we've no idea how they're going to react to a new VS version...
But even you had told us, you'd save yourself a lot of time just installing VS 2010 in a VM and trying your plug-ins out.
Nope at least Resharper 4.5 is not working in VS2010
No. Unmanaged addins are COM objects that are tied to the version of the IDE environment. For the most part, the addins just need to be rebuilt with only minor changes though.
EDIT: Addins that go beyond using the standard addin interfaces though will probably require retooling for the VS2010 environment.
EDIT 2: Managed addins are typically deployed using .addin files which are sometimes located in "%APPDATA%\Microsoft\MSEnvShared\Addins". The .addin file is an xml file that can be edited by hand. You can try adding a new HostApplication element to the file for a particular managed addin - and specify version 10.0.
Here is the info on the resharper compatibility:
http://blogs.jetbrains.com/dotnet/2009/05/preview-of-resharper-for-visual-studio-2010-coming-soon/
(Basically they will have a preview release in June)