Tracking change and innovation in the enterprise software development community
IBM WebSphere
Virtualize apps
to lower costs,
Increase agility
Learn more!
Create REST
-enabled Web Apps
with Project Zero
from IBM.
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
QCon San Francisco
Nov 19-21:
+ 80 sessions & tracks
Register now
and Save $400!
Posted by Jonathan Allen on Jun 07, 2007 01:48 AM
For a number of years Visual Studio has supported non-Microsoft languages as plug-ins. However, the high cost of Visual Studio itself prevented it from being a platform for 3rd party language developers. This has changed with the announcement of Visual Studio 2008 Shell.
Visual Studio 2008 Shell is literally just the Visual Studio shell sans-compilers. VS Shell is completely free of licensing and royalty fees, making it a suitable platform for competing languages.
VS Shell packages can be deployed in one of two modes. Integrated mode merges the package into the standard Visual Studio environment. This should allow developers to work with traditional VS languages like C++, VB, or C# alongside newer languages like IronPython.
The second mode, known as isolated mode, is more for application development than language development. In the example on the Visual Studio Shell site , an end-user application called Fabrikam Home Automation Studio is shown. As this application is a specialized tool rather than a typical programming language, it runs with toolbars and menus customized just for it. One could think of this as a general case of Visual Studio Express, where each 'version' is isolated from the next even though they technically share the same IDE.
VS Shell does not have support for any Microsoft tools or languages built in. However, if the user also has a paid Visual Studio SKU (Standard, Professional, or Team System) then the tools and languages will be available alongside VS Shell packages deployed in integrated mode.
Developers considering using VS Shell are being asked to contact Microsoft at vsipinfo@microsoft.com.
IBM Agile Development eKit: Free Articles, Expert Q&A, Educational Resources
SOA Development Survival Guide
Software Quality Survival Guide
IBM Web 2.0 Developer eKit: Free Tutorials, Webcasts, Whitepapers
Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.
In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.
In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.
It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.
In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.
In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.
Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.
Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.
1 comment
Reply