Visual Studio 2005 SP1 Released

Visual Studio 2005 SP1 has been released, this is needed if you are using Visual Studio for CE 6.0 o/s development and application development – of course you should install SP1 if you are using Visual Studio for regular desktop application development.

Heath Stewart has useful information about installing the SP1 update for VS 2005 – if you’ve installed the Beta drop you should remove this before installing the SP1 bits.

Here’s a quick list of updates:


  • Windows Embedded 6.0 platform and tools support
  • New processor support (e.g., Core Duo) for code generation and profiling
  • Performance and scale improvements in Team Foundation Server
  • Team Foundation Server integration with Excel 2007 and Project 2007
  • Tool support for occasionally connected devices and SQL Server Compact Edition
  • Additional support for project file based Web applications
  • Note that there are two additional updates in the works that you should be aware of, the first is for developers using Vista known as “Visual Studio 2005 SP1 Vista Refresh Beta”, the second update is a Windows Embedded CE 6.0 Service Pack – dates are not available for these updates, I will post more information on these updates as it becomes available.

    – Mike

    Comments (11)

    1. Bob Zurad says:

      I’ve installed SP1, but now I cannot debug my applications on my Windows CE 5.0 device.  I can’t use ActiveSync, so I use ConmanClient2 and CMAccept to debug my apps.  However, after installing VS 2005 SP1, I keep getting error messages on my dev computer (xp pro sp2) saying that ActiveSync is not installed.  It’s the same error that I would get before I upgraded to SP1, however, running ConmanClient2 and CMAccept resolved this.  

      Has something changed with ConmanClient2 or CMAccept with SP1?  I noticed that the date on ConmanClient2 is newer, but CMAccept is the same. Do I need to rebuild my CE OS image?  Do I need to use your FileWiz app and make a new catalog item in my OS design that includes the new ConmanClient2?

      Thank you.

    2. Larry Hull says:

      Bob, I have also had the same experience on my systems (I have tried it on 3 different systems, all running XP Pro SP2). If SP1 is installed VS 2005 cannot connect to my CE 5.0 target system using ConmanClient2 & CMAccept (if you have ActiveSync installed on your development system you will get the following message instead: “The configuration data for this product is corrupt.  Contact your support personnel.”). If I remove SP1 then everything works OK. So right now I have a dedicated system without SP1 installed for my 5.0 target systems.


    3. Bob Zurad says:

      Larry, thank you for your post.  Now I know I’m not alone.  

      I used FileWiz to make a new catalog item for the files in C:Program FilesCommon FilesMicrosoft SharedCoreCon1.0Targetwce400armv4i.  I then rebuilt the project and ran sysgen on the OS image.

      After all that I still cannot debug my apps with ConmanClient2 and CMAccept.

      Mike, what’s going on?

    4. David Vescovi says:

      Yup, broke my setup also. Can’t debug or deploy to CE 5.0 device via ActiveSync anymore. Removed SP1, back to normal. Can’t believe they didn’t test this scenario.

    5. mikehall says:

      after installing VS 2005 SP1 the CoreCon bits will have been updated/replaced on your development PC – if you have a CEFileWiz component that wraps the CoreCon bits you will need to rebuild the CoreCon project (which will copy the update CoreCon files to the Build Release Folder) – a rebuild of the CoreCon project will also force a MakeImg, so your new image should have the right bits in it…

      If you are running a debug build of the o/s can you capture the debug output when you run ConManClient2 and CmAccept and then try to connect from VS 2005 for application development ?

      – Mike

    6. bobzurad says:

      I rebuilt the CoreCon project and ran MakeImg.  Still no luck.  

      The only debug build I have is with the emulator, but when I try to attach to the device I get the following errors:

      (CoreCon)  16:39:07 12/22/2006 Central Standard Time:  Failed to co-create service host!

      (CoreCon)  16:39:07 12/22/2006 Central Standard Time:  Transport service failed to connect

      (CoreCon)  16:39:07 12/22/2006 Central Standard Time:  Warning:  One or more services failed to connect.  Make sure that the service is properly configured.

    7. David Vescovi says:

      After struggling a bit more, I got it.

      The old set has the property version 8.0.50727.42 RTM. The new set should be 8.0.50727.762 SP. Make sure "Visual Studio 2005" shows up as the "Product Name" property of the files.

    8. Joshua Moore says:

      The reference for this is:

      You need to copy new target files to your ce device.  They were updated on your PC during the install.  The files are located in:

      C:Program FilesCommon FilesMicrosoft SharedCoreCon1.0targetwce400<processor type>

    9. Kris says:

      I’m trying to find the updated versions of all the files…but…all of the files that I’m finding on my PC are .42.  Is there a trick to getting the .762 files?  Or, is there a website we can pull them from?


    10. Josh Stodola says:

      I am so sick of the Error List in Visual Studio 2005 (before AND after SP1).  It is telling me I have errors and warnings that I fixed WEEKS ago.  I double click on the error/warning, it does NOTHING.  I have no way of getting them off the list and it is very aggravating.

      What the heck is the deal?!?!!?

    11. Lucas says:

      Same problem for me, the SP1 completely brokes my configuration. Now when i’m using the SP1 version of CMAccept/Dbgcon files on my WinCE5.0 device, it completely freezes the device. Ahhhh, should have never installed the SP1 (damn .. i knew it !)