Scott Guthrie has announced that Visual Studio 2008 and .NET 3.5 are now available for download and provides a tour of some of the new features. "Visual Studio 2008 and .NET 3.5 contain a ton of new functionality and improvements. Below are links to blog posts I've done myself as well as links to videos you can watch to learn more about it."
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-06
I dont get your point? You write a lot of nonsense, impossible to respond to.
That's because you have no clue what I am talking about, or what you are attempting to talk about. You know what? I rather suspect you do know ;-).
What dependencies? The dependecies (external libraries etc) i in my application?
If you take that attitude then you start losing a stable target to port to - rapidly. Bundling everything with an application, including the entire framework your application runs on, is not an option, especially when other applications installed on a target machine may well use the same software. Apple users think app folders are so cool. Yer, right? Watch what happens when people actually develop for your platform and are sharing many of the same components.
When you use .Net and Microsoft's development tools any time soon, you'll find that if someone uses Avalon, although it may well run on Vista, you're going to have to give serious thought as to how it will run on XP and 2000 and what you will install to do it. If you use WinFX, as the development tools and literature now gears you towards using, where does that leave you in terms of deployment? You may well choose not to use it, as most aren't. I mean, the following is a slide from a presentation I have seen myself:
http://weblog.infoworld.com/udell/gems/WinformsVsAvalon.jpg
That's just fricking insane.
You are right its not 1990 anymore, and its not 1995 anymore either. Luckily dll-hell is non-exisiting in .net, if you do things the "Correct way"(tm).
DLL hell is still very much around. It's just called dependency hell now. You're reading way too much marketing literature, and that above decision diagram is not the correct way by any stretch of the imagination.
And yes it is fud, i strongly belive you yourself has had a big dose of it.
It's called everyday usage, and I can bet you anything it is talked about in every Microsoft development circle and has been for years.
Member since:2006-04-10
None of your arguments "stick". I have used .net in a couple of years since 1.1, and i am still using it, both for win and web-developement.
I have never had, seen anyone or read about anyone having issues with using different versions of assemblies, or the framework itself. If there was problems, it was because of not following instructions.
I find it pretty funny you say i read to much marketing, and then afterwards you point me to a ancient marketing-slide. I am pretty sure that slide is insanely old, and it is _not_ correct. Avalon runs fine on xp.
Come with some sources for your points
Member since:
2006-04-10
"If only it were that easy. Not only do you need to test with that version, or test with all versions, .Net and your application do not stand by themselves."
I dont get your point? You write a lot of nonsense, impossible to respond to.
What dependencies? The dependecies (external libraries etc) i in my application? If a version of library not exists on the system, i simply put it in the gac. The gac manages all the different versions of that library, and i just load the one i need.
You are right its not 1990 anymore, and its not 1995 anymore either. Luckily dll-hell is non-exisiting in .net, if you do things the "Correct way"(tm).
And yes it is fud, i strongly belive you yourself has had a big dose of it. You arguments point suggest it.