[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Abhishek

9/13/2011 4:48:00 PM

121 Answers

Dee Earley

9/13/2011 4:53:00 PM

0

On 13/09/2011 17:48, Abhishek wrote:
> most probably will work.
> http://imageshack.us/photo/my-images/835/vb...
>
> from
> http://www.buildw...

So native apps are still supported.
We'll see whether they support the VB(6) runtimes or not.

--
Dee Earley (dee.earley@icode.co.uk)
i-Catcher Development Team
http://www.icode.co.uk...

iCode Systems

(Replies direct to my email address will be ignored.
Please reply to the group.)

Bob Butler

9/13/2011 5:23:00 PM

0


"Abhishek" <abhishek007p@hotmail.com> wrote in message
news:j4o1g8$720$1@speranza.aioe.org...
> most probably will work.
> http://imageshack.us/photo/my-images/835/vb...

That image shows "VB" but that is what Microsoft calls VB.Net now. They
don't admit to anything about VB6 or earlier

> from
> http://www.buildw...

The statements I've heard and seen all say that Microsoft is committed to
making anything that runs on Windows 7 run on Windows 8. They want to
concentrate on replacing the UI with the phone interface first, then trash
the applications later.

Abhishek

9/13/2011 5:26:00 PM

0

But not on Arm based devices. but c, c++ people are safe, they have said
they are going to provide cross compiler to compile c apps to Arm.


"Deanna Earley" <dee.earley@icode.co.uk> wrote in message
news:j4o1pt$6dn$1@speranza.aioe.org...
| On 13/09/2011 17:48, Abhishek wrote:
| > most probably will work.
| > http://imageshack.us/photo/my-images/835/vb...
| >
| > from
| > http://www.buildw...
|
| So native apps are still supported.
| We'll see whether they support the VB(6) runtimes or not.
|
| --
| Dee Earley (dee.earley@icode.co.uk)
| i-Catcher Development Team
| http://www.icode.co.uk...
|
| iCode Systems
|
| (Replies direct to my email address will be ignored.
| Please reply to the group.)


Abhishek

9/13/2011 5:33:00 PM

0

VB6 comes under Win32 category.


"Bob Butler" <bob_butler@cox.invalid> wrote in message
news:j4o3le$vtr$1@dont-email.me...
|
| "Abhishek" <abhishek007p@hotmail.com> wrote in message
| news:j4o1g8$720$1@speranza.aioe.org...
| > most probably will work.
| > http://imageshack.us/photo/my-images/835/vb...
|
| That image shows "VB" but that is what Microsoft calls VB.Net now. They
| don't admit to anything about VB6 or earlier
|
| > from
| > http://www.buildw...
|
| The statements I've heard and seen all say that Microsoft is committed to
| making anything that runs on Windows 7 run on Windows 8. They want to
| concentrate on replacing the UI with the phone interface first, then trash
| the applications later.
|


David Kerber

9/13/2011 6:45:00 PM

0

[This followup was posted to microsoft.public.vb.general.discussion and
a copy was sent to the cited author.]

In article <j4o1pt$6dn$1@speranza.aioe.org>, dee.earley@icode.co.uk
says...
>
> On 13/09/2011 17:48, Abhishek wrote:
> > most probably will work.
> > http://imageshack.us/photo/my-images/835/vb...
> >
> > from
> > http://www.buildw...
>
> So native apps are still supported.
> We'll see whether they support the VB(6) runtimes or not.


My guess would be that they'll run, but won't be installed by default
any more.

Abhishek

9/13/2011 6:52:00 PM

0

yes, runtimes wont be included beyond Windows 7, but then we can always
include them in setup. I was waiting for this to decide on a new app,
whether to choose VB6 or VB.NET, i am choosing VB6.


"David Kerber" <dkerber@WarrenRogersAssociates.invalid> wrote in message
news:MPG.28d96eccc0d036d3989741@news.eternal-september.org...
|
|
| My guess would be that they'll run, but won't be installed by default
| any more.
|


Tom Shelton

9/13/2011 7:01:00 PM

0

Abhishek explained on 9/13/2011 :
> yes, runtimes wont be included beyond Windows 7, but then we can always
> include them in setup. I was waiting for this to decide on a new app,
> whether to choose VB6 or VB.NET, i am choosing VB6.
>

Depending on the app - I if you aren't going to use .net - then, I
might think in terms of C++. If you go C++ (something I am extreamly
likely to do - since, C++ is my first love anyway) - and you design
right (seperate logic from the ui is my primary thought here) - you
will be able to make that app a first class citizen in the new
immersive interface when the time is right and work on both the desktop
and on tablets (and probably phones in the future if you care at all
about that). As well, as cross compile for both x86 and ARM. I just
can't really imagine using VB6 for any new serious development...

--
Tom Shelton


Karl E. Peterson

9/13/2011 7:37:00 PM

0

The Koolaid said:
> a first class citizen in the new immersive interface when the time is right

*retch*

> I just can't really imagine using VB6 for any new serious development...

So you've been saying for years now, yes...

--
..NET: It's About Trust!
http://vfre...


Mayayana

9/13/2011 8:01:00 PM

0


| I just
| can't really imagine using VB6 for any new serious development...
|

....Or .Net. It's all still gossip at this point, but
my impression was that MS is aiming for HTML
and javascript in a version of IE that's tied into
the Windows API. Compiled software would be
a grudging optional extra to run in the "Desktop
tile".

On the other hand, that whole idea seems so
absurd and unwise that I have to believe it's a
temporary case of cloud/tablet-fever. After all,
MS was talking about converting the API to an
easy, OO managed sandbox almost 10 years ago.
....It never happened. What was it they called
that? I think it was something like ".Net". That idea
was as wacky as this new web-app trip. Lucky for
us, they stuck with native code and COM. :)


Tom Shelton

9/13/2011 8:18:00 PM

0

Mayayana formulated on Tuesday :
>> I just
>> can't really imagine using VB6 for any new serious development...
>>
>
> ...Or .Net.

..NET is still a major part of windows 8 - which makes sense because of
it's jit behavior. Look at the slide.

> It's all still gossip at this point, but
> my impression was that MS is aiming for HTML
> and javascript in a version of IE that's tied into
> the Windows API.

Partially right. The trident rendering engine from ie 10 will be used
to render the new desktop. But, you don't have to develop that ui
using html5 or javascript. Those are just another option.

> Compiled software would be
> a grudging optional extra to run in the "Desktop
> tile".
>

Nope. Look at the slide. Metro UI apps. Taht's the new desktop.
Now, older winform, silverlight, wpf, native apps, and vb6 apps will be
there - but, all of those code bases - except one - have the option of
rewriting their UI's and becoming first class citizens again.

> On the other hand, that whole idea seems so
> absurd and unwise that I have to believe it's a
> temporary case of cloud/tablet-fever.

As much as I'm not a huge fan of the paradigm, I don't think it's going
away anytime soon.

> After all,
> MS was talking about converting the API to an
> easy, OO managed sandbox almost 10 years ago.
> ...It never happened.

Apparently, it has now. It's called WinRT.

> What was it they called
> that? I think it was something like ".Net". That idea
> was as wacky as this new web-app trip. Lucky for
> us, they stuck with native code and COM. :)

It's not about web apps. It's about touch friendly interfaces, etc.
But, I already know you are ludite of sorts - so, there is not need to
argue about it.

--
Tom Shelton