bharry's WebLog

Visual Studio Testing Tools Roadshow in Chicago and Milwaulkee

bharry — Tue, 08 Dec 2009 12:44:52 GMT

Angela Dugan (Binkowsky), a friend of mine in the field, asked that I help her advertise a roadshow she is doing. Here’s what she had to say about it:

Visual Studio Testing Tools Roadshow and Deep Dive

Ram Cherala, Principal Program Manager in the Visual Studio Test Tools Business, will be visiting the Midwest District to provide a deeper dive into the innovative new capabilities being introduced in Visual Studio 2010 Ultimate, Visual Studio Test Elements and Test and Lab Management products.

These sessions are targeted toward Developers, Architects, and Quality Assurance teams. Attendees will be given the unique opportunity to have a first glimpse into the products and interact directly with the Redmond team responsible for designing and delivering these products to the market. We will cover a broad range of important topics including Software Quality Assurance, historical debugging, manual test runner, test impact analysis and test lab management.

Agenda:

8:30am – 9:00am................. Introductions and Continental Breakfast

9:00am – 10:30am............... VS 2010 ALM Tools: Walkthrough of All New Features

10:30am – 11:30am............. 2010 MSDN and Licensing Updates

11:30pm – 12:00pm............. Lunch (provided by Microsoft)

12:00pm – 2:00pm............... Deep Dive and Demos of VS 2010 Quality Assurance Features (Coded UI Testing, Manual Test Runner, Lab Management, etc)

2:00pm – 2:15pm................. Break

2:15pm – 4:00pm................. Quality Assurance Tools: Migration and Integration Options

4:00pm – 4:30pm................. Feedback, Book Raffle & Zune Giveaway

This is a FREE event – Register now to reserve your seat!

Date	Location	Register
Milwaukee Monday, December 14, 2009	N19 W24133 Riverwood Drive, Suite 150 Waukesha, WI 53188	Register Here
Chicago (Downers Grove) Wednesday, December 16, 2009	Neudesic 377 E. Butterfield Road Suite 440 Lombard, IL 60148	Register Here
Chicago Thursday, December 17, 2009	Microsoft Office Aon Center Office 200 East Randolph Drive, Suite 200 Chicago, IL 60601	Register Here

	Ram Cherala is the Principal Program Manager in the Visual Studio Test Tools Business, which is part of the Developer Division at Microsoft. Ram is very passionate about building a well-integrated set of tools and technologies that enable developers build, test and ship quality software.

Book raffle and Zune Give-a-way

One random attendee will be selected to receive a brand new Zune HD!

Some WPF Designer Performance Improvements

bharry — Tue, 08 Dec 2009 00:35:00 GMT

We've heard loud and clear that the WPF designer performance in Beta 2 was unacceptable. Well, in a good kind of way, we knew that before we shipped Beta 2. This was one case where our performance tests were telling us the right thing. We discovered some issues late in the Beta 2 cycle (partially a regression, I think) and didn't have time to fully test a solution to address the performance issues. We did code it up and include it in the Beta but you have to use a registry key to enable it. Here's thread on it if you want to give it a try:

http://social.msdn.microsoft.com/Forums/en-US/vswpfdesigner/thread/4511d43f-c134-4329-a970-e374252a620e

This change will often address slowness and random pauses in the WPF designer. It's not the only cause but we've found most people who try it see good results. We've since had time to finish it and it is on permanently from here on out.

Today I saw some perfmon graphs that demonstrate how WPF designer overhead is improving over time.

This first graph is from Beta 2 without the reg key flipped. The very first spike is the CPU hit to open a C# file. the rest is the CPU hit to open an empty XAML file.

Here's the state with the reg key flipped. Don't be suprised that the reg key didn't make a huge difference in this scenario. It makes a much bigger difference in other scenarios.

And here's the current graph for the same thing with current bits. As you can see, it continued to improve.

Brian

WPF TreeView performance tip

bharry — Mon, 07 Dec 2009 19:42:00 GMT

Another of the many performance issues we hit (trust me not all of them were WPF related, it just so happens that the first two I've blogged about were)...

http://blogs.msdn.com/permanenttan/archive/2009/11/20/wpf-treeview-memory-consumption-and-performance.aspx

We hit this in the tree view you use to select which branches you want to visualize change for. A 108MB savings (on an admittedly artificially large data set), not bad :)

Brian

Team System Web Access 2008 Scalability Update Released

bharry — Mon, 07 Dec 2009 17:47:00 GMT

While we're talking about perf...

Over the past year we've heard increasing complaints from customers about the scalability of the Team System Web Access Power Tool as more and more people try to use it. The problem is usually manifested as frequent application recycles (you can see if it's hitting you by looking in your event log). We've done a bunch of work in the 2010 release (where we've integrated Web Access into TFS) to improve performance and scalability.

Back in August, our leadership team met to make the hard call on whether to update the 2008 Web Access Power Tool or to just wait for people to upgrade to 2010 to get the fixes. After much debate, we decided that the issues were serious enough that it was worth back porting the fixes and releasing an update - particularly since many customers will not upgrade to 2010 right away.

It took a while to back port, test and customer validate the changes but, today, we released two updates (one a QFE for the TFS object model and the other a new version of the Team System Web Access Power Tool) that should significantly improve the scalability. Most of the issues fixed had to do with memory over allocation or leaking that resulted in memory exhaustion and process recycling.

You can get the updates here:

· KB974402 - QFE for TFS Object Model Assemblies

· TSWA 2008 – Updated TSWA 2008 SP1 Release (full install, you need to uninstall your existing TSWA 2008 instance first)

And you can read a bit more about it on Hakan's blog:

http://blogs.msdn.com/hakane/archive/2009/12/07/team-system-web-access-2008-sp1-scalability-update.aspx

Your mileage with this will vary but to give you some context, it had gotten to the point where our heavily used dogfood server was recycling about once an hour. With the fixes provided here, we are now seeing recycles every 29 hours (which is what the IIS app pool is set to recycle at by default) - so, in other words, pretty much no recycles due to memory consumption issues.

Brian

The first of many performance discoveries

bharry — Mon, 07 Dec 2009 15:47:00 GMT

Along with painting the big picture of our performance efforts I'd like to share a few specific things we've learned along the way. The first is hosting a WPF window inside a Windows Forms Window.

We've spent a lot of time looking at memory usage over the past several months and one of the things that we saw was that some tool windows were causing surprising growth in memory usage. We tracked the problem down to hosting a WPF control inside a WinForms window wrapper. I'm particularly close to this one because the issue was discovered by the TFS team. We've done some cool visualizations in this release (like branch hierarchy and merge visualization, etc) and we chose to use WPF to create them to get really nice looking images. We found that we had 3 tool windows in version control alone that used this. I know there are others. Once we shared the learning with the rest of the division, I heard anecdotal reports from other areas of the product but I never did a full tally.

The situation is this...

WPF can not render natively into a Windows Forms window. Instead it renders into memory and "bitblts" it into the WinForms window. We observed that, in our VS tool windows, there was about a 20MB memory cost for each tool window to do this. Further we saw transient incremental memory allocation as the tool windows were resized of about 4MB per resize (although it was garbage and the GC would eventually reclaim it).

We have solved the problem by eliminating the intermediate WinForms wrapper windows in the WPF tool window chain (VS now provides a native WPF root level tool window).

This change has saved dozens of megabytes in some VS scenarios and is something you should be thoughtful about as you look at extending Windows Forms applications with new WPF components.

Brian

Shipping a great release

bharry — Mon, 07 Dec 2009 12:33:00 GMT

I've seen a number of comments here (and elsewhere) about VS 2010 being another "Vista". We are very aware how weakness in a few key areas (like performance) can cast a pall over an entire product. As I said in the original post, we are committed to shipping a great release (in all respects).

David mentioned in a comment on my last post that we are taking "risky fixes" later in the product cycle than we usually would. David's right but I'd like to add a little color to this. We normally think of Beta 2 as our "validation" pre-release. We are looking for customers to confirm or deny that we are about ready to ship. We have tons of feedback opportunities before Beta 2 (CTPs, Beta1, more CTPs, TAP customers, dogfooding, etc) to try to make sure we are in a position for customers to say "yes".

This time they did not. As a result, several things have happened:
We have spun up an effort to reach out to every customer (external and internal) who said no to understand why and try try out fixes.
We have assessed (and will continue to) why our metrics were telling us one thing and our customers another.
We have reset many of our scenarios, metrics and goals to better align with the feedback. As importantly we've communicated to the division that "this is not good enough".
We have redoubled our effort on performance investigations and fixes. We've made some pretty substantial improvements.
We have adjusted the end game schedule to allow for more performance improvements while maintaining a high quality bar for the final release.
We are working on adding another widely available pre-release after the first of the year to give us another round of readiness feedback from customers.

We're committed to making it great. I'm not saying noone will flame us over something - of course they will. That happens pretty much no matter what we do. But we will make sure the vast majority of people are very happy with the release.

Thanks,

Brian

Anatomy of a Performance Problem

bharry — Sat, 05 Dec 2009 13:00:00 GMT

You've seen me write a fair amount recently about the VS 2010 Beta 2 performance problems - well, you're going to see me keep writing about them :) We've had enough time, at this point, to understand the feedback and characterize the problem - I'd like to share it with you in hopes of you understanding it and perhaps learning something that can help you avoid the same issue in the future.

The irony of the whole thing is that in this product cycle, we had a bigger concerted focus across the division on performance than we had ever had before. From the very beginning we focused on defining scenarios, goals, regression tests, etc. We went into this product cycle knowing that performance was going to be a challenge. The adoption of WPF for some of our UI elements and a new editor certainly were among the highlights of features likely to lead to issues. We wanted to head off performance problems from the start.

As I look back, there were many things that lead to the situation that we currently find ourselves in. However, if I were to pick one that was the most impactful, I'd say it was the way we measured and goaled performance.

Prior to this release, our performance efforts were hindered by regressions and unreliability of measurements. We set out this product cycle to fix that problem by having every team create a clear list of scenarios and automated tests to measure them (TFS, for instance, has about 150). We focused on making sure the tests were repeatable and had very small standard deviations so that if a test showed a significantly different time than expected, we had a strong reason to believe there was an actual regression to investigate. We set up automated suites that would run some of the tests on virtually every checkin, some every day and some every week. We call the effort RPS (or Regression Prevention System). It was to be our canary in the coal mine.

Clearly it didn't work as well as we had hoped. Why? My analysis is this... It order to get a very reliable, very repeatable set of regression tests, we had to spend a lot of time refining the tests (almost the whole product cycle). We iteratively removed randomization and focused the tests so that we got consistent runs every time. The result is a set of very precise tests that test individual features very well. The problem? No one actually uses the product one very isolated feature at a time. The reality is when you load up a real world application, you have 5 editor windows open, 3 forms designers an architectural diagram, you've just finished debugging and you now hit "Go to definition" on a symbol - it's totally different than what we were testing. I learned 2 things from this exercise about how to ensure your performance testing is measuring the "real world":

You must use a "real" dataset - We must have realistic solutions with a realistic mix of projects, realistically complex artifacts (like forms or architecture diagrams).
You must use a "real" usage pattern - We can't start up the IDE, test one thing and shut it back down. We must measure in the context of an appropriate amount of data/context loaded and we must do it within the context of a normal user session (for example, we might run a debug session and then test how fast the form designer is).

So you might ask, don't you use the product? Why are you just relying on these "microbenchmarks". Yes, we do use the product. After we started getting the Beta 2 feedback about performance, we did a survey of internal users (just within DevDiv) on satisfaction with the Beta and ship readiness. 70% of respondents said they were dissatisfied with VS performance (that's more than twice than the 30% of external respondents who said the same thing). So we had the data that it wasn't good enough but we weren't listening to it. Why? I think we made up all kinds of stories. We said it was "long memory" - people's impressions were tainted by the performance of Beta 1. We said it was taint from their development environment (most devs actually use components that they build themselves - not just ones from the official build lab; after all, we do build the IDE :)). We said it was lag - all the great performance improvements we were working on just hadn't made it into all of the branches yet, etc. etc.

Clearly a learning to be had there too.

There are many other issues too, including:

1) Performance hardware - We didn't do a great job ensuring that we were validating on an appropriately wide range of hardware. For example, we weren't looking at netbooks at all and if you look at my intellisense videos from yesterday, you can see that Beta 2 netbook performance was abysmal. There were other hardware related issues - for example, we found that WPF hardware accelerated performance varies dramatically depending on the quality of the video card and is sometimes slower than software rendering.

2) Carving out room for new technologies - Anytime you add something it's likely to take more resources. You have to figure out how to make room for it. We did not do a good job of this in this release. In Windows 7, the Windows team had some really good practices around this. For instance, there was a rule that if you are going to add anything to boot (CPU, Disk, Memory, etc) you must find enough savings elsewhere to pay for it before you are allowed to check in. There was a strict "no-growth" rule in key scenarios. Definitely a practice that we'll be looking at.

3) Coordination across the division - In all aspects of our work we struggle with the tension between letting individual product units run their own business and coordinating efforts centrally across the division. It's clear to me that in this release coordination was not good enough but it's very tough balance. We'll be spending some real time thinking about this in the next release.

4) I'm sure there are more we'll learn as we continue to reflect on this product cycle. In the meantime, we will continue working to ensure a top quality product when we ship.

So what do we know about the performance issues we are having? We've categorized them as follows:

Virtual Memory Exhaustion - Large solutions and lots of feature usage are causing virtual memory (you've got 2GB on a 32-bit OS) to fill up and for VS to become unstable and crash. It's not exactly a performance problem because it doesn't generally cause VS to slow down, however we treat it as one because it's a resource exhaustion problem and many of the things you do to address it also improve actual memory usage and therefore improve performance too.

Leaks - Allocation and retention of memory that is never used again and accumulates over time. It ultimately leads to Virtual Memory Exhaustion but can also cause working set and other issues due to heap fragmentation that keeps the unwanted memory in the workingset. I also like to separate this out because the way I think about it is different. With Virtual Memory, you are balancing trade-offs and it's an optimization problem. With Leaks, it's a zero tolerance policy. No leaks are acceptable in any circumstance. The way you test for them is different, etc. Beta 2 had a LOT of leaks.

Performance - Specific scenarios where the application doesn't perform according to user expectations. This can be due to any bottlenecked resource (CPU, memory bandwidth, network bandwidth, disk I/O, etc). The two most common underlying causes are innefficient algorithms (too much CPU usage) and too large a working set (more memory used than the physical RAM can accomodate, resulting in thrashing pages in and out to the disk). Based on the feedback, we've identified a number of areas of common performance complaints, including Editing/Intellisense, WPF Designer, Debugger, and Project Load.

Yesterday, I blogged about performance gains in editing/intellisense (including before and after videos). Over the next few weeks, I hope to do a post every couple of days on our efforts and the results of our performance work. Stay tuned and hopefully it will be both entertaining and informative. Since Beta 2, we have had some tremendous improvements and I'm confident we're going to ship with good performance and high customer satisfaction, but it has certainly been a bit of a call to action for us.

Brian

Lab Management in VS 2010

bharry — Sat, 05 Dec 2009 12:18:00 GMT

One of the coolest new capabilities in 2010 is "Lab Management". It enables you to automate the setup and configuration of test environments, saving you a bunch of time doing it every time you have a new build you want to test. We first released it in Beta 1, but the truth is it's a V1 product and it just wasn't really ready enough for a lot of people to be successful getting it up and running - installing and configuring it was too complicated.

We've done a ton of work over the past 7 months or so to make it much easier to get up and going, easier to diagnose when there are issues and more reliable when you use it. While what we shipped in Beta 2 isn't done, we believe that most people should be able to get started and see the value of it.

An important part of our release cycle is soliciting feedback from you to know when we are ready to ship. We've gotten a lot of feedback on Beta 2 - particularly on performance as you can see from other posts I'm writing :). We don't feel like we've gotten enough feedback on lab management to be able to tell. We need your help. We've put together a 4 part blog series that covers everything you need to know to get started with Lab Management. I know I'm asking a lot - it requires significant hardware and several hours of time investment, but I really believe if you get it up and working and figure out how to integrate it into your development cycle, it will be a big time saver for you in the long run. If you can, I'd really appreciate you giving it a try. Here are links to the series.

Part 1: Install

http://blogs.msdn.com/lab_management/archive/2009/11/18/Getting-started-with-Lab-Management-_2800_Part-1_2900_.aspx

Part 2: Configure TFS, build controller, test controller

http://blogs.msdn.com/lab_management/archive/2009/11/18/getting-started-with-lab-management-part-2.aspx

Part 3: Configure system under test – unit testing with a calculator app. Create LE, configure test settings, etc.

http://blogs.msdn.com/lab_management/archive/2009/11/20/getting-started-with-lab-management-part-3.aspx

Part 4: Stitch all the pieces together to create the E2E workflow.

http://blogs.msdn.com/lab_management/archive/2009/11/23/getting-started-with-lab-management-part-4.aspx

Looking forward to hearing from you...

Thanks,

Brian

Improvements in Intellisense post Beta 2

bharry — Fri, 04 Dec 2009 13:03:46 GMT

I’ve written a couple of posts in the last month or so soliciting performance feedback from you all and talking about our performance efforts. Since we realized the degree of performance problem that we still had, we have spent a ton of effort working on understanding it and making it better.

Just yesterday, we made available a build we’re calling “SLCTP1” (Super Limited Community Technology Preview 1 :)). That build is only available under NDA and is only being provided to customers who have reported specific performance issues and worked with us to narrow them down so that we could improve them. We’ll be doing another SLCTP build in a couple of weeks, followed by a more generally available preview in the new year. We are serious about addressing your concerns and ensuring that VS2010 is the best version of VS we have ever shipped in almost every respect.

One of the areas we’ve gotten a lot of feedback on is intellisense performance. We’ve made a ton of improvements. Below, I’ve included some before and after videos running on a Netbook. The first video approximates the typing performance in Beta 2 and the second is what we are seeing today (with all of the fixes that we have made).

Now I have to say, I have some trepidation in posting these. When I looked at these videos myself, I thought – How could we have possibly shipped Beta 2 this way? And, The current is WAY better but I still wouldn’t call it great yet. The first thing I will observe is that I have a number of other videos on less constrained hardware where the difference is MUCH harder to see (because Beta 2 wasn’t nearly so bad). I’ve posted this one precisely because it highlights how much difference we have made. Clearly we had some serious CPU bottlenecks in Beta 2 that didn’t show up on high end dev machines but did on under powered net books. Part of what we learned from Beta 2 was that testing on our pristine, relatively new, test machines in our lab was not a very realistic reflection of what customers would see. We’re addressing that.

Here they are as I grimace :(

We’re not done. We have a lot more work in the queue to make performance even better but I wanted to share with you some of the great progress we have made.

Brian

Quest releases a public Beta of Oracle integration

bharry — Fri, 04 Dec 2009 12:15:00 GMT

Quest software has been working on a provider to enable the Visual Studio database tools to work with Oracle databases (refactorying, deployment, testing, analysis, etc). They've just released a public Beta that you can try out with the VS 2010 Beta 2. Read more about it and download the Beta. You can also check out a video demonstration of the capabilities. In it they cover creating a new Oracle database project, importing your schema, managing and altering objects, comparing your changes to the live schema and deploying them back to the database.

Check it out!

Brian

Initial TFS 2010 BPA Tool Available

bharry — Wed, 02 Dec 2009 12:18:29 GMT

We’ve also just released the first cut at the TFS 2010 Best Practices Analyzer that will help you diagnose configuration issues on TFS 2010 servers. It’s a long way from being done – we’ll be continuing to work on it hard between now and the 2010 release but it’s a start.

Updating the BPA tool was a major undertaking due to all of the new TFS topologies and features in 2010. Application Tier scale out, Data Tier scale out, Build agent pooling, Sharepoint flexibility and Lab Management are just a few of the new features that required a pretty major overhaul of the BPA tool. Our goal for this initial release was to get the BPA infrastructure updated to support the new multi-machine topologies, remove all of the old rules that don’t make sense any longer and add a handful of new rules that show we can scan the breadth of a TFS 2010 Server Farm. Over the next few months, we’ll be building out the new rules to provide a more comprehensive validation of a TFS install.

We’d certainly appreciate you giving it a try at some point and letting us know how it works for you.

You can read more about it on Ladislau’s blog here: http://blogs.msdn.com/lszomoru/archive/2009/11/17/team-foundation-server-2010-beta-2-best-practices-analyzer.aspx

Brian

SCRUM For Team System V3, Beta 2 released

bharry — Wed, 02 Dec 2009 03:53:00 GMT

EMC (formerly from Conchango) has recently released a Beta of a new release of their popular SCRUM for Team System. This Beta is designed to work with TFS 2010 Beta 2. You can find download details here:

http://scrumforteamsystem.com/cs/forums/4554/ShowPost.aspx

and I recommend checking out Crispin Parker's blog to learn more:

http://consultingblogs.emc.com/crispinparker/default.aspx

Brian

TFS 2010 Power Tools are Available

bharry — Wed, 02 Dec 2009 03:02:00 GMT

The first public build of the TFS 2010 Power Tools are now available. I wrote details about them a couple of weeks ago: http://blogs.msdn.com/bharry/archive/2009/11/18/tfs-2010-power-tools-coming-soon.aspx

A reminder – these are really “pre-release” Power Tools. We’re producing this build so that early adopters of TFS 2010 Beta 2 will have them but we’ll be producing a final 2010 Power Tools release near the VS/TFS 2010 launch date.

We’ve also moved our Power Tools from the general Microsoft download site to the Visual Studio Gallery site. This is in an attempt to make it easier to find all of the relevant Visual Studio add-ons.

Here are the links:

1. TFS MSSCCI Provider: http://visualstudiogallery.msdn.microsoft.com/en-us/f959ea32-5ac3-424a-a709-5001a158ebe8

2. TFPT: http://visualstudiogallery.msdn.microsoft.com/en-us/0e69a28f-020c-488b-80b3-f4c89a20621d

As always, if you find any issues, please report them. We are eager to fix any significant issues before the final 2010 release.

You can share questions, comments, etc on: http://social.msdn.microsoft.com/Forums/en-US/tfspowertools/threads

And you can report bugs at: https://connect.microsoft.com/VisualStudio

You can just set the product as TFS 2010 and note somewhere that it is a Power Tool issue and we’ll route it appropriately.

Thanks and sorry for the long wait,

Brian

More Beta 2 Localized builds available publicly

bharry — Wed, 25 Nov 2009 18:50:00 GMT

German

Microsoft Visual Studio 2010 Ultimate Beta 2 - ISO
http://www.microsoft.com/downloads/details.aspx?FamilyID=dc333ac8-596d-41e3-ba6c-84264e761b81&displaylang=de

Microsoft Visual Studio 2010 Ultimate Beta 2 – Web Bootstrapper

http://www.microsoft.com/downloads/details.aspx?FamilyID=92c65d2d-0a6b-4507-a4dc-767f4cc6e823&displaylang=de

Microsoft Visual Studio 2010 Professional Beta 2 - ISO
http://www.microsoft.com/downloads/details.aspx?FamilyID=a80dfb5d-51c6-4778-8656-a9ff29d3a132&displaylang=de

Microsoft Visual Studio 2010 Professional Beta 2 – Web Bootstrapper
http://www.microsoft.com/downloads/details.aspx?FamilyID=79d01825-f64b-433c-8873-17297fa5cc16&displaylang=de
Microsoft Visual Studio Team Foundation Server 2010 Beta 2 – ISO
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c70fd8f-615e-4203-a028-acb2c2b8b88f&displaylang=de

Microsoft .NET Framework 4 Beta 2
http://www.microsoft.com/downloads/details.aspx?FamilyID=ded875c8-fe5e-4cc9-b973-2171b61fe982&displaylang=de

Microsoft .NET Framework 4 Beta 2 Web Bootstrapper
http://www.microsoft.com/downloads/details.aspx?familyid=9F5E8774-C8DC-4FF6-8285-03A4C387C0DB&displaylang=de

Microsoft .NET Framework 4 Beta 2 LangPack – DEU
http://www.microsoft.com/downloads/details.aspx?FamilyID=178a0003-f791-4ff3-b6f6-633f0ad1740d&displaylang=de
Microsoft .NET Framework 4 Client Profile Beta 2
http://www.microsoft.com/downloads/details.aspx?FamilyID=68a7173d-7ee5-4213-a06f-f2e943ec9249&displaylang=de

Microsoft .NET Framework 4 Client Profile Beta 2 Web Bootstrapper
http://www.microsoft.com/downloads/details.aspx?FamilyID=206505ec-aa66-4d4e-be26-2b69b7d697d0&displaylang=de

Microsoft .NET Framework 4 Client Profile Beta 2 LangPack – DEU

http://www.microsoft.com/downloads/details.aspx?FamilyID=f04b5749-218f-4c8e-8673-1436037e0540&displaylang=de

Arabic

Microsoft .NET Framework 4 إصدار بيتا 2 لـ
http://www.microsoft.com/downloads/details.aspx?FamilyID=ded875c8-fe5e-4cc9-b973-2171b61fe982&displaylang=ar

Microsoft .NET Framework 4 Beta 2 Web برنامج تمهيد التشغيل لـ
http://www.microsoft.com/downloads/details.aspx?familyid=9F5E8774-C8DC-4FF6-8285-03A4C387C0DB&displaylang=ar

Microsoft .NET Framework 4 حزمة اللغة للإصدار بيتا 2 لـ
http://www.microsoft.com/downloads/details.aspx?FamilyID=178a0003-f791-4ff3-b6f6-633f0ad1740d&displaylang=ar

Microsoft .NET Framework 4 Client Profile إصدار بيتا 2 لـ
http://www.microsoft.com/downloads/details.aspx?FamilyID=68a7173d-7ee5-4213-a06f-f2e943ec9249&displaylang=ar

Microsoft .NET Framework 4 Client Profile Beta 2 Web برنامج تمهيد التشغيل لـ
http://www.microsoft.com/downloads/details.aspx?FamilyID=206505ec-aa66-4d4e-be26-2b69b7d697d0&displaylang=ar

Microsoft .NET Framework 4 Client Profile حزمة اللغة للإصدار بيتا 2 لـ
http://www.microsoft.com/downloads/details.aspx?FamilyID=f04b5749-218f-4c8e-8673-1436037e0540&displaylang=ar

Brian

VS Beta 2 is now available to MSDN subscribers in German

bharry — Sat, 21 Nov 2009 03:23:00 GMT

In addition .NET 4.0 Beta 2 is available in Arabic.

Here's the SKU list:

Visual Studio 2010 Team Foundation Server Beta 2 (x86 and x64) - DVD (German)

Visual Studio 2010 Ultimate Beta 2 (x86) - DVD (German)

Visual Studio 2010 Professional (x86) - DVD (German)

Visual Studio 2010 Ultimate Beta 2 Web Installer (x86) - (German)

Visual Studio 2010 Professional Beta 2 Web Installer (x86) - (German)

.NET Framework 4 Full Language Pack Beta 2 (x86) - (German)

.NET Framework 4 Full Language Pack Beta 2 (x86 and x64) - (German)

.NET Framework 4 Full Language Pack Beta 2 (x86 and ia64) - (German)

.NET Framework 4 Client Profile Language Pack Beta 2 (x86) - (German)

.NET Framework 4 Client Profile Language Pack Beta 2 (x86 and x64) - (German)

.NET Framework 4 Full Language Pack Beta 2 (x86) - (Arabic)

.NET Framework 4 Full Language Pack Beta 2 (x86 and x64) - (Arabic)

.NET Framework 4 Client Profile Language Pack Beta 2 (x86) - (Arabic)

.NET Framework 4 Client Profile Language Pack Beta 2 (x86 and x64) - (Arabic)

Brian