DisclaimerPostings are provided 'As Is' with no warranties and confer no rights.
Internet Explorer 7 Beta 3 is now available for download and includes improvements in reliability, compatibility, user features, and security. Although Internet Explorer 7 Beta 2 was layout complete, they."
Internet Explorer 7 reliability has improved in Beta 3 as several layout-rendering bugs have been fixed as well.
In addition, Beta 3 contains all the security fixes addressed in the June Internet Explorer Security Bulletin MS06-021.
Enjoy!
Fresh from the WCF Team, here is the latest Documentation CTP for you to download.
Don't let the title confuse you. There is no new version for Enterprise library for .Net Framework 3.0. Yet...
But, Tom Hollander, has posted that the patterns & practices team are starting to plan that version, and they are looking for ideas. So, If you have have some suggestions, this is your chance.
Two detailed Hands On Labs for .Net Framework 3 Beta 2 are available for download at wcf.netfx3.com:
If you are experiencing troubles with the intellisense or with the refactoring smart tags after installing LINQ May CTP here is the solution for you:
MSDN TV has a new episode featuring Clemens Vasters speaking about WCF bindings (and what they cause in the channel stack). Totally 20 minutes, really nice talk...
When exploring new technologies, You often wonder what is really written in the assemblies you reference.
Currently, exploring WF and WCF along many other exiting new technologies, I am working with a great tool that I want to share with you: Reflector for .NET.
Reflector is the class browser, explorer, analyzer and documentation viewer for .NET. Reflector allows to easily view, navigate, search, decompile and analyze .NET assemblies in C#, Visual Basic and IL.
So, If you want to know all about how System.Windows.Forms.Control is implemented, and how serialization works, Download this excellent yet simple tool.
Through WCF Cpnnection site, you can get in touch with the Windows Communication Foundation Product Team, submit suggestions for new features, and report errors in the product, in our tools and in the product documentation.
Microsoft Corp. today announced that effective July 2008 Bill Gates, chairman, will transition out of a day-to-day role in the company. The company announced a two-year transition process. The company announced that Chief Technical Officer Ray Ozzie will immediately assume the title of chief software architect and begin working side by side with Gates on all technical architecture and product oversight responsibilities. Gates then will continue as chairman and advisor while increasing Foundation efforts.
Read more...
The next version of ADO.NET starts to deliver on Microsoft’s vision for an Entity Framework that can fundamentally change how you think about data. Find out what problem spaces the ADO.NET Entity Framework and Language-Integrated Query are targeting, and their innovative approach for addressing those challenges.
Download the Next Generation Data Access white paper here.
Download the ADO.NET Entity Framework Overview here.
Download the ADO.NET Technical Preview - Entity Data Model. Read more here…
Since this API is exposed from the Weblogs providers, programmer have to use a client-side programming model to communicate with it according to the XML-RPC protocol. Josh Gough has created and published this C# programming wrapper which allows us to easily develop C# client applications that consumes this API via a service.
How do you get started ?
Example:
using MetaBlogAPI;
IBlogger proxy = MetaBlogAPIFactory.Create();string user = "user";string password = "password";string blogid = "bursteg";
// Create a post. There are some optional properties such as Categories// that were not supplied in this sample.Post p = new Post();p.title = "Bloging from C# code";p.dateCreated = DateTime.Now;p.description = "Can you see it?";string postid = proxy.newPost(blogid, user, password, p, true);
Great, isn't it?
My next step is to write a workflow activity that posts an entry to my blog. Look forward for it!
Enjoy!
When debugging code, one of the annoying things for me is to step into a one-line method or property. For example, Assume that I have the following property:
/// <summary> /// Returns the word (string) of this lookup word /// </summary> public string Word { get { return word; } set { word = value; }
And I have a code that uses that property when calling a method:
// Use that property as a parameter for a method DoSomething(obj.Word);
When you debug that line, and step into the method, you'll step into the get section of the property, and only then move on to the method.
There is a way to control this behavior and instruct the debugger to step through that method and not into it. This is done using the System.Diagnostics.DebuggerStepThrough attribute, when placed above the method.
/// <summary>/// Process the word /// </summary> /// <param name="w"></param> [System.Diagnostics.DebuggerStepThrough] public void DoSomething(Word w) { // Do something
To apply this attribute to properties, you should simply apply the attribute to the get section and set section separately since each of them is implemented as a method itself.
/// <summary> /// Returns the word (string) of this lookup word /// </summary> public string Word { [System.Diagnostics.DebuggerStepThrough] get { return word; }
[System.Diagnostics.DebuggerStepThrough] set { word = value; }
This instruction will cause the debugger not to step into that method (property) as normal, but you can always place a breakpoint in that method and stop there. In order to prevent the debugger from stepping into that method as a rule, you can use System.Diagnostics.DebuggerHidden attribute.
If you want to expose a service that outputs RSS 2.0 or ATOM 1.0, It is now easy than ever. Today the WCF RSS Toolkit was announced for public use.
."
Download the toolkit from here (source code included).
Following the latest announcement by Soma, A new site dedicated fully to .Net Framework 3.0 has launched today.
NetFx3.com is a new developer community that focuses on the four new technologies included in the Microsoft .NET Framework 3.0 (the technologies formerly known as WinFx):
NetFx3.com is based in part on the feedback we received for the WindowsWorkflow.net and WindowsCommunication.net sites that were launched. The Windows Workflow Foundation and Windows Communication Foundation sites are now represented as “sub-communities” within NetFx3.com. We have also created new sub-communities for Windows Presentation Foundation and Windows CardSpace, so that the four new pillars of the .NET Framework 3.0 are fully represented in this site.
The site has been designed to aggregate information on the .NET Framework 3.0 technologies from product team and community bloggers, MSDN forums, and Channel 9. You can easily find and share samples, code snippets, and other resources.
So – update your RSS feeds to the new site, and enjoy it!
S. Somasegar, VP of the Developer Division at Microsoft Corporation, announced today that the name WinFX was renamed to .Net Framework 3.0. The change is in name only and will not affect the technologies being delivered as part of the product..
Looking forward!