Announcing Visual Studio 2010 Service Pack 1 Beta


I’m happy to announce that the Visual Studio 2010 Service Pack 1 Beta is now ready for download! MSDN subscribers may download the beta immediately with general availability on Thursday. Service Pack 1 Beta comes with a “go live” license which means you can start using the product for production related work (see the license agreement with the product for more details).

Since the launch of Visual Studio 2010 and the .NET Framework 4 earlier this year and our subsequent Feature Packs, we have been concentrating on your feedback and worked hard on the issues you reported through Connect and our survey. I just recently blogged about the results from our recent survey and called out some of the latest improvements the team has delivered.  

Service Pack 1 (SP1) continues that momentum of focusing on improving the developer experience by addressing some of the most requested features like better help support, IntelliTrace support for 64bit and SharePoint, and including Silverlight 4 Tools in the box. Some of the additional highlights are:

  • Help Viewer –  The new local Help Viewer is a simple client application that re-introduces key productivity features including a fully-expandable table of contents and a keyword index.  For additional information about these improvements, check out Jeff Braaten’s post here.

 

  • Better platform support – Looking at support of platforms newly-available around Visual Studio 2010 release, we wanted to make small investments to upgrade our support for them. Silverlight 4 Tools for Visual Studio 2010 (with a few updates to RIA Services) is now included in the box along with Silverlight 3 support, underscoring our commitment to that quickly-evolving platform. We’ve also made a number of other targeted changes, including some additional Win7-specific MFC APIs to support use of Direct2D, DirectWrite, and Windows Animation Technologies. There were also a number of areas where you told us we could do better, so we went in and filled some holes:
    • Unit Testing on .NET 3.5 – today all unit tests are run under .NET 4. While acceptable for most users because of the compatibility work we did in .NET 4, this caused problems for some of you with .NET 3.5-specific dependencies.
    • IntelliTrace F5 for 64 bit and SharePoint projects – you’ve told us that IntelliTrace is great, but you want to use it on all the projects you’re working on.
    • Performance Wizard for Silverlight – Similarly, our performance profiling tools are very useful, but you want to use them for your Silverlight development as well. Silverlight projects are included in the Wizard just like your client projects today.
    • VB Compiler runtime switch – This switch will enable Visual Basic developers to target their apps and libraries at platforms where the full Visual Basic Runtime hasn’t traditionally been available.

As an engineering team, the goal for this Service Pack was to work hard on releasing a high quality beta with a focus on only fixing the top-set of important issues we heard about from our customers. Please download the beta and send us your feedback through our Visual Studio Connect site and/or submit your feedback via our Service Pack 1 Beta Survey.

Enjoy!

UPDATE

If you have “ASP.NET MVC 3 RC” installed, please be aware that installing Visual Studio 2010 SP1 Beta will break Razor IntelliSense.  There will be a new “ASP.NET MVC 3 RC2” installer released next Monday that you can upgrade to in-place. If you’ve already installed Visual Studio 2010 SP1 Beta, don’t uninstall the Beta Service Pack, just wait until Monday and upgrade your MVC installation.

If you have “Visual Studio Async CTP” installed, please be aware that installing Visual Studio 2010 SP1 Beta will break Visual Studio Async CTP. We are looking at options for an updated release that will make the Visual Studio Async CTP compatible with Visual Studio 2010 SP1. In the meanwhile if you need to work with the CTP you should stick with VS2010 RTM.

Comments (109)

  1. John Doe says:

    Is it faster than before? Because VS 2010 is slow as hell!

  2. John Doe is a Troll says:

    VS 2010 is smooth and quick – great work! Way to go on the help viewer; the HTML one was meh, this is better.

  3. John Doe says:

    If I have a complaint I am a Troll! That is good logic! I am a professional .NET developer and I am really upset with VS 2010. It crashes more often than VS 2008. It is slow as hell. It even crashes when debugging. VS 2010 is built with WPF which is causing all these problems.

  4. Jasonz says:

    @John Doe – I'm definitely interested in hearing all feedback. Can you contact me through this blog with your specific issues?  We'll take a look.  thanks, Jason

  5. Ash McConnell says:

    I am experiencing the same problems as John Doe.  The strange thing is, sometimes it's really quick, but mostly it's very slow (45 secs for a single cpp change!) – when it's compiling it doesn't use much CPU at all, so that's not the problem and there is plenty of RAM available (4 gig in total).  If I can figure out what is causing it I'll report to connect, but currently I can't see a pattern or reason behind it.

  6. redwolvx says:

    Hi Jason,

    Great to hear SP! is finally being realeased into the wild.

    Just wanting to confirm that it does include the fix for the follwing bug I submitted

    connect.microsoft.com/…/report-viewer-2010-report-at-zoom-100-is-huge-was-fine-in-2005-2008

    Cheers

    Duncan

  7. David Scheidt says:

    What about IIS Express Integration?

  8. Will says:

    After ages here (hour or so), it's failed, asking for an x64 prerequisites file at a bogus-looking location ("1").    It's now rolling back because I don't actually have that file (it was a .EXE install which did the main download itself, not a DVD download)

    Are you set-up to get the automatic feedback from this installation failure?

  9. Pete Wilson says:

    Is there no source for a detailed list of changes/fixes?

  10. Scott W says:

    Can you provide a link to the list of bug fixes that are fix in the SP?  I don't see the KB article or anything on Connect?  I am sure hoping the list is very long.  Bug fixes are much better than enhancements.

  11. onovotny says:

    Is there any word about compatibility with the C# 5 Async CTP?  Do we need to uninstall it first?  Will there be an updated version that works with the beta or will we need to wait until the SP RTM before the next release.

  12. Swylie says:

    If I install and build with the new SP1 beta but i DON'T deploy it to my client machines, will the app still run on the client?

    I don't want to be installing a beta framework on their machines and then install an RTM one later.  I want to fixes as a developer but don't to do more work in deployment.

  13. Pieter says:

    Is there a KB detailing all changes?

  14. James says:

    I agree with John Doe vs2010 is slow and buggy (ex undo feature is corrupted)

    moving to WPF was one of the worst mistakes ever made.

    vs2008 is super fast by comparison.

    sigh, C# is slow, WPF is slow, silverlight is slow, can microsoft do anything right ? that is not slow ?

    please undo that WPF switch, please !!!

    i just knew WPF was a bad move for vs2010 but did the devs listen? nooo! So here it comes "I told you so".

    Ok now you have made your mistake and got burned hand, can you listen me now and remove WPF from vs2010.

    everything that can be done in wpf can be done in native code, just fine, you just have to use your brains and stop trying to be so lazy all the time!

  15. Steve Goyette says:

    Does this fix the debugging problems? In general I've found 2010 to be stable, quick and a great overall development experience…with the exception of the debugger which just seems to stubbornly refuse to honor breakpoints and will run off home to mama while stepping through code. A fix to this would certainly enhance my overall development satisfaction and cause me to become outrageously productive and the envy of all non VS2010 users.

    Steve

  16. Scott Hanselman says:

    <font color="red"><b>IMPORTANT NOTE: If you have “ASP.NET MVC 3 RC” installed, please be aware that installing Visual Studio 2010 SP1 Beta will break Razor IntelliSense. There will be a new “ASP.NET MVC 3 RC2” installer released next Monday that you can upgrade to in-place. If you’ve already installed Visual Studio 2010 SP1 Beta, don’t uninstall the Beta Service Pack, just wait until Monday and upgrade your MVC installation. </b></font>

  17. John Dope says:

    Jason, Can Intellitrace be finally used with Silverlight? Is this part of the SP1 Beta?

  18. Jon Kragh says:

    I'm also hoping this improvement marked as fixed is in VS 2010 SP1:

    connect.microsoft.com/…/add-aspx-or-inline-c-as-an-option-in-text-editor-formatting-options

  19. Jasonz says:

    thanks everyone for the comments, lots of great questions as well.  some answers:

    @Ash – I'd be very interested in hearing about your config, project, etc so we can help identify what issue you might be seeing.  Please do feel free to contact me directly through this blog.

    @redwolvx – [[bug fixed?]]

    @David – IIS Express does work out of the box with the release, but we do not install IIS Express itself with our setup.  You can get IIS Express here: http://www.microsoft.com/…/install.aspx

    @Will – Sorry to hear you are having problems with the installation.  Can you contact me directly and we can help diagnose the issue?  These sort of things often have to due with bad state on a client machine (reg keys or temp files).

    @Pete – we don't have a formalized bug fix list but we have concentrated heavily on user feedback for this release.

    @Scott W – our focus for this SP was definitely on fixing user requested issues.  You will find very few feature enhancements (primarily those mentioned above which were very frequent requests).

    @onovotny – [[C# Async CTP]]

    @Swylie – The servicing update to NETFX (which we do install) is designed to be 100% compatible with NETFX 4 RTM.  We are not updating the existing multi-targeting reference pack because of this.  So it winds up being just like targeting NETFX 2.0 from VS2010:  the version of the runtime we use to run VS is not the same as the version you deploy to the client and the references you add into your project are under your control.  You're good to go.

    @Pieter – we don't have a full list of changes but it was focused primarily on bug fixing for this release.

    @James – I'm sorry to hear you are having issues with the release.  I'd be very interested in hearing your (concrete) issues that you have run into.  Please let me know the machine config, project type, and what kinds of operations you are trying which are causing you issues.

    @Steve – We've definitely concentrated on fixing reported issues through the Connect site.  Do you have a specific issue number you have filed we can check on?  I generally do not hear of the type of problem you are describing so I'd be interested in making sure we follow up.

    @Scott Hanselman – thanks for the heads up; I will add an update into the mainline text also.

    @John Dope – nothing new to report on this release, sorry

    @Jon – Generally bugs marked fixed will be in this SP.  Give it a try and make sure and send us your feedback.

  20. Jasonz says:

    I realized I missed a couple of answers as I composed all the responses, sorry about that:

    @redwolvx – the best way to tell if the bug is fixed is through the status (e.g. active vs fixed).  this one is still marked Active which leads me to believe it is not in the SP.  I am following up.

    @onovotny – unfortunately the Async CTP does not yet work with the SP.  You will need to stay with the RTM version of VS2010 if you want to use the CTP.  We will do an update at some point to bring these back inline.  Sorry for the inconvience on this.

  21. AlfredBr says:

    I agree that VS2010 is slower than VS2008, but not unbearably so.  

    There is one very aggravating bug in the WinForms editor.  If the designer tab is open and you debug your application using F5, you will not be able to compile/debug again unless you exit and restart VS2010.  VS2010 will complain that your .exe (i.e. your compiled program) is 'in use' and cannot be overwritten.  A check using ProcessMonitor shows that it is VS2010 itself that is locking your executable.  I never experienced this problem until I moved my projects to VS2010.  

    But overall, I am happy with VS2010.

  22. Carel Lotz says:

    To echo Steve's request for fixing the debugging issues.  It makes it very frustrating to debug unit tests with the debugger not honouring break points and jumping at will out of functions will stepping through it.  Here is a connect issue:  connect.microsoft.com/…/556756.

    Also, if with the SL 4 tools now being packaged as part of the SP, do we need to uninstall this first before installing the SP?

  23. Tobias says:

    Good to hear, that there will be improvements.

    [quote]we don't have a formalized bug fix list but we have concentrated heavily on user feedback for this release.[/quote]

    Sorry for being a little sarcastic: But how can you handle this huge product without a fix list? I would expect this of a backyard 2-men software company!

  24. Will says:

    @Jason – Thanks – I sorted out my install problem – from the failed install log, I could see it was something to do with help that was causing the problem.    I tried to uninstall the 'help viewer power tool' from ARP which I'd installed previously, but that gave a manifest error on uninstallation (I suspect this was what was breaking the SP install).

    So I removed it with the MS-Office Windows Installer cleanup tool (you know, the one which is ONLY for Office), deleted all the related files, and then successfully reran the SP install.   So just another MSI problem.  What a surprise.

    Is VS2012 going to be xcopy deploy…?

  25. fatcathu says:

    WHAT ? Still no intelisense for C++/CLI ???

  26. guest says:

    WHAT ? Still no intelisense for C++/CLI ???

  27. KZ says:

    I am waiting for AOP support in VB/C# compilers. Please, implement it as soon as possible

  28. CraigTP says:

    Hi Jason,

    Thanks for the blog post about VS2010 SP1.

    Personally, I'm most interested in support for SQL Server Compact Edition 4.   Scott Guthrie indicated that: "VS 2010 and Visual Web Developer 2010 Express will add SQL CE 4 tooling support for ASP.NET scenarios in an update we’ll be rolling out in the future." in a blog post he did here: http://is.gd/inRUx

    I'm wondering if this tooling support will be part of Visual Studio 2010's Service Pack 1 release (either this beta or the final RTM version).  Also, I'm wondering when SQL Server CE 4 will hit RTM, also?

    Thanks for any info you can provide on this matter.

    -Craig.

  29. Vinod says:

    Does the local help viewer includes the docking facility of index and other other parts which are on the left hand side.. this way we can save screen space and see more help material..

  30. Adi says:

    Any idea if Reporting model (rdl) is now supported?

  31. Jeff Williams says:

    Please tell me they've fixed the "file is being used by another process" for dlls in the obj/Debug.  I love VS2010 except for that one caveat.  It makes it extrememly frustrating to even want to work on WinForms projects.  ASP.NET and Silverlight seem to build fine always.  And Thank You, Thank You, Thank You for awesome Windows Phone 7 tools.  WOW!!!  Now, I've just got to convince my company we need to switch:)

  32. Aidan Ryan says:

    How can I configure a C++/CLI unit test project to target .NET 3.5?

    Thanks.

  33. JH says:

    Great news!

    I'm very interested in a complete change list though.

    Have the out "of memory exceptions" related to copy and paste been fixed for example?

  34. Ryan says:

    I agree with Ash and John Doe about VS2010's slowness and crashiness.  While I don't know what causes the crashes, I can tell that if I do things like closing the current window or closing all windows it's very slow.  Opening files is slow too, especially if I want to open multiple files at once – I may have to wait up to a minute to open ten or less files.  There are a handful of other issues that I'll try to remember.  I would say that overall it's a slower user experience than VS2008.

  35. Pieter says:

    Jason wrote:

    @Pieter – we don't have a full list of changes but it was focused primarily on bug fixing for this release.

    Are you saying; you don't have a complete changelist doc yet, but you will eventually publish one, or you will never publish a changelist, and I have to do code difs to decide what the impact on my product is?

  36. Ryan says:

    I thought of another one…this one is probably the most annoying one for me.  Sometimes when I'm debugging a website, the site hangs.  As soon as I stop debugging the web page will load.

  37. GT says:

    I don’t want to use VS.NET 2010, but since this project is on .NET and it was my idea 2 years ago, I guess there is no choice but to complain here.

    Did you speedup SLOZALEX? (VS.NET)

    About the guy who is saying VS.NET 2010 is smooth and quick, please try it before the medical marihuana 🙂 after it everything in slow motion is pretty fast and colorful 🙂

    WPF is the slowest technology Microsoft ever created, sorry, the second slowest, the first is BizTalk 2004, WCF is slow, just everything there in VS.NET 2010 is slow!.

    I wish Microsoft was like Google, imagine them releasing a new version of WPF every six weeks with an updated and faster .NET framework; oh what am I talking about, that can only be done by Google Chrome!

    The next project will definitely not be in VS.NET 2010. And .Net may not be used at all, welcome Google Chrome, it is a savior!

    Good luck with SLOZALEX!

  38. Keith says:

    I too would like to see some release notes for this product, documenting which (if any) bugs have been fixed.

    I see that MFC bug 535704 is still outstanding, even though the fix is trivial: replace ATLSTATIC_ASSERT with ASSERT in atlcomcli.h.  Preventing the use of the /J compiler flag in this way really is the tail wagging the dog.  Just because template class CVarTypeInfo would be confused if the default char type was unsigned shouldn't cause compilations that don't use that class to fail.  MFC seems to be designed to be robust when faced with unsigned char, so please fix this issue.

  39. FFS says:

    So.Many.Haters 🙁

    Cheers for the heads up, JasonZ. Lets hope the release is a great help to all types of .NET dev's out there.

    Here's to hoping that updates to VS will be smaller and quicker (ala like Google Chrome) in the future 🙂 Lots of small love, more often … than big love once a year.

    @Haters: IMO VS2010 > VS2008 > VS2005. VS2010 + ASP.NET MVC == the win.

  40. Chad says:

    Still no intellisense for C++/CLI? I can't believe it. Tell me you're kidding!

    So you chose a f***ing help viewer over intellisense in C++/CLI?????

    This is like a bad dream.

  41. johnnynine says:

    I'd be happy without the new features if you could just fix the bugs and prevent VS2010 from crashing on me everyday.

  42. Steve Carroll - MSFT says:

    Regarding debugger issues reported in the comments, we believe we have fixed the reported issues in this thread.  That includes the bug where the debugged program continues when you step in the debugger and also the IIS hang.  If you are still seeing these issues after you install the SP beta, please contact me at scarroll -at- microsoft.com and we'd love to get more details on your repro.

  43. Kevin Clark says:

    I attempted to install the SP, but it ended with a "Generic trust failure"

    The log file had the following information

    BlockIf: A compatible version of Visual Studio 2010 was not detected on the system. This update is designed for only the Microsoft Visual Studio 2010.

    Not: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Or: evaluating

    Exists: evaluating

    Exists evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to false

    Exists: evaluating

    Exists evaluated to true

    Or evaluated to true

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to true

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to true

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to true

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to true

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to true

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to true

    Exists: evaluating

    Exists evaluated to false

    Or evaluated to true

    Not evaluated to false

    BlockIf evaluated to false

    Global Block Checks no blocking conditions found

    Applicability for Installing: evaluating each item

    Determining state: of D:SetupUtility.exe

    LessThanOrEqualTo: evaluating

    LessThanOrEqualTo evaluated to false

    Determining state of D:SetupUtility.exe – not applicable

    Determining state: of D:VS10sp1_x86.msi

    Exists: evaluating

    Exists evaluated to true

    Exists: evaluating

    Exists evaluated to false

    Determining state of D:VS10sp1_x86.msi – available but not verified yet

    Determining state: of D:VS10sp1-KB983509.msp

    Microsoft Visual Studio 2010

    Version 10.0.30319.1 RTMRel

    Microsoft .NET Framework

    Version 4.0.30319 RTMRel

    Installed Version: Professional

    Microsoft Office Developer Tools

    Microsoft Office Developer Tools

    Microsoft Visual Basic 2010

    Microsoft Visual Basic 2010

    Microsoft Visual C# 2010

    Microsoft Visual C# 2010

    Microsoft Visual C++ 2010

    Microsoft Visual C++ 2010

    Microsoft Visual F# 2010

    Microsoft Visual F# 2010

    Microsoft Visual Studio 2010 Team Explorer

    Microsoft Visual Studio 2010 Team Explorer

    Microsoft Visual Web Developer 2010

    Microsoft Visual Web Developer 2010

    Crystal Reports Templates for Microsoft Visual Studio 2010  

    Crystal Reports Templates for Microsoft Visual Studio 2010

    Microsoft Visual Studio 2010 SharePoint Developer Tools   10.0.30319

    Microsoft Visual Studio 2010 SharePoint Developer Tools

    Any ideas why this is failing?

    Thanks.

  44. cuterhei says:

    VS2010的确很慢,Crash掉的频率很高(较VS2008),占用的内存也很大,希望SP能够对此有所改进。

    如果不是一定要使用VS的简洁华丽的界面命令,我觉得还是Windows SDK 7.1比较好,就是调试不太方便(习惯了VS的界面操作)。

  45. Suprotim Agarwal says:

    Jason – Since the Color Printing extension is now available for VS 2010, can you guys add it to your to-do list. We want out-of-the-box SourceCode Color Printing support in VS 2010 SP1.

  46. heaths says:

    If you're having problems installing SP1 Beta, please see blogs.msdn.com/…/providing-feedback-on-visual-studio-2010-service-pack-1-beta-installation.aspx for instructions on gathering logs. I'll also be posting solutions and workarounds to common installation issues at http://blogs.msdn.com/heaths.

  47. art says:

    I'm also hoping this silly ATL bug is fixed in VS 2010 SP1:

    social.msdn.microsoft.com/…/42fb42f7-6976-4cd1-a946-833c8eca02bc

  48. Dan Martini says:

    WTF?  I write a relevant comment yesterday and also email you a copy of it and it doesn't get posted and you don't respond to my email?  Yet some yak can fill a page with "Not: evaluating, Or: evaluating, Or: evaluating" dozens of times and that doesn't get sensored.  

    Alow me to try again: Will the Visual Studio 2010 SP1 allow ASP.NET WebForms developers use a HTML5 doctype and write HTML5/CSS3 apps?  I understand, repeat, I understand they are not completed standards, but that's an excuse if anything.  I would like to see the VS IDE support HTML5 and CSS3 to the degree that IE9 will.  Makes sense that I would want to be able to write fully IE9 compatible apps with Visual Stusio 2010 doesn't it?

    If I try to set an input type="email" which may not seem important to anyone, but causes iPhone to render a radically different keyboard, VS 2010 currently complains with an error than "email" is not a valid value for type.  That is just stratching the surface because a complete integrated HTML5 dtd would recognize all of the elements that Modernizr accomodates and compensates for in IE at a minumum.

    The larger point is that HTML5 is important NOW, not tomorrow or next year or the year after but now.  Microsoft has been hammering home how IE9 is going to bridge the gap with modern browsers and that means HTML5 + CSS3 among other things.  So if MS is throwing its weight behind web standards, why can I easily and naturally build standards based, forward thinking web applications in VS 2010, using WebForms.  Please, no hurling MVC at me.  On this planet, MVC has a piddling percentage of the market compared to all of the lines of code written (ant that will be written) in ASP.NET WebForms.  Sure, WebForms itself needs an overhaul and if done so correctly, would make people forget about MVC altogether.  Barring that, how about allowing me to get work down on modern applications?

    I hate the thought of the flagship browser finally hitting it's stride only to have my core development become an also-ran (or worse, an object of derision) because it doesn't allow me to participate fully in modern web application

    development.

    How long will I have to wait for this?

    Thanks,

    Dan Martini

  49. Dan Martini says:

    Never write in an agitated state without edit/undo …

    a) Should be: Makes sense that I would want to be able to write fully IE9 compatible apps with Visual Studio 2010 doesn't it?

    b) Should be: …(and that will be written) in ASP.NET WebForms

    c) Should be: …Barring that, how about allowing me to get work done on modern applications?

    d) Should be: …only to have my core development IDE become an also-ran (or worse, an object of derision) because it doesn't allow me to participate fully in modern web application development.

    The argument still stands.  Please tell me that you guys have already baked this stuff in and just neglected to mention it.

    Dan Martini

  50. PaulShave says:

    Jason – It's rather disappointing that you have concentrated on new features rather than fixing bugs. VS2010 crashes several times a day for me, and recovering wastes a lot of time. I always send off the error reports – do they actually get looked at?

  51. PaulShave says:

    Jason – It's rather disappointing that you have concentrated on new features rather than fixing bugs. VS2010 crashes several times a day for me, and recovering wastes a lot of time. I always send off the error reports – do they actually get looked at?

  52. Chad says:

    The user "FFS" makes a great point: Microsoft (in general) needs to get away from the once-a-year massive updates and needs to be more responsive to the end-user's feedback. Those of us who have been struggling with the VS2010 upgrade have been waiting a long time for an update.

    PM's at M$: You guys can't keep doing the same 'ol update strategy and expect to keep your market share. Apple and Google are going to crush you guys if you don't change your ways. This isn't 1996 any more.

    (Sorry, but I'm extremely frustrated by VS2010's lack of overall quality and this service pack missing key fixes)

  53. setiri says:

    Let me jump in here too – vs2010 is definitely too slow. I coudl run 10 instances of 2008 without issue, but sometimes my 4 gig new laptop struggled with just one 2010. Ive upgraded to 8 gigs ram and it's better now, but… that's pretty drastic?

  54. Michael says:

    How do you uninstall this beta?  Every time I try uninstalling, it asks me to point it to the location of the Installation CD.  VS keeps crashing on exit with this SP1 installed.

  55. jschroedl says:

    I'll be a non-hater. SP1 installed flawlessly and all our projects built fine. The help viewer is a huge improvement.  It also appears that Managed Incremental Linking made it in too and that's welcomed.

    As a C++/CLI dev I'm still disappointed that Intellisense didn't make it but Boris Jabes told us it wouldn't be in SP1.  Will continue use Visual Assist until SP2 or V.next.  

    I turned /INCREMENTAL back on for our mixed mode project – can anyone confirm that incremental linking is supposed to work with mixed mode apps now? I haven't seen a warning yet –fingers are crossed.

    The file locked after a debug session is still not fixed — and the connect issue is "Active". It's a bug in srcsrc.dll which is part of Windows, not VS.connect.microsoft.com/…/vs2010-locks-static-library-after-debug-session

    I too would appreciate a list of changes/fixes but having to put together Release Notes for products, you have to realize that it can be difficult to cull relevant bug fix reports from an internal bug db. so I can cut slack there. I'd rather the bug get fixed than have buracracy of tagging bugs and release notes slow the fixes down.

  56. jschroedl says:

    correction to my comment. It's "srcsrv.dll"

  57. heaths says:

    @Kevin Clark,

    How did you install SP1? Was it from the ISO or from the web downloader? We'll also need logs. Please see blogs.msdn.com/…/providing-feedback-on-visual-studio-2010-service-pack-1-beta-installation.aspx.

  58. Pieter says:

    1 install ok, 1 install fails.

    Create a defect on Connect with logs, defect gets closed as CNR:

    connect.microsoft.com/…/sp1-beta-install-fails-install-i-interactive-error

    What is the point of logging defects if they just get closed?

  59. grumpy says:

    Just installed the SP1 beta, and now help no longer works.

    If I hit F1 from within VS, it opens my browser, points it at 127.0.0.1, and tells me that it couldn't contact the server.

    And I can't find this fancy new help viewer anywhere.

    Am I missing something obvious?

  60. tom_mai78101 says:

    Can anyone confirm that there's a hotfix for local variables not able to be debugged by the debugger in this Service Pack?

  61. Iosu says:

    Is this beta compatible with Azure 1.3 tools??

  62. Richard says:

    Hi Jason,

    please add Intellisense support for managed C++ in the final Service Pack release. I (and I am not the only one) need this urgently. Even if it doesn't work perfect – Intellisense that works correct in only 80% is much better than nothing.

    Richard

  63. cateye says:

    This is un-f**ing-believable. Still no intellisense for C++/CLI! Instead they focus on a help-viewer? Microsoft is really disappointing me here. I have been developing using VS for over 10 years no. This is the first time I seriously consider settling for another non-MS platform. VS2010 has already gone into the annals by being the worst development product of this decade…

  64. bbqchickenrobot says:

    VS.NET 2010 is an awesome product and I'm so happy to have an IDE of this caliber! I couldn't imagine using monodevelop or eclipse day to day! It runs quite fast for me, no crashes and does everything I need it to do. Not sure what these other guys have on their machines or maybe they're still running AMD KII processers =p  In any case, just throwin out some positivity for the product. Only thing I was really anticipating was the round trip UML engineering but it looks like it may not have made it in this time around… oh well, will just have to wait I suppose!  Great work guys!

  65. thewordofb says:

    I don't want to be a hater, but I'm pretty surprised by the list of fixes.  A help viewer?!  Seriously?  I would have assumed the number one fix would be why Intellisense kills your system's performance.  I'm surprised nobody at Microsoft has been able to reproduce this and with the out-cry in the comments I know I'm not alone anymore.  

    We have 140 developers working on various teams specializing in C++/MFC, C#/Winforms, C#/WPF, and Javascript/C#/ASP.NET and we've all found the switch to VS2010 a mistake.  The fact that such disparate teams are all disappointed should show that it's not language specific but some sort of architectual failure.  

    Our solution has been to just out right disable intellisense.  We've noticed the biggest killers are switching between source files, opening files, Go To Definition/Declaration, Scrolling (Yeah, freaking scrolling kills a Core i7), etc.  No matter how we try to tweak intellisense it just kills us.  It rebuilds and rebuilds and rebuilds.  I've seen switching between two open files take 2 minutes.    

  66. Aethec says:

    Is the DrawingContext.DrawText() method now using the new WPF 4 text stack ?

    I reported the bug on the WPF Text blog, and got told it had been reproduced, but I don't know whether it has been fixed (and I don't want to install a beta Service Pack…)

  67. heaths says:

    @Michael, when prompted for source on uninstall you need to have your installation media handy (DVD or mounted ISO). When prompted, find that .msi file on your media and click OK. Some files are needed from the RTM sources when SP1 files are downgraded.

  68. dawmail333 says:

    That VB runtime switch…

    Does that mean we could see VB for XNA?

    *crosses fingers*

  69. Simon says:

    Please fix the horrible *blury* text editor. I hope this version will allow me to use the raster fonts I have been using for 20 years! I have read all the WPF and VS teams blogs posts about it, but it's still awful. I want it to look like VS 2008, period! Today, I still use VS 2008 whenever I can although VS 2010 has some interesting features.

  70. Bill Campbell says:

    Hi,

    I haven't been able to find any info on what you need to uninstall prior to installing SP1. I am developing in Silverlight 4 right now and I installed the SP1 and I no longer get any of my usercontrols displayed. It's almost like the browser plugin is gone. Should we be removing all the previous SL stuff prior to installing SP1? How about feature paks or power tools? Please tell us the order for these things. I just uninstalled VS2008, all the other 2008 things I had installed, all the Silverlight things installed (Toolkit, VS tools, SL sdk and SL runtime). I even uninstalled VS2010 and am starting from scratch installing VS2010 then I'll install SP1. Do I need other things installed for SL4 development? Please share with us how to correctly do this. Please!

    thanks!

    Bill44077

  71. Bill Campbell says:

    Hi,

    Just a quick update: after removing all my VS2008/10 and all associated files including all the Silverlight tools/dll's I reinstalled on VS2010 and then the VS2010 SP1. When I load my solution that includes my silverlight projects it tells me that it can't load them. I know that SP1 is supposed to include the VS Silverlight tools but there is obviously something else that is missing. Could use some instructionn for what is needed. Another thing I noticed is that after installing the SP1 my wireless on my Dell D630 stops working. I noticed that the previous time I installed it. When I remove it, the wireless finds and connects to my default setting. Strange.

    thanks!

    Bill44077

  72. Tim Baigent says:

    The mild illiteracy of this announcement makes me doubt the worth of the Service Pack.

    Can a person who writes English so badly competently oversee such a complex logical framework?

  73. ThomasG says:

    I installed it and i cant open masterpage

  74. Mark Groves says:

    @bbqchickenrobot

    You can find UML Code Generation and Reverse Engineering as part of the Feature Packs  msdn.microsoft.com/…/ff655021.aspx

    Here is the documentation:

    msdn.microsoft.com/…/ff657795.aspx

    msdn.microsoft.com/…/ff657806.aspx

    Thanks,

    Mark

  75. Eugene says:

    Hello Jason,

    I've got a strange issue after upgrading VC#2010 Express with SP1 Beta. Namely, all my breakpoints can't be hit at all – debugger just ignores them! Adding/removing them just has no effect.

    I tried fully rebuilding my projects – switched to release and back to debug… Actually, tried all the stupid tricks I could imagine. No success.

    The situation is reproducible: I've got it at home and at work.

    Maybe it makes some difference… The project is targeted against .NET2.0 for compatibility reasons.

  76. Damian Edwards says:

    @Dan Martini

    We did indeed include initial HTML5 support for the HTML editor in SP1, which you can choose from the HTML Source Editing toolbar or HTML text editor options. It even addresses your specific example regarding <input type="email" />, however ASP.NET Web Forms itself was not updated in any way for HTML5. We also relaxed the validation in the CSS editor to not complain if valid CSS3 selectors are used, although no support for new CSS3 properties was added. We are continuing to work on having great HTML5 and CSS3 support in a future Visual Studio release.

  77. VishalRJoshi says:

    @Joe, The extra line break issue with web.config transformation  connect.microsoft.com/…/web-config-transform-writes-extra-line-break-spaces-to-values-elements-under-applicationsettings-section is fixed in SP1…

    Thanks

    Vishal Joshi

  78. VishalRJoshi says:

    @Joe, The extra line break issue with web.config transformation  connect.microsoft.com/…/web-config-transform-writes-extra-line-break-spaces-to-values-elements-under-applicationsettings-section is fixed in SP1…

    Thanks

    Vishal Joshi

  79. Bill Campbell says:

    Just wanted to let you know that I found out why SL4 stopped working on my machine. After installing VS2010 SP1, my wireless stopped working as well as my webex and SL4. I uninstalled and reinstalled VS2010 and all the SL goodies. Still no luck. But my wireless did come back. I found that re-installing IE8 solved my SL4 problems as well as my webex issues. Weird. Just in case anyone else had these problems…

    thanks!

  80. Rui Sun - MSFT says:

    @Eugene

    We have not been able to reporduce the problem you reported on the breakpoints not getting hit.  This is probably due to us not having all the requisite information based on your description. Please contact me at ruisun -at- microsoft.com and we'd love to get more details on your repro.

    Thanks.

    Rui

  81. Tania says:

    VS2010 is very easy to use and we can also say its user friendly.The process is fast. I too faced an error as John Doe and Ash McConnell said, but not all the times. Only few times. At that i dont know what to do. Anybody can resolve my problem.

    godwinsblog.cdtech.in/…/requested-page-cannot-be-accessed.html

  82. Tom Kirby-Green says:

    Just installed the first beta of Visual Studio 2010 Service Pack 1 and was horrified to see that IntelliSense for C++/CLI is still not available. When is it going to be put back? This is a serious regression over '2008 and a major pain point for software dev in the Financial Services industry.

  83. Tom Kirby-Green says:

    Just installed the first beta of Visual Studio 2010 Service Pack 1 and was horrified to see that IntelliSense for C++/CLI is still not available. When is it going to be put back? This is a serious regression over '2008 and a major pain point for software dev in the Financial Services industry.

  84. Zach says:

    Guys, stop talking about C++/CLI, seriously.

    Despite how obviously frustrating it is, I don't know why you were expecting a *FEATURE* to appear in a *SERVICE PACK*, when there are other things called *FEATURE PACKS*.  Intellisense not working isn't a bug.  Intellisense is a feature that never made it into C++/CLI for 2010.  So while everyone is understandably annoyed about it, it would be great to stop littering all these blog posts with complaints about it, since Service Pack 1, 2, or even 10 was never going to do anything about C++ / CLI intellisense anyway.  

    Post your complaints through the proper channels, or at the very least in the appropriate blog posts.  

  85. Richard says:

    For me, VS2010 doesn't *feel* quite as fast as VS2008, but it's generally not too bad. It's certainly not as bad for me as it seems to be for some of the commenters!

    If it's slow because it's WPF, the answer isn't to rip out WPF and go back to the 90's; it's to fix WPF. If you make WPF faster, VS2010 will be faster, and so will every other WPF application.

    Sure, you could do the same thing in native code if you "stop trying to be lazy", as James suggested. You could also eschew this modern programming language malarkey and stick to machine code. "Real" developers don't cripple their code's performance by using this lazy assembly-language junk; they flip the bits by hand and debug using a torch and a photo-sensitive panel!

  86. Malcolm says:

    Help Viewer Beta feedback is greatly appreciated.  We wish to make the SP1 final release as solid and productive as possible.  To help us resolve issues you see in the Beta, and future feature requests, please log a connect bug providing as much detail as possible.   For collecting SP1 error data, please see blogs.msdn.com/…/providing-feedback-on-visual-studio-2010-service-pack-1-beta-installation.aspx

    Will – Powertool – there is a readme item that may pertain to your issue – not sure as we need more repro information.  In the meantime, take a look at the Help Viewer readme.

    In the Help Readme (C:Program FilesMicrosoft Help Viewerv1.0ReadMe_ENG.htm), under 4.0 Known Issues:

    “8. In Add/Remove Programs, selecting Help repair may cause Help Library Manager to throw an error if the contents store was originally put somewhere other than default. To work around this browse to helplibmanager.exe.config (C:Program FilesMicrosoft Help Viewerv1.0), open helplibmanager.exe.config (in notepad.exe) and change key="FirstTimeRun" value="False" to key="FirstTimeRun" value="True". Next time Help Library Manager is run it will prompt for a folder path to store documents.”

    Grumpy – we really need more repro information in order to determine what is happening.  Please consider logging a Connect bug so that we can take appropriate action.

    Vinod – “the docking facility of index and other parts”  We did capture this for our future work.  

  87. Nick Tompson says:

    I don't know what y'all complaining about – VS2010 is blazingly fast… at least on my machine.

  88. grumpy says:

    @Malcolm: I would, if I was sure it was a bug. But to begin with, I'd just like to know what I should expect, so I can verify that there actually is a problem, and I haven't just gone momentarily blind.

    Where am I supposed to find the new help viewer? What is supposed to happen when I hit F1?

    At the moment, F1 opens my browser, as it did before SP1, but it no longer launches the help agent, so it fails to contact 127.0.0.1. Is there something I should have done to actively enable the new help viewer?

  89. SteveSmith says:

    The sp1 would not install, is there anything that I can do to have it install?

  90. JoelTbay says:

    What a disappointment!  No list of fixes.  Many bugs un-fixed.  No hope of a Service Pack 2 (just like Visual Studio 2008 which is now a hot fix mess!).  

    This development cycle is flawed.  Pumping out version after version of Visual Studio without fixing massive lists of bugs is flawed.  This albatross is becoming so unweildy and complex its at risk of collapsing under its own weight.  

    There should be a Service Pack 2 (at least) for Visual Studio 2008.  There should be similar plans for 2010.  Then, a Service Pack 3.  If this means stopping the relentless pursuit of 2012, then so be it.  If this product is too complex to fix properly before releasing a new version, then something is fundamentally flawed.

  91. Jasonz says:

    Lot's of great feedback and comments here, I'm working to respond to everyone today.  A few to start:

    @AlfredBr – the issue your seeing with F5 locking your image is definitely not something we are seeing.  Can you file a Connect issue for this so we can get repro steps?  thanks

    @Tobias – you are of course correct that we have everything fully tracked (in TFS).  What I generally find is our bug list tends to be noisy as we track everything (internal build breaks, patching changes, EULA updates, readme updates, etc).  I think what you really want is the core set of issue fixes which we have not (yet) scrubbed out of the bigger list.  I’m working with the team to produce this, stay tuned…

    @Will – glad to hear that you were able to resolve the issue.  I always want to make setup easier.  A key issue for us is VS is built on .NET which means we are usually updating the framework install as well.  As a Windows component, that cannot be xcopy installed.

    @WalkingCat, guest, et al – Unfortunately the SP does not contain support for C++/CLI Intellisense.  I can tell you the team has internalized this feedback loud and clear and is looking at what it can do.  Without boring you with too many details, the work here requires major changes to the front end of the compiler that is used in the IDE (a different code base than that used for actual code generation).  So it is not a trivial piece of engineering work.  But we hear your feedback on this and the team is looking at what they can do in a future release.

    @KZ – I’m actually not a huge fan of AOP.  Its advantage is giving you a way to apply semantics to large bodies of code.  The downside is unintended side effects in call graphs and the removal of imperative knowledge for the developer.  I think the usage of custom attributes in .NET gives you a lot of this kind of support without the potential gotchas.  I’m always happy to discuss philosophies on this, but right now we don’t have plans to add any AOP style features.

    @Vinod – the local help viewer has been designed to add the bulk of the core features that were present in VS2008.  Please do give it a try and let us know what you think!

    @Jeff Williams – glad to hear things are going well with the Windows Phone 7 work; I’ve written several apps myself and it’s a ton of fun.  On the Winforms issue I’m definitely interested in hearing your repro scenario.  Do you have a Connect bug on this?

    @JH – the copy / paste bug was actually fixed in a QFE release a while back.  Check out this post for a pointer:  blogs.msdn.com/…/visual-studio-2010-survey-results.aspx  As I mention above we’re looking at publishing more stuff on the release

    @Ryan – thanks for the feedback on the release.  I’m definitely interested in hearing your perf feedback.  In particular understanding machine configs, size of files, etc is an important part of diagnosing perf.  Please do feel free to contact me directly.  Thanks!

    @Tim – my wife majored in English Lit, I majored in computer science.  Fortunately I am well versed in a number of programming languages.

  92. Tarek Madkour [Microsoft] says:

    I wanted to quickly follow up regarding the comments on C++/CLI IntelliSense.

    @WalkingCat, Chad, jschroedl, Richard, cateye, Tom Kirby-Green and others who really wanted to see C++/CLI IntelliSense added back to Visual Studio as soon as possible: I wanted to assure you that we hear you and that we understand your pain. This is very important feedback for us that we are indeed already using to shape our product plans and execution. It was very unfortunate that this work could not fit in SP1. We will make sure to communicate our plans for C++/CLI IntelliSense once we have finalized them so stay tuned.

    Tarek Madkour

    Lead Program Manager

    Visual C++ Team

  93. Damian Edwards says:

    @CraigTP

    SP1 includes changes that are required to support tooling for SQL Server Compact 4.0. To get this support you need SP1, the SQLCE4 runtime and the VS tooling, i.e.:

    * Visual Studio 2010 Service Pack 1 Beta

    * SQL Server Compact 4.0 CTP2 – http://www.microsoft.com/…/install.aspx

    * Visual Studio 2010 SP1 Tools for SQL Server Compact 4.0 CTP2 – http://www.microsoft.com/…/install.aspx

    If you want support for generating SQL scripts from SQLCE4 databases during deployment using Web Deploy, you'll need Web Deploy 2.0 Beta 3 as well – http://www.microsoft.com/…/install.aspx. Once you install Web Deploy 2.0 Beta 3, VS SP1 will automatically start using it.

    Hope this gives you the information you need.

    Damian Edwards

    Program Manager

    Visual Studio Web Tooling

  94. cash cow? says:

    I agree with JoelTbay.

    VS 2008 should have SP2.

    VS 2010 should have SP2.

    It's absolutely ridicules how much developers pay for a release of VS, only to have a small-ish # of bugs fixed in SP1, … then be forced to Upgrade to newer version a couple years later and repeat the purchasing process.  Is V$ a sacrificial money-cow?

    Why did VS 6 get so many SPs … then VS 2003, 2005, 2008 and (I can only assume 2010) only have 1??   The only correlation I can see is upper management’s eyes shifted to more dough about the time .NET came about.

  95. malcolm5 says:

    @grumpy – The fact that the agent is not running in your sys tray is concerning – it needs to be to have Help content displayed correctly.  I want to take this offline to see what is going on.  Please email us at hlpfdbk@microsoft.com so that we can get more details to try to resolve this with you.  In the meantime, to manually start the agent, go to the Help application folder, Program FilesMicrosoft Help Viewerv1.0, and double click HelpLibAgent.exe.  That should kick-start the Agent (if it doesn’t, then we have other issues to uncover).  Then, in the IDE, in the Help drop down, select Manage Help Settings, which will launch the Help Library Manager.  From there, select Settings (top right corner of Help Library Manager UI) and then make sure you have “I want to use local help” selected.  Given the local host IP address, looks like that is so, just want to verify.  Then, if you haven’t already, please install some local Help content.  In Help Library Manager, you can install content from online.

    Malcolm

  96. malcolm5 says:

    @grumpy – The fact that the agent is not running in your sys tray is concerning – it needs to be to have Help content displayed correctly.  I want to take this offline to see what is going on.  Please email us at hlpfdbk@microsoft.com so that we can get more details to try to resolve this with you.  In the meantime, to manually start the agent, go to the Help application folder, Program FilesMicrosoft Help Viewerv1.0, and double click HelpLibAgent.exe.  That should kick-start the Agent (if it doesn’t, then we have other issues to uncover).  Then, in the IDE, in the Help drop down, select Manage Help Settings, which will launch the Help Library Manager.  From there, select Settings (top right corner of Help Library Manager UI) and then make sure you have “I want to use local help” selected.  Given the local host IP address, looks like that is so, just want to verify.  Then, if you haven’t already, please install some local Help content.  In Help Library Manager, you can install content from online.

    Malcolm

  97. Jasonz says:

    @Pieter – we are working on publishing a list of changes.  As I mentioned previously I want to scrub out the noise (EULA changes, readme, internal stuff) that we typically track in the overall issues list.

    @Ryan – have you file a Connect issue for the behavior you are seeing?

    @GT – we are always looking for performance feedback.  You can send your specific issues to vsperf@microsoft.com.  Knowing your machine config, project types / sizes, and specific issues is very helpful.

    @johnnynine – the SP does contain a number of bug fixes for reported crash behavior.  Please give it a try and let me know if you are still hitting issues.

    @Kevin Clark – Heath posted some instructions on how to collect setup logs and submit them.  Can you give that a try and let us know?  Thanks!

    @PaulShave – we’ve actually focused almost exclusively on bug fixing for this release (we’re working on posting the list).  Features were really not the priority for this release (in stark contrast to VS2008 SP1).

    @Chad – sorry to hear you are frustrated with the overall release.  If you can point us to the Connect issues that are blocking you we can take a look.

    @setiri – I’m definitely interested in hearing more about your machine config, project types, and issues you are seeing.  We are monitoring issues at vsperf@microsoft.com.

    @jschroedl – thanks for the feedback.  The C++ team is definitely heard the feedback on intellisense and is working on a plan.  I’m checking on your connect issue.  We are planning to post a scrubbed bug list soon.

    @thewordofb – what you are seeing is not expected and does not match our perf testing.  I’d be very interested in hearing from you directly on this so we can diagnose what is wrong.  Can you mail your contact info to vsperf@microsoft.com?  Thanks!

    @dawmail333 – it is our strategy to keep C# and VB in sync with each other.  We now have VB working successfully on Windows Phone and I would like to see it for XNA.  Please stay tuned…

    @Simon – most often when we see this kind of issue it has to do with video cards / drivers.  Have you tried changing to software rendering in Tools, Options, Environment, Visual Experience?

    @SteveSmith – Heath posted some answers on install issues.  If you can collect / send the log to us we can help investigate

  98. Jasonz says:

    @Suprotim Agarwal – I checked the team on color printing and it will not be part of SP1.  This is primarily a timing issue; we want to have more bake time on the code.  In the meanwhile you will always be able to use it as an extension for VS2010 and we will put it in v-next.

  99. Chad says:

    @JasonZ: Thanks, I've already submitted my feedback on the connect site over the course of several months after deciding to take the plunge from 2008. Most of the issues were closed as "cannot reproduce" — now I know how QA feels when I do that to them 🙂

    I've been using Visual Studio (and previous versions of Visual C++) for the better part of 13 years now and VS2010 is the first time I've noticed obvious bugs and missing features. I certainly will do a better job next time testing the water before jumping in.

    I feel bad for the poor folks in the trenches trying to ship this thing. I can only imagine what kind of death march the VS2010 project must have been.

  100. Asesh says:

    What about performance improvements? The move to WPF was a big mistake, now VS 2010 is just like Vista–SLOW. Please fix it

  101. VSTS Quality Tools says:

    @Aidan Ryan: We have posted a blog on how to configure C++/CLI unittest project in SP1 to target .Net fwk 3.5.

    blogs.msdn.com/…/how-to-re-target-unit-tests-to-net-framework-3-5-in-vs-2010-sp1.aspx

    It also covers steps required for configuring C#/VB.Net unit-test projects. Please give the feature a try and let us know your feedback.

    Thanks,

    Abhishek Agrawal, Program Manager, Visual Studio

  102. Jeff Williams says:

    Thanks for your reply.  I have just entered a connect bug regarding the issue (ID#632829).

  103. Alex Thaman (MSFT) says:

    @Keith, re:Using /J with ATL/MFC

    As you know this scenario in general is not supported.  There is a KB article about this here:  support.microsoft.com/…/813540.

    That said you do have a valid point about the experience not being friendly if you are not using the types that we are trying to prevent from being used with /J.  We don't plan to fix this for SP1 but we will go ahead and take a look at this for a future release, possibly just warning in the face of /J.

    Thanks!

    Alex Thaman

    Senior Test Lead

    Visual C++ Team

  104. Shaun says:

    Please, please, please fix issues with service references updating slowly in VS2010 w/ TFS integrated.  It takes 10 minutes to update a service contract.

  105. XiaoyingGuo says:

    Hi Shaun,

    Could you please let me know more details about the issue you encountered? What is your service contract looks like, where is it from and what does it contain? It would be great if you could provide me with a repro sample. You can contact me through xiaoying @microsoft.com

    Thanks,

    Xiaoying Guo

    Program Manager, Visual Studio Business Applications Tooling

  106. Norman Mackay says:

    Is there any feedback if you intend to add Jarek Kowalski's Entity Framework caching provider into SP1 with caching support for stored procedures ?

    We're currently evaluating whether to go with winforms or WPF, WPF more likely. The biggest question mark is entity framework and it's lack of caching and especially stored procedure caching. Our LOB system uses a lot of stored procs and they aren't going to be re-written in a hurry so we need to data access layer with good stored proc support, LINQ would have been the way to go but MS suddenly dropped it/rolled it into EF. We'd rather use a MS data access layer for obvious reasons but EF gives us a lot of question marks and we need to decide soon.

    VS2010 has problems with debugging and some odd quirks but for WPF dev it's much better than 2008, I designed a hotel TV system in VS2008 & WPF and it was a pretty painful process. I usually have three instances open with no issues (3GB ram), it is a bit more clunkly but it will get better I'm sure.

    Any update on whats in SP1 regarding entity framework and some info on where entity framework is going would be great, it's hard to get a clear picture of where MS is going sometimes with Visual Studio….and I've been using it since VB3.

  107. Dat says:

    Hi,

        If you are upgrading to SP1 Beta and are experiencing problems and looking for support we are available to help.  Please follow this link to register:

    blogs.msdn.com/…/going-live-with-the-visual-studio-2010-service-pack-1-beta.aspx

    *.Dat

    Microsoft Developer Support