Re: lifecyle?
- From: "mayayana" <mayaXXyana1a@xxxxxxxxxxxxxxxx>
- Date: Fri, 03 Nov 2006 22:20:47 GMT
How long will Microsoft give support to Vb6?
How long will Microsoft give support to COM?
(please, let's not get into the argument between VB6 and the .NET).
Will we always be able to run VB6 applications under Windows platforms?
I see many new Microsoft products which require Winsow XP as minimum...
Microsoft only officially, fully supports XP SP2
at this point, and they had to grant an extension
to do that. (XP Home was scheduled to be already
kaput by now.) ...And from what I've been reading,
people seem to be wondering whether MS might
just skip XP SP3 and let XP fade away once Vista
is out. So there's a question as to how
relevant Microsoft support is altogether. I don't
have any fully supported MS software - and I don't
want any. And I wouldn't be surprised if I'm able
to run my Win98 at a later date than current XP Home
users, since MS could start refusing to issue
new product activation codes at any point.
I was reading an interesting article today about
guidelines for writing to Vista:
http://msdn.microsoft.com/windowsvista/reference/default.aspx?pull=/library/
en-us/dnlong/html/AccProtVista.asp
They mention using COM objects for various
purposes, like dealing with a high-permission
action in an otherwise low-permission program
in Vista. There doesn't seem to be any
indication that VB6 will be a problem in Vista,
(although VB is ignored in their article) but it looks
like the permission issues will be
a big pain in the neck. For instance, a limited
user can only write to App Data. If I understood
it all correctly, if you want to write to HKLM
or your own app.path, you can embed a manifest
into a signed EXE (which will probably involve
hacking the resource table for VB6 programmers).
The manifest tells Vista how much permission
you want. Then if UAC is active the user gets
pummelled with permission dialogues when your
software runs. The other option is to use no
manifest. You're then allowed to write to HKLM
or Program Files, but it's fake. Vista will actually
write to alternate, low-security single-user keys
and folders, while letting you think that you succeeded
in writing to HKLM, etc. It appears that AllUsers\AppData
is the only means of saving "all users" data in
normal operation.
It looks a lot like Suse Linux to me, (except with
the usual Rube Goldberg decorations that MS likes
to add in, like the virtualization of Registry and
folder paths): In Suse, one has to either put up with
constant permission prompts, which I personally
find entirely unworkable, or track down the semi-hidden
settings that allow one to run as actual root.
It's going to be interesting to see how this all
goes over. I can't imagine the average person
dealing with UAC.
So....it looks like COM will be around for awhile.
....And there seems to be a question as to how
soon Vista will be relevant. 1year? 2 years? More?
.
- Follow-Ups:
- Re: lifecyle?
- From: Michael B . Johnson
- Re: lifecyle?
- Prev by Date: Re: VB6 ActiveX DLL Form & Excel
- Next by Date: Re: VB6 ActiveX DLL Form & Excel
- Previous by thread: Re: lifecyle?
- Next by thread: Re: lifecyle?
- Index(es):
Relevant Pages
|
Loading
