File size

Here, Visual Studio General Manager Jason Zander sits down with us to discuss how the Visual Studio engineering team addressed your Beta 2 feedback and made some helpful updatesto the Visual Studio 2010 Release Candidate. Jason even demos some of the improvements made in the VS 2010 RC — and on quite a modest PC.

Jason and his team went to great lengths to improve the overall experience of writing applications inside VS 2010. Performance. Performance. Performance... Of course, Jason and team want you to have the final word regarding whether the updates hit the mark,so please download the RC and take it for a test drive. Your feedback is critical to the VS team and they thank you, as always.

Awesome. I have wanted to love Dev 10, but the IDE perf and stability of Beta 2 kept getting in the way, then Windows 7 came along and set the standard for beautiful software with wonderful performance. So I've been really looking forward to this RC and
hope it's the build that finally lets me uninstall Visual Studio 2008 - at least on my box at home. Kudos to the teams involved for all their hard work.

[Updated. Big thank you to Rico and the rest of the VS team, the performance of the RC is sweet. Visual Studio 2008 came
off my laptop this morning and '2010 is my default, go-to, dev tool. Windows 7 + Visual Studio 2010, life is good!]

PerfectPhase"This is not war, this is pest control!" - Dalek to Cyberman

Or rather, does anyone know if the current Silverlight 4 beta bits will work with the new Visual Studio 2010 RC? I'd heard from someone inside MS that they didn't work with some of the interim builds, and about all I'm doing these days is Silverlight 4,
so it'd be nice to know before I uninstall Beta 2.

ScottGu tweeted: "Support for Silverlight 4 with the VS 2010 RC will show up with next public SL4 drop (and so is not yet enabled with today's bits)". Next obvious question: "When will the Silverlight 4 bits get refreshed?"

On the whole Silverlight 4 / .NET 4 front there is the Expression Blend 4 preview. This has been designed to work against Visual Studio 2010 Beta 2 - not sure if it's good for the RC. Charles, do you know?

Does anyone have the inside scoop on when we will see the next SL4 drop that works with this RC0? I cannot imagine people using VS candidates and betas for much else than playing around web development, and maybe some entity framework stuff. And now the
RC does not support that? Strange days.

Currently all new Greenfields web development is in limbo. Migrating a proper (RIA,PRISM,MEF,CLOG,) SL3 app from 2008 to SL4 2010 is going to be very nightmarish. At least it was so for me with VS 2010 Beta 2 + SL4... to many changes. Multi-targetting between
SL3 & SL4 in the beta was a proper disaster.

Therefore I am stuck in development limbo, lying to the authorities and developing my new WEB apps in vs2010 beta 2 + SL4 hoping that when the WEB site is supposed to go live, M$ has released at least a GO LIVE on SL4. If not I am in big trouble.

I'd guess sometime around March 15th (Mix) would be a likely time for the next SL4 drop unless MS has SL-related plans for Mobile World Congress. Even if they do, I'd expect only an announcement there with code following at Mix.

The only thing I am not really happy with is the Add Reference dialog that is mentioned in the video... true, the window now appears immediately, so the UI
feels snappier, but since the list is left accessible while it is being populated and there is no definite visual clue indicating when it's done, I found myself trying to navigate it too early. The resulting experience can be described as trying to
grab a bar of soap in a bathtub...

it looks like something is broken here. In Beta 2, dynamic anonymous types passed between assemblies worked fine, in this version I get a RuntimeBindingException. Even though I am able to use reflection to access the properties, they are unavailable
through the dynamic keyword. Is this new behaviour or a bug?

I think this must be a feature of some kind, or an edge case I just missed. I could have sworn that I used this without having to do anything else to get it to work. As it stands, it seems that the called assembly must grant the caller Internal visibility
for the dynamic magic to now work. Since standard reflection continues to function I must assume this is some type of implementation detail related to how dynamic now works.

Remove this comment

Remove this thread

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums, or
Contact Us and let us know.