Karl Seguin

Here's an idea for Microsoft, build an IDE that can work with multiple versions of the framework through plug-ins. You know, like all those other IDEs for those other languages out there.

If it wasn't for ReSharper, I wouldn't even use Visual Studio.

I KNOW you can't register, but that's the problem of Telligent and their incapability to run the site, sorry for that.

I disabled anonymous comments because of the # of spamreplies during the day. Though I think writing your own comment in a blogpost won't hurt :)

The VM idea sucks. (1) my employer has to buy better hardware than normal (2) my employer needs to buy more licenses than normal.

It's a big win for Microsoft, and not so much for everyone else.

Accessing and Updating Data in ASP.NET 2.0: Retrieving XML Data with XmlDataSource Control [Via: ] Vista...

The funniest thing to me is the implication that the VB6 IDE "works" on Windows XP. It "works," if by "works" you mean "has dozens of UI glitches not present on Win2k in addition to the ridiculous compiler problems unknown to users of real languages."

Dan,

I was never really a VB programmer. I did program a couple ActiveX controls in VB6 a month or so ago and the going was very rough. Never figured they were XP specific...

I don't think I was ever a VB programmer, either. I merely had a bunch of VB projects thrust upon me by developers who have subsequently gone on to pursue careers in the gravel industry. Maybe I'm in denial.

It is sad, that with all of the stability one could expect from a company with the prominence of microsoft that there is no stability, no cross compatibility even within its own projects. There should be backwards compatibilty to 2003 at least and it should run, without glitches on all versions of Microsoft OS from 2000 on.

This is just one of those examples of microsoft telling everyone if you want to develop apps for us, you have to follow what we do. Java is sounding tastier at the moment.

Does this mean version 1.1 components won't run, or can't even be modified on Vista which "has" to work for a version 1.1 sub-program?

Derek: 1.1 apps will run...it's the actual IDE (Visual Studio) that'll have problem.

Since this was initially reported, it's been cleared up that for the most part VS.NET 2003 _WILL_ run on vista and there shouldn't be any problems. However, I don't think it'll officially be supported on Microsoft and you _might_ have some issues, but I think for what most people do, it'll be fine.

Me:

Maybe...one of the initial issues was that we didn't get a reason why. It turns out that it has a lot to do with security and the debugger. At least we have a reason now...and it's probably a good one (we really have to take their word for it). I don't know much about it, but it makes sense...you assume debuggers run very deep in the kernel and hook deep into the system...

Unfortunatly, I have just found that 'Find in Files' does not work in VS2003 on Vista RTM. I managed to install VS2003 and SP1 and all was going fine (debugging unmanged code etc) untill I searched my solution for somehting... CRASH!

Well, although in the Microsoft world, it is possibly to constantly use the newest technology, unfortunatly, in my pittyful world, we have to support applicaitons that are built in VS2003 and event 2002 & 6.0 (generally unmanged c++). Do we simply state that our products are not Vista compaitble (although clearly the applicaitons run fine once developed)?

How are we supposed to debug problems if we can not debug them on the OS the user is running?

I can't believe MS could make this decision for a supported product. I could understand it maybe for a product out of the suport cycle.

Microsoft use to be very good to developers, which obviously worked because there are so many applications for Windows. It quite simply helped make Windows the success it is today. What happens when said develpoers either stop developing Windows applications OR don't support the new OS, simply because MS cant provide support in their new OS's? Surly what will happen is the number of applicaitons for Vista will decrease. Won't that, in the long run, mean people either won't upgrade to Vista, or won't use Windows full stop?

And as for installing inside a VM - Well bang goes the ability to debug in the OS the user is running - again so its no real argument.

Might pissed off about this - especially something as "simple" as find in files! Typical.

/Rant over.

Phil

VS2003 in Vista - "find in files" crash - right-click Visual Studio link -> Properties -> Compatibility  and tick Disactivate Visual Themes. It works ! Where is the logic in that though ...