MSDN Library is now featuring 44 chapters from 13 O’Reilly books on subjects such as C# 3.0, Visual Basic 2008, ADO.NET 3.5, .NET 3.5, the ADO.NET Entity Framework, WCF Services, and ASP.NET 3.5.
You can find them in 3 distinct areas of the MSDN Library:
And here’s the list of the books that have some of their chapters featured on the library:
ASP.NET:
Visual Studio 2008:
.NET Development:
Enjoy!
With the release of .NET Framework 4 this week, it is relevant to talk about migration issues you might run into when upgrading your applications to .NET 4. My team has put together a topic that describes the migration issues (formerly known as breaking changes) between the .NET Framework version 3.5 Service Pack 1 and the .NET Framework version 4. The change in terminology is to reflect the fact that not all changes introduced by a new version of the framework break your application; rather, these are changes in behavior discovered during design review and testing that could potentially impact an application.
We’ll update our portal (.NET Framework Version and Assembly Information) that points to different migration issues topics to include the .NET 4 version as well. So in a nutshell, these are the migration issues topics we have published so far and their locations:
Give Your Feedback on the Documentation
Help us improve the developer documentation by taking the Visual Studio and .NET Framework Content Survey. This survey will give us a better understanding of the type of applications you are developing as well as how you use Help and how we can improve it. The survey takes only 10 minutes, and we appreciate your feedback!
The CLR team is posting a series of Channel 9 videos mainly about the new CLR 4 features.
You can access all the videos posted, by clicking here.
This is the list of videos published so far:
You can download the Channel 9 videos in different formats so that you can even watch them at your Zune or IPod.
Soma, senior VP of the Developer Division, just announced on his blog that today we are releasing Beta 1 of Visual Studio 2010 and .NET FX 4! If you are a MSDN subscriber, you can download the Beta today from here. For the rest of the world, the Beta will be publicly available on Wednesday.
And we’re also shipping today the documentation on MSDN online!
For .NET Framework 4 Beta 1 documentation, click here.
For Visual Studio 2010 Beta 1 documentation, click here.
As usual, send your feedback on the documentation so we can get your comments and suggestions incorporated before we ship the final release.
More is on the way for the next releases, so stay tuned!
When IE8 was released, I went ahead and installed it in all my machines at home and at work. In one of my machines at work, I started to get an annoying memory error message whenever I would close the browser or sometimes while browsing. The error message was the following:
“The instruction at "0x749860a0" referenced memory at "0x00000000". The memory could not be "read". Click on OK to terminate the program.”
Today we had a presentation from a Program Manager of the IE group and I asked him about this error after he finished. What he told me is that usually is an add-on that is causing the issue. So he suggested me to go to Tools –> Manage Add-ons, select all add-ons and click on Disable all. Close the browser, reopen and close it again. If the message box disappears (in my case it did), I’d know that is one of the add-ons that was causing the issue.
Adding back one add-on at a time (closing, reopening and closing again after I enabled each one to see if the message would show up) , I was able to find some culprits. ;-)
I hope this helps!
Microsoft has just released the Release Candidate 1 for Internet Explorer 8 that you can install from here.
Some of the new features include:
· Mapping a location: Highlight a street address in your Hotmail, Yahoo Mail, or other web mail account, right-click on the blue button that appears, and hover over “Map with Live Search.” Presto! You’ll see the map with the location right there—no more copying and pasting street addresses from web mail to a mapping site. Plus, you can choose what mapping service you want to use.
· Instant Search Box: Go to the search box in the top right, and type a search item—see how the enhanced Instant Search Box is more helpful, providing real-time search suggestions, including images, from your chosen search provider.
· InPrivate Browsing: Click on a new tab, and see the options that are presented there, including “InPrivate Browsing.” Click InPrivate Browsing and watch what happens—you are now in a browser session that is leaving no trail behind, so research gift suggestions for your significant other to your heart’s content without worrying about who might pick up the crumbs after you.
Also, IE8 is supposed to be faster, easier to use, safer and more reliable. It is worth to check it out!
The CLR team has a column inside the MSDN magazine called 'CLR Inside Out'.
This month’s article is about Best Practices For Managed And Native Code Interoperability. It was written by Jesse Kaplan, the PM for Managed/Native Interoperability on the CLR team. The article provides high-level architectural guidance and discusses the three techniques available in the .NET framework for managed-native interoperability: P/Invoke, COM Interop and C++/CLI.
To see a list of all articles already published on the 'CLR Inside Out' column, go here.
Just a quick note to announce that the CLR team has created a blog to post about interesting subjects about - of course - CLR! In the coming weeks, the posts should be starting pouring over there. Be sure to add to your favorites or RSS readers.
Check it out at http://blogs.msdn.com/clrteam/.
The Visual Studio documentation is localized into nine languages: Chinese (Simplified), Chinese (Traditional), English, French, German, Italian, Japanese, Korean, Spanish. To expand the availability of relevant technical content to a wider, global audience of developers, Microsoft has launched two years ago the MSDN Translation Wiki. The first language available for this was the Brazilian Portuguese. The Translation Wiki was a combined effort of Microsoft and local universities to get a good machine translation in place and some tech reviews in the most popular topics. So Brazilian developers now have the MSDN documentation in their native language. The automatic translation is not always great, that's why is in a wiki format. Users can suggest a better translation and the moderators (like myself) will review it.
Because it's a translation wiki, the default view has both languages side-by-side (English and Portuguese). For me, as a moderator, that is great because I can review the original sentence and the translation. What struck me today is that I've never realized that you could choose to show only the English frame or only the translation frame, which is very helpful for someone that is not interested in the English version. And I only realized that because of a customer feedback bug that I was translating today!
So I'll switch to Portuguese now to try to help our customers facing this issue...
Se você está visualizando uma página em português no MSDN, como por exemplo Guia de Programação C#, observe que tem um filtro no menu superior chamado Exibir Conteúdo. A opção pré-selecionada é Lado a Lado, que vai exibir o conteúdo tanto em inglês como em português, o que pode dificultar a leitura. Por isso, você pode selecionar entre as opções Apenas em Inglês ou Apenas Tradução.