Groups > comp.lang.basic.visual.misc > #655

Re: Upgrading older VB programs (sans Project Files) to VB.NET

From	"Mayayana" <mayayana@invalid.nospam>
Newsgroups	alt.comp.lang.vb, alt.comp.lang.visualbasic, comp.lang.basic.misc, comp.lang.basic.visual.misc, microsoft.public.dotnet.languages.vb, microsoft.public.dotnet.languages.vb.upgrade
Subject	Re: Upgrading older VB programs (sans Project Files) to VB.NET
Date	2012-01-13 20:58 -0500
Organization	A noiseless patient Spider
Message-ID	<jeqn9e$mas$1@dont-email.me> (permalink)
References	(5 earlier) <jen22c$n55$1@dont-email.me> <jepvvp$h89$1@dont-email.me> <jeq3r8$9kq$1@dont-email.me> <jeq687$pag$1@dont-email.me> <jeq6r3$utp$1@dont-email.me>

Cross-posted to 6 groups.

Show all headers | View raw


| You can not access Win32 functions directly in a metro app.  For all
| practicle purposes, it is dead to the a developer targeting the metro
| interface.  Period.  To think that WinRT does not make use of Win32 at
| this point would be naive at best.
|

  Exactly. It's another wrapper in API's clothing.
I don't want to write Metro trinkets. I doubt
that you really want to either. And it's *very*
unlikely that anyone's going to make money
doing that.

   It'll be interesting to see how it pans out. Metro
is completely unrealistic for PCs. Nokia/Win phones
are getting great reviews, but no one is buying them.
Tablets never made much sense in the first place,
so it's hard to know how that will work out. No
matter how you look at it, people are not going to
be writing docs and spreadsheets on a swipe screen.

  Microsoft tried to move developers out of the system
with .Net. They're doing it further with Metro. The plan
sounds a lot like trying to cash in on the Apple model:
Tight control. Developers have to be approved. MS gets
a 30% cut of software sales. That might happen, but it's
not going to happen on a PC. And that's the only kind
of software I'm interested in writing or using.

  I'm actually very curious. On the surface, at least,
Microsoft seems to be turning away from corporate and
toward the entertainment market. So corporate PCs with
Win8 will be set to Desktop while non-business PCs will
be tuned to Metro, where people will spend their time
updating their Facebook page on their swipe screen?
That vision is so untenable in so many ways that I'm
quite curious to see how it all shakes out.

  It seems clear that VB will be usable for Desktop
software as long as people can actually control their
own Windows PCs. And .Net will continue to be relevant
on corporate intranets, if nowhere else. If Metro survives
at all it will be in an entirely different arena.

Back to comp.lang.basic.visual.misc | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Upgrading older VB programs (sans Project Files) to VB.NET Ubiquitous <weberm@polaris.net> - 2012-01-04 18:23 -0500
  Re: Upgrading older VB programs (sans Project Files) to VB.NET "Mayayana" <mayayana@invalid.nospam> - 2012-01-05 09:25 -0500
  Re: Upgrading older VB programs (sans Project Files) to VB.NET "Thorsten Albers" <gudea@gmx.de> - 2012-01-05 16:33 +0000
  Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-05 14:57 -0500
  Re: Upgrading older VB programs (sans Project Files) to VB.NET Helmut_Meukel <Helmut_Meukel@bn-hof.invalid> - 2012-01-05 22:32 +0100
    Re: Upgrading older VB programs (sans Project Files) to VB.NET "Auric__" <not.my.real@email.address> - 2012-01-06 02:50 +0000
  Re: Upgrading older VB programs (sans Project Files) to VB.NET Tony Toews <ttoews@telusplanet.net> - 2012-01-09 20:29 -0700
    Re: Upgrading older VB programs (sans Project Files) to VB.NET "Mayayana" <mayayana@invalid.nospam> - 2012-01-10 09:22 -0500
      Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-10 10:14 -0700
        Re: Upgrading older VB programs (sans Project Files) to VB.NET "Mayayana" <mayayana@invalid.nospam> - 2012-01-10 17:04 -0500
        Re: Upgrading older VB programs (sans Project Files) to VB.NET Schmidt <sss@online.de> - 2012-01-11 21:02 +0100
          Re: Upgrading older VB programs (sans Project Files) to VB.NET "Henning" <computer_hero@coldmail.com> - 2012-01-12 15:33 +0100
            Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-12 23:58 -0500
          Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-12 09:34 -0700
            Re: Upgrading older VB programs (sans Project Files) to VB.NET Schmidt <sss@online.de> - 2012-01-13 20:17 +0100
              Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-13 14:31 -0500
              Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-13 13:22 -0700
                Re: Upgrading older VB programs (sans Project Files) to VB.NET "Mayayana" <mayayana@invalid.nospam> - 2012-01-13 16:07 -0500
                Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-13 14:14 -0700
                Re: Upgrading older VB programs (sans Project Files) to VB.NET "Mayayana" <mayayana@invalid.nospam> - 2012-01-13 20:58 -0500
                Re: Upgrading older VB programs (sans Project Files) to VB.NET Tony Toews <ttoews@telusplanet.net> - 2012-01-19 19:10 -0700
                Re: Upgrading older VB programs (sans Project Files) to VB.NET Schmidt <sss@online.de> - 2012-01-14 00:12 +0100
                Re: Upgrading older VB programs (sans Project Files) to VB.NET "Henning" <computer_hero@coldmail.com> - 2012-01-14 00:24 +0100
                Re: Upgrading older VB programs (sans Project Files) to VB.NET Schmidt <sss@online.de> - 2012-01-14 00:58 +0100
              Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-13 19:35 -0500
                Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-13 22:46 -0500
                Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-13 23:50 -0700
                Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-14 14:31 -0500
                Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-14 22:47 -0700
                Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-15 01:26 -0500
                Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-15 07:54 -0700
                Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-15 14:09 -0500
                Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-15 16:47 -0700
                Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-15 16:49 -0700
                Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-15 21:16 -0500

csiph-web