PowerBASIC Peer Support Forums
 

Go Back   PowerBASIC Peer Support Forums > User to user Discussions > Cafe PowerBASIC

Cafe PowerBASIC General discussion. Topics need not be related to PowerBASIC, but promotion of other programming languages is not appropriate.

Reply
 
Thread Tools Display Modes
  #1  
Old Sep 27th, 2006, 06:46 AM
Stan Durham Stan Durham is offline
Member
 
Join Date: Jun 2004
Posts: 852
I said it would happen - Goodby DLL Hell - Hello NET Hell

"Visual Studio 2005 SP1 will run on Vista but will likely have a few
compatibility issues. We are working with the Vista team to understand
those, to provide workarounds where possible and also work on
providing you with a set of fixes beyond SP1."

"However, we will not support Visual Studio .NET 2002 or Visual Studio
.NET 2003 as development environments on Windows Vista."
http://blogs.msdn.com/somasegar/arch...26/772250.aspx

A lot of things in NET are brilliant but I think it will turn into a
maintenance monster that even MS can't sustain.

Every application may need to be recompiled as a version goes out of
scope, which may break some things.
(That may also mean that all third-party tools will have to match,
which also may break things.)

That also means that all users will have to upgrade their runtime.
If everything doesn't sync right - broken app.

Just upgrading a service pack may break add-ons until they are
upgraded to match.

If something changes in Vista, the whole NET environment has to change
to match.

It took years to finally get Windows basically working right, Windows
XP, and then they had a brilliant idea.
It will take many years to get Vista right, if they ever get it out
the door.
That means the NET environment will be in a constant state of flux.


------------------
Reply With Quote
  #2  
Old Sep 27th, 2006, 07:53 AM
Marco Pontello Marco Pontello is offline
Member
 
Join Date: Oct 2002
Location: Venezia, Italy
Posts: 2,586
I don't understand.
The entry in the blog only talk about incompatibility of the dev environment (witch I don't find strange, in the MS universe, so to speak), not about problems running .NET apps.
I mean, nothing really new from that post.

Bye!

------------------
Try Online TrID file identifier! Recognize over 2.200 filetypes and counting...
Give a powerfull scriptable Lua interface to your application with PowerBLua
Leakout - Firewall outbound control tester - BitmapRip Extract/recover bitmaps from any file!

[This message has been edited by Marco Pontello (edited September 27, 2006).]
__________________
-- The universe tends toward maximum irony. Don't push it.

File Extension Seeker - Metasearch engine for file extensions / file types
Online TrID file identifier | TrIDLib - Identify thousands of file formats
Reply With Quote
  #3  
Old Sep 27th, 2006, 09:25 AM
Mike Doty Mike Doty is offline
Member
 
Join Date: Feb 2005
Location: Omaha, NE USA
Posts: 5,775
Along the DLL hell subject.
The Visual Basic 6 SP6 runtime library may have eliminated
the problem with VB6 since it will not be changed.
Have heard VB SP6 is included with XP. Is this true?



------------------
Reply With Quote
  #4  
Old Sep 27th, 2006, 10:03 AM
Knuth Konrad Knuth Konrad is offline
Member
 
Join Date: Apr 2000
Location: Frankfurt/Main, Germany
Posts: 3,894
Can't be as VB SP6 was released later than Win XP. So, an unpatched XP or XP SP1 (don't know for sure) might not include VB SP6 runtimes.

Knuth

------------------
http://www.softAware.de
Reply With Quote
  #5  
Old Sep 27th, 2006, 10:09 AM
Paul Squires Paul Squires is offline
Member
 
Join Date: Oct 2000
Posts: 2,086
I miss my Tandy 1000SX... life was so much simpler back then.


------------------
Paul Squires
FireFly Visual Designer, Cheetah Database System, JellyFish Pro Editor
www.planetsquires.com
__________________
Paul Squires
FireFly Visual Designer (for PowerBASIC Windows 10+)
Version 3 now available.
http://www.planetsquires.com
Reply With Quote
  #6  
Old Sep 27th, 2006, 10:34 AM
Stan Durham Stan Durham is offline
Member
 
Join Date: Jun 2004
Posts: 852
I might be getting a bad case of the “old fart syndrome” BUT,
I think the all-in-one runtime is a bad idea.

If things are kept in the smallest functional components, just replace bad components.

NET car; have a flat – replace car.


------------------
Reply With Quote
  #7  
Old Sep 27th, 2006, 12:48 PM
Mike Doty Mike Doty is offline
Member
 
Join Date: Feb 2005
Location: Omaha, NE USA
Posts: 5,775
XP SP2 and higher include VB6 runtime.
Run VBRUNSP6.EXE and let Microsoft do the installation.
Full download below: http://www.microsoft.com/downloads/details.aspx?familyid=7B9BA261- 7A9C-43E7-9117-F673077FFB3C&displaylang=en

Since this is the final update, I agree, no more DLL hell.




[This message has been edited by Mike Doty (edited September 27, 2006).]
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 08:11 AM.


Powered by vBulletin® Version 3.8.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright © 1999-2011 PowerBASIC, Inc. All Rights Reserved.
Error in my_thread_global_end(): 1 threads didn't exit