Tracking change and innovation in the enterprise software development community
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Free Book Offer
SOA Demystified
$40 Value
Posted by Jonathan Allen on Sep 30, 2006
Microsoft has a tough decision. They can either concentrate on the next version of Visual Studio, with features such as LINQ, or they can ensure Visual Studio 2002/2003 works Vista.
Comments such as these are common on the Microsoft web logs:
Seeing that the support for VS2003 will not be present on Vista is a bit worried for us. We've lots of large customers that works with .NET 1.1 applications and surely they will not be ready for a migration soon. In second, we work a lot on the Dynamics platform, and here .NET 1.1 is he standard.
Should we plan to have a machine with Vista and a machine with XP? Not so good... By doing this, you'll see that XP will be the main platform for a lot of time.
Stefano Demiliani
Visual Studio .NET 2003 is a product that was out 2+ years ago. Many of our customers, partners and vendors still rely on it. Not supporting VS 2003 and/or .NET 1.1 is harshly forcing everyone to upgrade to 2005 version. Many IT Departments and CTOs are unable to justify the upgrade in such a short span of time.
Wilson Loo
While there isn't a lot of vocal support for their decision, Microsoft is standing firm for both technical and financial reasons.
Development tools as a whole have requirements that are not a part of normal applications. Some of the things developer tools expect to do are also the types of things that malicious code tries to perform on a user machine. As you all know, the Windows team has continued to make great progress w/Vista on the security front. There are a number of new security related work and features that are a part of Windows Vista. In the case of Visual Studio, things like debugging while attaching to a process requires reading and modifying that process’ memory, or registering a COM component directly conflict with the principles behind some of the new security features in Windows Vista.
I’ve also clearly heard the concern around our decision not to support VS.NET 2003. We know from talking to customers that some of them have been successful in using VS.NET 2003 and VS2005 on Windows Vista when running as an administrator on the machine. However, there are some scenarios, like those I described above, that will not work. Going forward, we will provide more details on what these issues are and any known workarounds that you can use. Also, when we have fixes to workaround some of these problems, we will make them available.
Like you, we have resource constraints. It might look like Microsoft is a huge company with infinite resources but, unfortunately, it’s not. We are just as constrained as everyone else in the world as to how we invest our time and money. I can assure you we have spent a lot management time wringing our hands over what the right thing to do here is. All work we do comes at an opportunity cost. For example, if we go back and make VS2002 work on Vista, we have to trade that off against not making progress on Orcas. Ultimately, we balanced all of these trade-offs and came up with this plan. The plan is to support our run time environments on Vista and to support VB6, VS2005, Orcas and all future versions. Would it be good to support more? Yes. Is it worth the opportunity cost? We think it isn’t.
Understand and Align BPM, SOA, and Lean Six Sigma: 43 page IBM Redguide
Architectures Behind Facebook, Skype, Sky.com, Bwin, League of Legends @ QConLondon
.. is that .NET 1.1 support is missing from the newer tools. There are three issues here. First, and most importantly, will .NET 1.1 applications work on Vista? Second, will .NET 1.1 applications be buildable and maintainable on Vista? Third, will the old VS2003 work on Vista? Arguably, all three are obvious and important, and right now the second and the third are coupled.
Peace,
Cameron Purdy
www.tangosol.com/
Microsoft has the resources to branch VS2003 and continue to support it with a dedicated team of developers for the next hundred years, and at the same time develop a completely new/different VS for Vista, if they want to. Its a matter of priorities and willingness to support the current customer base.
In my opinion, what they really want is to move everyone to Vista as soon as possible, and forcing the developers to move first is a key strategy in making that happen.
My question is:
Will (and should) VS2005 be supporting .NET 1.1 projects (on XP or Vista)?
I don't understand how not ensuring VS2003 works on Vista will force developers to use Vista. I think the opposite is true -- it could be a barrier to adoption for Vista. If you need to use VS2003, then you also stay on XP. The comment by Brian Harry says that the runtime environments (which I take to include .NET 1.1) will work on Vista, just not the development environment.
Agree with Eric.
How about using Virtual PC for the VS 2003 development? If added enough RAM on the developers' workstations, they could use the virtual machine to work on VS 2003. The developers do not need to worry about if they need to upgrade to Vista or not.
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
5 comments
Watch Thread Reply