Umbraco Web CMS 4.9 Focuses on the Editor Experience, Rich Media

The open source content management system Umbraco may have dropped version 5, but the refocus on version 4 has brought some nice improvements and a number of bug fixes.

The free, ASP.Net-based Umbraco is designed for building websites — from small campaign or brochure sites to large media-based sites — and complex Web applications.

Umbraco, which bills itself as a  “priceless CMS at the cost of virtually nothing,” was first released in version 2.0 in 2005, which was also when the first developers conference, called CodeGarden, was held. Unfortunately a turn in the wrong direction resulted in dropping the next major version of the Web CMS to go "back to the basics".

“The early days of Umbraco was the result of a wonderful collaboration between three guys in Copenhagen,” wrote one of those guys, Niels Hartvig, on the Umbraco blog. He added that, “almost eight years later — I’m smiling again” because of the new release.

Focus on the Editor Not the Developer
Umbraco 4.9 features a revised editor, easier integration of third-party videos and images, and a new media library. In addition, the new version includes more than 50 “big” bug fixes, incorporated from submissions by over 20 contributors.

The application now supports HTML5 uploads to the media section, and there’s a new folder content overview that can be filtered and from which common actions can be applied to media items.

The Media button in the Rich Text Editor now supports the oEmbed standard in its embedder, and the code editor for templates, scripting and XSLT templates has been upgraded. Creating and inspecting relation types can now be conducted from the backoffice.

Will Microsoft dive into Open Source Ecosystem?

Microsoft has come a long way in its acceptance of open source. And its motto doesn’t seem to be (this time) to embrace and extinguish.

The Microsoft watching will go on. A few illustrious members of the worldwide Microsoft community to share their insights via guest posts on a variety of topics — from Windows Phone, to Hyper-V. Today’s entry is all about Microsoft and open source and is authored by Richard Turner.

Microsoft is increasingly warming to open source. Not only is the company increasingly publishing open-source projects of its own, it’s also developing major parts of its web/cloud infrastructure in the open and is also supporting a variety of external open-source projects. This is great news, but it’s taken a long time and a considerable amount of hard work and damage-repair to make it happen.

Microsoft’s stance on open source began to thaw during the 2000’s as the company grew-up and learned more about open source and how it can significantly benefit all of us.

It would be constructive to share examples that illustrate that Microsoft (and its ecosystem) are serious about mending fences, supporting external open-source projects and opening up development teams and projects.

Here’s the top 10 list:
1. Encouraging the Open Source Ecosystem
The Windows and .NET development community is exploding with home-grown .NET open-source projects and initiatives. Everything from IoC/DI containers such as Ninject, AutoFac, Castle Windsor and StructureMap to testing tools like nUnit. From NOSQL document stores like (the utterly awesome) RavenDB to powerful Content Management Systems (CMS) like Orchard and Umbraco. And let’s not forget IronPython, IronRuby and F# that Microsoft nurtured before transitioning to community ownership in 2010.

These are just a tiny subset of the amazing range of open-source projects built specifically for (or supporting) the .NET/Windows platform.

2. Wheel-Reinventing Reduced
One of the biggest criticisms many have had of Microsoft is its insistence in building its own version of technologies that already exist in the open-source world.

It came as a pleasant surprise, therefore, when Microsoft shipped ASP.NET MVC 3.0 with jQuery and Modernizr included. This was a big step forward (and was the result of a HUGE amount of effort internally) and marked one of the first times Microsoft shipped a major product containing open-source code. In ASP.NET 4.0, Microsoft is continuing the adoption of open-source projects by including jQuery Mobile & JSON.NET.

3. Facilitating With NuGet Package Manager
Almost every active open-source development ecosystem has seen huge growth in the number of open-source utility libraries made available by “package managers” such as Ruby’s Gems, node’s npm, etc. These package managers allow developers to simply type, for example, “npm install express” and the express library will be downloaded and installed into the user’s current project/system.

A package management tool was missing from the Windows/.NET developer’s toolbox until a skunk-works team at Microsoft created NuGet – a package manager for .NET developers. NuGet and its accompanying site, gallery and package feed were adopted by the Outercurve Foundation in October 2010 and is now maintained by the NuGet team and the community. The NuGet gallery currently contains almost 6000 packages including jQuery, Modernizr, JSON.NET, ELMAH, log4net, Ninject, and the vast majority of the libraries most useful to .NET developers.

While many other open-source communities would scoff at “only 6000” packages being available, it’s important to note that the project count is increasing rapidly and that the proportion of really useful packages to frivolous and/or repetitive packages is very small. Let’s hope it stays this way!

4. Making Windows a great platform for open-source
Many of the hottest open-source projects available today were originally built on Linux-based platforms and, as such, are welded to UNIX-style IO, file storage, process management and thread scheduling mechanisms. In order to run on Windows, such projects typically run under CygWin – a POSIX emulation infrastructure that allows most POSIX apps to run unchanged on Windows. While this is a pragmatic approach for non-performance-sensitive code, Cygwin often introduces a significant performance hit in high performance code.

This was the situation facing node – the blossoming asynchronous JavaScript engine – to run on Windows, it had to be run under CygWin, which impacted performance significantly. To solve this problem, Microsoft and Joyent (node’s primary sponsor & employer of Ryan Dahl - node’s creator) agreed to work together to make node run natively on Windows. The work to port node to Windows spawned LibUV – a library that provides a platform-abstraction layer allowing node (and any other open-source project) take full advantage of both *N*X and Windows’ async IO (and other platform dependent differences) with little effort.

In November 2011, Microsoft announced the first stable builds of node, using the new LibUV library, running natively on Windows. Simultaneously, Microsoft built IISNode allowing node to be hosted within IIS (Microsoft’s web server). The code for IISNode is hosted on GitHub and is free and open for all to see and/or modify should you wish to do so. And that’s not the end of the story: LibUV has turned out to be so useful that other open-source projects are now employing it to port their code to run natively on Windows.

5. Forking and Maintaining Ports
In a sign of increasing maturity in how it works with open-source communities, Microsoft has now begun (appropriately) forking and maintaining open-source projects: In November 2011, Antirez announced that Microsoft had provided patches to port Redis to run natively on Windows, using LibUV. While Antirez decided NOT to accept Microsoft’s patches into the Redis core (yet, for reasons he articulated in the post linked to above), he encouraged Microsoft to create their own Windows fork of Redis. Microsoft worked with others in the community to create a Windows fork of Redis which became the first project officially published by the newly formed Microsoft Open Technologies Inc. subsidiary formed in 2012 and is run by Jean Paoli.

6. Supporting Apache, PHP and Ruby on Windows
In 2008, Microsoft began helping upgrade Apache and PHP significantly update their projects in order to support the newer and far more effective Visual C++ 2008 VC9 compiler. This work resulted in native builds of both the Apache web server and the PHP engine which consumed less RAM and performed much better than before.

In 2008, alongside the new and improved PHP, Microsoft also released support for FastCGI within IIS. This enabes IIS to reliably host non-threadsafe code such as PHP and Ruby, alongside .NET code and native IIS handlers and modules within the same website if required. This means that IIS can now safely and reliably host PHP-based websites and services including Wordpress, Drupal, Joomla, etc.

7. Supporting open-source platforms in Azure
At Mix09, Microsoft announced official support for PHP, Java and Ruby on Windows Azure.

Since Windows Azure Web Role instances are essentially Windows Server VM’s, this should come as no surprise since Microsoft had already released FastCGI support for IIS.

What this announcement introduced, however, was the fact that not only was Microsoft supporting PHP, Ruby and Java on Azure, but that they were also in the process of providing comprehensive API’s for each environment, allowing developers to access all of Azure’s service control & configuration capabilities, table, blob and queue storage, message-bus infrastructure, etc. from their preferred language/platform.
Then, in December 2011, after the work to port node to Windows was completed, Microsoft announced that node is now fully supported in the Windows Azure cloud platform, along with a node Azure SDK providing programmatic access to the Azure environment and storage and message-bus infrastructure.

8. Backing Hadoop
In late 2011, Microsoft and HortonWorks announced they were teaming-up to port Hadoop to Windows. This is a big deal; not only did Microsoft decide to plow effort and resources into porting Hadoop to Windows, they decided to abandon their own home-grown big-data solution in the process. Microsoft’s adoption of Hadoop can only result in good things – particularly to end-users who will be able to analyze colossal datasets using familiar tools such as Excel and PowerView.

9. Becoming A Top-20 Contributor To The Linux Kernel
In 2011, Microsoft became one of the top 20 contributors to the Linux kernel … the same Linux that CEO Steve Ballmer described as a “cancer” just over 10 years previously. My, how times change!

Microsoft’s contributions largely center around drivers they submitted to enable Linux to be hosted within Hyper-V – Microsoft’s OS virtualization technology. The drivers Microsoft submitted to the Linux kernel project provide a significant performance boost to Linux VMs’ storage, networking and video-subsystems.

10. Open Sourcing ASP.NET MVC4.0, WebAPI and Razor View Engine
Perhaps the biggest news related to Microsoft and open source came when Microsoft announced that:

ASP.NET 4.0 MVC, Web API and Razor View Engine would be made open-source
The ASP.NET team will consider accepting changes to ASP.NET submitted by the community
The ASP.NET team would continue development of ASP.NET “in the open”, submitting all future code changes into a public-facing GIT repository hosted by the Outercurve Foundation’s CodePlex site.
It clear that Microsoft has finally turned a corner and is now increasingly following a path towards greater acceptance and support for open-source. This is a GIGANTIC step forward.

Microsoft is leading by example and sending a strong message to their legions of developers that open-source need be feared no longer and that publishing open-source code benefits everyone. Hopefully, this will result in a gradual, but eventually sizable increase in the volume of high-quality, reusable code being made available as open-source for us all to enjoy, learn from, help improve and adopt.

Now, the time is Come. Welcome to the open-source world, Microsoft. Please Hop-On.

ASP.NET MVC, Web API, Razor and Open Source

Microsoft has made the source code of ASP.NET MVC available under an open source license since the first V1 release. We’ve also integrated a number of great open source technologies into the product, and now ship jQuery, jQuery UI, jQuery Mobile, jQuery Validation, Modernizr.js, NuGet, Knockout.js and JSON.NET as part of it.

I’m very excited to announce today that we will also release the source code for ASP.NET Web API and ASP.NET Web Pages (aka Razor) under an open source license (Apache 2.0), and that we will increase the development transparency of all three projects by hosting their code repositories on CodePlex. Doing so will enable a more open development model where everyone in the community will be able to engage and provide feedback on code checkins, bug-fixes, new feature development, and build and test the products on a daily basis using the most up-to-date version of the source code and tests.

We will also for the first time allow developers outside of Microsoft to submit patches and code contributions that the Microsoft development team will review for potential inclusion in the products. We announced a similar open development approach with the Windows Azure SDK last December, and have found it to be a great way to build an even tighter feedback loop with developers – and ultimately deliver even better products as a result.

Very importantly - ASP.NET MVC, Web API and Razor will continue to be fully supported Microsoft products that ship both standalone as well as part of Visual Studio (the same as they do today). They will also continue to be staffed by the same Microsoft developers that build them today (in fact, we have more Microsoft developers working on the ASP.NET team now than ever before). Our goal with today’s announcement is to increase the feedback loop on the products even more, and allow us to deliver even better products. We are really excited about the improvements this will bring.

Microsoft Releases Open-source Content Management App

Microsoft has released an early version of an open-source content management platform that developers can use to build sophisticated blogs or large Web sites.

Called Oxite, its creators describe it as a standards-compliant and highly extensible content management platform. They built it not because there is a need for another blog engine, but because they were building the MIX Online site for Web designers and wanted to offer an example of a use for ASP.NET MVC, according to the Oxite Web site.

ASP.NET MVC lets developers use ASP.NET to build Web applications using an architecture called model-view-controller. Microsoft released a preview of the ASP.NET MVC framework, designed to make it easier for developers to test applications, late last year.

Oxite includes a number of important blog functions that can be complex to implement, according to Microsoft. The framework offers many features common in blogs, including pingbacks, trackbacks, anonymous or authenticated comments with the option to moderate comments, RSS feeds for any page and a Web administration panel.

It's also designed for users to easily add new Web pages and sub-pages.

At first glance Oxite appears to compete with established blogging products including those from Six Apart. However, Microsoft says that Oxite is designed for developers, rather than less-technical Web users wanting to set up a blog.

Read More..

ASP.NET Is The Latest Version Of ASP Technology

ASP.NET is the next generation ASP, but it's not an upgraded version of ASP. ASP.NET is an entirely new technology for server-side scripting. It was written from the ground up and is not backward compatible with classic ASP.ASP.NET is the major part of the Microsoft's .NET Framework.
ASP.NET is a server side scripting technology that enables scripts (embedded in web pages) to be executed by an Internet server.

•ASP.NET is a Microsoft Technology
•ASP stands for Active Server Pages
•ASP.NET is a program that runs inside IIS
•IIS (Internet Information Services) is Microsoft's Internet server
•IIS comes as a free component with Windows servers
•IIS is also a part of Windows 2000 and XP Professional

ASP.NET 2.0 improves upon Asp.Net by adding support for several new features and ASP.NET 3.0 is not a new version of ASP.NET. It's just the name for a new ASP.NET 2.0 framework library with support for Windows Presentation Foundation, Windows Communication Foundation, Windows Workflow Foundation; and Windows Card Space.

Benefits of ASP.Net

•ASP.NET has better language support, a large set of new controls and XML based components.
•ASP.NET provides increased performance by running compiled code.
•ASP.NET code is not fully backward compatible with ASP.
•Event-driven programming
•User authentication, with accounts and roles
•Higher scalability
•Easier configuration and deployment


Read More..

Using URL Rewriting With Web Parts

Web parts are a great new system for allowing personalization of web sites by end users that was introduced in ASP.NET 2.0. However, it isn't useful when used in combination with URL rewriting.

URL rewriting allows you to respond to requests from dynamic URLs by redirecting the handling to a different .ASPX file on your server. This can be used to make your URLs more readable and improve your search engine optimization (SEO), instead of using long query parameters.

Some example systems for implementing this are UrlRewriter.net and UrlRewriting.net.

When you use web parts in combination with a rewritten URL, the web parts will all be shared by all of the URLs that are rewritten to the same .ASPX file. This library corrects this by replacing the WebPartManager with RewritableWebPartManager and the SqlPersonalizationProvider with RewritableSqlPersonalizationProvider.

It also provides additional functionality in the form a personalization levels. This allows you to share common personalization settings amonst multiple URLs. When a user is browsing, if no personalization is specified at a particular level, the personalization defined at a higher level is displayed instead. For example, in a web store scenario you can allow the store operators to provide shared personalization that all users will see. Using levels, they can set personalization
that will appear on all item pages, such as a disclaimer, and then override that personalization with a different disclaimer on a specific item's page.

Read More..

ASP.NET Vs Others

When it comes to Web development these days, you have a lot of options. Many of these methods involve preprocessing—that is, embedding code into HTML pages with special tags that signal to a preprocessor that they contain code, and that it should do something with it. Much like a CGI, this code is then run on the server, and it returns some content, which then assumes part of the shape of the resulting HTML page sent back to the browser. Both the open source scripting language PHP and languages within Microsoft's ASP.NET framework fall into this category; JavaServer Pages (JSP) and Perl/Mason operate this way as well.

What is ASP.NET?
The latest incarnation of ASP, ASP.NET, is not completely backward-compatible with previous versions of ASP, as it is a complete rewrite of the software. Previous ASP technology actually has a lot more in common with PHP than with ASP.NET, which is a complete framework for building Web applications. One of the principal features of this model is the flexibility to choose your programming language. ASP.NET works with scripted languages such as VBScript, JScript, Perlscript, and Python, as well as compiled languages such as VB, C#, C, Cobol, Smalltalk, and Lisp. The new framework uses the common language runtime (CLR); your language source is compiled into Microsoft Intermediate Language code, which the CLR then executes.

The framework also provides for true object-oriented programming (OOP), and true inheritance, polymorphism, and encapsulation are supported. The .NET class library is organized into inheritable classes based around particular tasks, such as working with XML or image manipulation.

Besides the programming language and the methodology, database access is a significant concern. When you program in ASP.NET, integration with databases can be accomplished through ODBC, which provides a consistent set of calling functions to access your target database.

What is PHP?
PHP is a scripting language based on the model of preprocessing HTML pages. When the PHP preprocessor in your Web server notices a PHP language tag like the following, the PHP engine is invoked to execute that code:

some code here
?>

PHP will be familiar to any programmers who have worked with imperative programming languages; you'll notice syntactical similarities with Perl, C, and Java. Strictly speaking, Java is an imperative programming language, but it also makes use of object-oriented constructs and concepts. PHP borrows from this structure when it is convenient, but it is not a pure OOP language. Read More…

Mono 2.0 Released

It's now loosely compatible with .NET Framework 3.5

The open source Mono project that makes Microsoft's .NET development framework cross-platform - and is meant to entice Windows developers to Linux by making things seem warmly familiar - is now loosely compatible with .NET Framework 3.5.

It lacks Windows Presentation Foundation, Workflow Foundation and Communication Foundation. Read more...